Fix Findings

!PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel)}" && mkdir -p "$PROJECT_DIR/.claude" && touch "$PROJECT_DIR/.claude/.fix-findings-active" && echo "fix-findings marker created at $PROJECT_DIR/.claude/.fix-findings-active — post-review edit lock open for this run"

Take the review findings a human has already chosen, have a fresh sub-agent write each fix, have a second fresh sub-agent try to break it, and report both back. Hand off to a /pre-merge re-run, which is the only thing that re-stamps.

Why this skill exists

/pre-merge delegates the review to a sub-agent that did not write the code, because the session that wrote it has already demonstrated it cannot see these particular defects. Then the human picks findings, and the pipeline hands the fix back to that same blind session. The responsive commit is the most defect-dense code on the branch and the one commit with no independent reader.