Skip to content

rse/ase / plugin/skills/ase-repo-commit

ase-repo-commit

Verified

Determine commit message for staged Git changes. Use when the user asks to "give", "write", "craft", "suggest", or "propose" a "commit message", or wants to know how to "describe" or "phrase" the staged changes for a commit.

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

  1. Run the following command to find out details of what changes are currently staged in the Git index for commit, capturing its output into :

    git diff --cached

  2. Craft a commit in the following format:

    <type/>: <summary/>

    The known s (kept deliberately in sync with the intent groups of the ase-repo-diff and ase-repo-changelog skills) and their usual corresponding kind of change are:

    • FEATURE: new functionality or configuration
    • IMPROVEMENT: improved functionality or configuration
    • BUGFIX: corrected functionality or configuration
    • UPDATE: updated functionality or configuration
    • CLEANUP: cleaned up functionality or configuration
    • REFACTOR: refactored functionality or configuration

    The rules for generating are:

    • Use a maximum of 60-80 characters
    • Use imperative mood ("add" not "added")
    • Use no period at the end
    • Use no Markdown formatting
    • Never add Co-Authored-By trailers to commit messages

    Output this crafted commit message with the following :

    Do not output any further explanation.

    Finally, give the closing hint by expanding the following (which, depending on the configured , may expand into nothing and hence emit no output at all):

    The staged changes do not touch CHANGELOG.md -- use /ase-repo-changelog to update its entries before committing.

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: 318kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated 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: 318kUpdated 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: 318kUpdated Claude CodeCodexVerifiedInstall