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. Deterministic cleanup 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: Deterministic Cleanup Run the project's full verification gate: every check it defines as a pass/fail condition. The goal is that passing this step means the project's own checks (and CI, where it exists) pass. Build the gate by combining every source below that the project declares (sources 1-3); run the baseline (source 4) only when the project declares none of them: 1. **CI config** — where present, it is the authoritative gate; run the checks it enforces. 2. **Check scripts** — package-manager scripts (`check`, `verify`, `lint`, `typecheck`), Makefile or Taskfile targets, or a combined format+lint script. 3. **Configured tools** — any tool with a config committed to the repo, such as a dead-code or unused-dependency gate. A committed config means the project treats the tool as a gate; run it even when no script or CI invokes it. Do not run such a tool when the project has not configured it; unconfigured runs are discovery, which belongs to `/find-dead-code`. 4. **Baseline** — when the project declares nothing more, run the formatter, then the linter, t...