polish-code

# Polish Code ## Task Tracking At the start of every invocation (including re-runs from Step 7), use `TaskCreate` to create a task for each step: 1. Run `/stage` skill 2. Run `/run-checks` skill 3. Run `/review-code` skill 4. Run `/evaluate-findings` skill 5. Run `/apply-findings` skill 6. Run `/smoke-test` skill 7. Re-run `/polish-code` skill if changed ## Step 1: Run `/stage` Skill Run the `/stage` skill. ## Step 2: Run `/run-checks` Skill Run the `/run-checks` skill. Stage all changes made in this step before continuing. ## Step 3: Run `/review-code` Skill Run the `/review-code` skill on the staged changes. The diff command is `git diff --cached`. ## Step 4: Run `/evaluate-findings` Skill Run the `/evaluate-findings` skill on the results from Step 3. ## Step 5: Run `/apply-findings` Skill Run the `/apply-findings` skill on the evaluated results. Record any fix whose remedy you deliberately narrowed as you make it, naming what the remedy covered and what it left, so Step 7 carries it forward without reconstructing the decision later. When a fix ships with a regression test, confirm the test fails with the fix reverted, then restore the fix. Stage the fix immediately before mutating it (`git add <file>`), so `git checkout -- <file>` restores it exactly from the index. A file staged in an earlier step has an index copy older than the current edits, and restoring reverts them. Stage only the files about to be mutated, and reach for `git add -p <file>` when one...