Skip to content

simonepri/ifttt-lint / .agents/skills/amend

Amend the last commit with current changes and/or an updated message.

Amend

Amend the last commit. Assumes the existing commit message is correct — only update it to reflect the delta.

  1. Safety: check if the last commit exists on the remote. If it does, warn that amending requires a force push and ask for confirmation.
  2. Stage relevant files. If $ARGUMENTS contains file paths, stage only those.
  3. Message: read the existing commit message and the newly staged diff (git diff --staged). Update the message only if the delta changes the "what" or "why" — don't rewrite from scratch. Use the same body format as /commit (Problem + Solution with ## headings).
  4. Amend: create a unique temp file with mktemp /tmp/commit-msg.XXXXXX.txt, write the message to it, and run git commit --amend -F <temp-file> — do not add Co-Authored-By or other trailers.
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