simonepri/ifttt-lint / .agents/skills/commit
commit
VerifiedStage changes and create a commit with a conventional commit message.
Commit
-
Assess: run
git statusandgit diffto see changes. -
Stage: relevant files only. If $ARGUMENTS contains file paths, stage only those. If empty, stage all changed files or ask the user. Never stage sensitive files (.env, credentials) without confirmation.
-
Message: analyze the staged diff. Write a conventional commit message:
-
Format:
type(scope): subject— types:feat,fix,refactor,chore,docs,test,ci,perf -
Breaking changes: append
!(e.g.,fix!: remove deprecated endpoint) -
Subject: under 72 chars, imperative mood. Must reference what changed specifically — generic subjects like "initial commit", "fix bug", "update code" are never acceptable.
-
Body: always use the reasoning framework with
##markdown headings. Required: Problem + Solution. Optional (include only when they add non-obvious context): Goal, Background, Alternatives.## Problem <what was wrong or missing> ## Goal (optional) <what this change aims to achieve, if not obvious> ## Background (optional) <context needed to understand why, if non-obvious> ## Solution <what was done and why this approach> ## Alternatives considered (optional) <what else was evaluated and why not> -
One logical change per commit. If you need "and" in the subject, split it.
-
-
Commit: create a unique temp file with
mktemp /tmp/commit-msg.XXXXXX.txt, write the message to it, and rungit commit -F <temp-file>— do not add Co-Authored-By or other trailers.
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 |