Use this skill when the user asks for a commit name, commit subject, or commit message subject line.
Do not use this skill to create commits, edit files, push branches, open PRs, or monitor CI.
Source of truth
- If files are already staged for the intended commit, base the commit name only on that staged diff.
- Otherwise, base it only on the exact in-scope local changes that belong in the intended commit.
- Read the staged diff or staged file list before proposing a subject when staged changes exist; otherwise read the local diff or changed file list.
- Ignore prior commits, branch names, and planned future work unless they are visible in the staged or in-scope local changes.
Commit name rules
- Return one short subject line.
- Keep it specific to the main behavior change, not a file list.
- Prefer imperative phrasing.
- Do not add a body unless the user asks for one.
- Do not append
#CI by default.
- Append
#CI only when the prompt explicitly asks to include a CI marker on that content commit. Requests to trigger CI, trigger actions, run GitHub Actions, or commit with actions should create a separate empty #CI trigger commit after the content commit is published.
Writing heuristics
- If the change is a bug fix, lead with
Fix, Handle, Prevent, or Fallback.
- If the change is a feature, lead with
Add, Support, Show, or Create.
- If the change is mostly docs or workflow, lead with
Document, Clarify, or Add.
- If both code and docs changed, bias toward the code behavior unless the docs are the primary deliverable.
Output format
- Return only the proposed commit subject line unless the user asks for options.
Example
Fix member-employer worker ID fallback
1---2name: write-commit-name3description: Draft a short git commit subject from the staged diff when a commit slice is already staged, otherwise from the exact in-scope local diff. Append `#CI` only when the requester explicitly asks to include a CI marker.4---56Use this skill when the user asks for a commit name, commit subject, or commit message subject line.78Do not use this skill to create commits, edit files, push branches, open PRs, or monitor CI.910## Source of truth1112- If files are already staged for the intended commit, base the commit name only on that staged diff.13- Otherwise, base it only on the exact in-scope local changes that belong in the intended commit.14- Read the staged diff or staged file list before proposing a subject when staged changes exist; otherwise read the local diff or changed file list.15- Ignore prior commits, branch names, and planned future work unless they are visible in the staged or in-scope local changes.1617## Commit name rules1819- Return one short subject line.20- Keep it specific to the main behavior change, not a file list.21- Prefer imperative phrasing.22- Do not add a body unless the user asks for one.23- Do not append ` #CI` by default.24- Append ` #CI` only when the prompt explicitly asks to include a CI marker on that content commit. Requests to trigger CI, trigger actions, run GitHub Actions, or commit with actions should create a separate empty `#CI` trigger commit after the content commit is published.2526## Writing heuristics2728- If the change is a bug fix, lead with `Fix`, `Handle`, `Prevent`, or `Fallback`.29- If the change is a feature, lead with `Add`, `Support`, `Show`, or `Create`.30- If the change is mostly docs or workflow, lead with `Document`, `Clarify`, or `Add`.31- If both code and docs changed, bias toward the code behavior unless the docs are the primary deliverable.3233## Output format3435- Return only the proposed commit subject line unless the user asks for options.3637## Example3839`Fix member-employer worker ID fallback`
willakins