Skip to content

ashaychangwani/imprint / .agents/skills/commit

commit

Verified

Create a conventional commit from staged changes — picks type, scope, and writes the message.

Commit Skill

Create a well-formed conventional commit from the currently staged changes.

Step 1 — Check staged changes

Run git diff --cached --stat to see what's staged. If nothing is staged, tell the user and stop.

Run git diff --cached to read the actual diff.

Step 2 — Determine commit type

Pick the type based on the nature of the change:

TypeWhen to use
featNew user-facing feature or capability
fixBug fix
refactorCode restructuring without behavior change
perfPerformance improvement
testAdding or updating tests
docsDocumentation only
ciCI/CD configuration
choreMaintenance, dependencies, tooling
buildBuild system or external dependency changes
styleFormatting, whitespace, linting (no logic)

Step 3 — Determine scope

Pick a scope from the file paths changed. Established scopes in this repo:

cli, probe, backend, playbook, stealth-fetch, cron, notify, utils, types, replay-backend, mcp, record, redact, session-writer

If the change spans multiple areas, omit the scope. If it's a new area, derive the scope from the directory name.

Step 4 — Write the commit message

Format: <type>(<scope>): <subject>

Rules:

  • Subject line: imperative mood, lowercase, no period, under 72 chars
  • Body (optional): explain WHY, not WHAT. Wrap at 100 chars.
  • Footer (optional): BREAKING CHANGE: <description> if applicable

Step 5 — Show and confirm

Show the proposed commit message to the user. Ask if they want to proceed, edit, or cancel.

Step 6 — Execute

Run the commit using a heredoc:

git commit -m "$(cat <<'EOF'
<commit message here>
EOF
)"
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 implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall