Skip to content

PaloAltoNetworks/shifter / .claude/skills/stage

Stage files, run pre-commit, fix failures, loop until clean

Stage Changes

Step 1: Identify Changed Files

  1. Run git status to see all changed and untracked files.
  2. Exclude from staging: .env files, credentials, secrets, large binaries.

Step 2: Stage Files

  1. git add all relevant changed files.

Step 3: Pre-commit Loop

Run up to 5 iterations:

  1. Run pre-commit run --all-files.
  2. If it passes, proceed to Step 4.
  3. If it fails:
    • Read the failure output.
    • Fix the issues.
    • Re-stage any modified files with git add.
    • Go back to step 1.
  4. If still failing after 5 attempts, report the failure details to the user and stop.

Step 4: Report

  • List what is staged: git diff --cached --name-only
  • Confirm pre-commit passes.
  • "All files staged and pre-commit clean. Ready for commit."
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: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated 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: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall