Skip to content

pappcorn/universe / packages/best-practices-git/skills/commit

Stage and commit the pending changes the way this repository already does it. Reads the repo's own git history to infer its conventions (Conventional Commits or not, scopes, granularity, trailers) instead of imposing a house style, partitions the working tree so one commit is one logical change, screens for credentials and stray data files, stages by name, and writes a message whose body explains WHY. Refuses to commit on a protected branch, never runs `git add -A`, never `--no-verify`, never amends unasked. Use when the user says "commit", "commit this", "ship this", "save this", "haz un commit", or otherwise wants the current changes recorded.

Indexed versions of this skill
CommitIndexedFilesContent hash
c6c0897current2026-11-181 · 10.2 KBa774e6a2902dc9a7…
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