gen-commit-msg

Context

• Current git status: !git status
• Current git diff (staged changes only): !git diff --staged
• Current branch: !git branch --show-current
• Recent commits touching the staged files: !git diff --staged --name-only | xargs -r git log -10 --format='%h %s%n%b' --
• Recent commits (repo-wide, fallback only): !git log --oneline -5

Your task

Your task is to help the user to generate a commit message and commit the changes using git.

Guidelines

• DO NOT add any ads such as "Generated with Claude Code"
• Only generate the message for staged files/changes
• Infer the type and scope from the staged files' own commit history first; use the repo-wide log only when that history is empty (e.g. newly added files).
• Don't add any files using git add. The user will decide what to add.
• Follow the Format and Rules from the template file you read.
• You MUST first display all three of the following in your reply, in order: (1) the list of modified files, (2) a concise summary of the changes, and (3) the complete generated commit message (title and body). Only then use the AskUserQuestion tool to confirm before executing git commit — in the option's preview field, show ONLY the complete commit message (title and body), NOT the file list or the summary.
• After successfully committing, run fork log to open the Fork app for the user to review the commit history in GUI
• In plan mode: do NOT write a plan file or call ExitPlanMode. Treat the AskUserQuestion confirmation as approval, and run git commit then fork log directly.

Format

| Language | Trigger | Template | |----------|---------|----------| | English | Default | format-en.md | | Chinese | $ARGUMENTS = zh or user mentions "中文/Chinese" | format-zh.md |

Rules

• title is lowercase, no period at the end.
• Title should be a clear summary, max 50 characters (or 50 Chinese characters).
• Use the body (optional) to explain why, not just what.
• Bullet points should be concise and high-level.

Avoid

• Vague titles like: "update", "fix stuff"
• Overly long or unfocused titles
• Excessive detail in bullet points

Allowed Types

| Type | Description | | -------- | ------------------------------------- | | feat | New feature | | fix | Bug fix | | chore | Maintenance (e.g., tooling, deps) | | docs | Documentation changes | | refactor | Code restructure (no behavior change) | | test | Adding or refactoring tests | | style | Code formatting (no logic change) | | perf | Performance improvements |