polish

Polish

One combined quality pass over changed code. Fan out three review lenses as findings-only subagents (they read, they do not edit), merge and dedupe the results, auto-apply only the safe high-confidence findings, verify the result with the repo's own tooling, and hand back the riskier findings for the user to approve.

Proceed only when the surrounding user request explicitly asks for polishing (including direct /tgc-skills:polish invocation) or tgc-skills:ship invokes it. Do not load this skill from unrelated requests because polishing can edit files.

This is quality plus safe bug fixes, not a deep security audit.

Why findings-only subagents

Parallel agents that edit race each other on the same files. So the subagents only report structured findings, and a single orchestrator (you) applies edits sequentially. Fan-out read, fan-in write.

Step 1 — Resolve scope

• No argument: the current work — union of git diff --name-only, git diff --cached --name-only, and untracked files from git ls-files --others --exclude-standard. If all are empty, fall back to git diff --name-only HEAD~1 and say you did.
• Path argument: review that file/directory.
• Skip files a review can't help: lockfiles, generated code, snapshots, binaries, vendored dirs.

If there is nothing to review, say so and stop.

Step 2 — Fan out three lenses (parallel, findings-only)

Dispatch three general-purpose subagents in a single message so they run concurrently. Give each the file list and require it to return only a JSON array against this schema:

[{
  "file": "relative/path.ts",
  "line": 42,
  "lens": "correctness | simplification | over-engineering",
  "confidence": "high | medium | low",
  "behaviorChanging": true,
  "issue": "one-line description of the problem",
  "fix": "concrete, specific proposed change"
}]

The three lens prompts:

1. correctness — "Review these changed files for correctness bugs only: logic errors, off-by-one, null/undefined handling, wrong conditionals, race conditions, incorrect error handling, broken edge cases. Do NOT report style or simplification. Set behaviorChanging: true for any fix that alters runtime behavior (most bug fixes do). Return findings-only JSON — do not edit files."