encero-systems/incan / .agents/skills/write-commit-message
write-commit-message
VerifiedDraft commit titles and optional commit bodies using the workspace commit naming convention. Use when the user asks for a commit message, commit text, commit title, or wants commit wording in the format `chore|bugfix|feature - <issue_id(s)> <short description>`.
Write Commit Message
Workflow
- Identify the repository and inspect the actual change set before drafting anything.
- Infer the change type from the diff:
bugfixfor correctness fixes and regressionsfeaturefor new behavior or newly implemented surface areachorefor maintenance, docs-only changes, refactors without new behavior, or repository housekeeping
- Infer issue ids from the branch name first, then from explicit issue references in the current task context if needed.
- Write the title in exactly this format:
<type> - <short description> (<#issue_id(s)>)
- Keep the short description concrete:
- specific to the actual diff
- no trailing punctuation
- no vague filler like
updatesormisc fixes
- If the user also wants a commit body, write:
- one short sentence on what changed
- one short sentence on why
- optional flat bullets only if there are multiple distinct changes worth calling out
Issue Id Rules
- Use numeric ids joined by commas when there are multiple issues:
bugfix - preserve method result types for locals bound from calls (#252, #255)
- Do not prepend
#unless the user explicitly asks for that style. - If no issue id is discoverable, say so instead of inventing one.
Output Rules
- If the user asks for a commit message or commit text, return the commit title by itself unless they also asked for a body.
- If the user asks for both, return the title first and then the body.
- Do not wrap the final title in commentary.
- If the requested type conflicts with the actual diff, follow the diff and say so.
Examples
bugfix - preserve something important for locals bound from calls (#42)
feature - add Session builder and DataFusion backend seam (#5)
chore - tighten RFC 008 optimizer boundary wording (#18)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |