modrexio/modrex / .agents/skills/commit
commit
UnverifiedPropose a conventional commit message for the current diff
commit
Run git diff HEAD and git status, then propose a commit message.
Format
Read commitlint.config.ts for the enforced format rules. Follow them exactly.
Keep the subject short and imperative. Do not add a body unless the change is genuinely complex.
Rules
- Propose the message — do not run
git commituntil the user confirms. - If there are no staged or unstaged changes, say so and stop.
- Never include unrelated files in the same commit — if the diff spans multiple logical changes, say so and ask which to commit first.
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: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | 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: 319k | 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: 319k | Updated | Claude CodeCodex | Verified | Install |