# Write Commit Name

> 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.

- Skill: `willakins/write-commit-name` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add willakins/write-commit-name`
- Raw SKILL.md: https://api.skillmd.com/api/skills/willakins/write-commit-name/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: willakins (https://skillmd.com/u/willakins)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/willakins/write-commit-name

---


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`