Use this when a PR has review feedback, merge conflicts, pending checks, or
SkillScore13Maintained
Automatic
◆Coding pack
Last verified 7/28/2026
What it changes
Passed 2 of 19 test cases with the skill, and 0 of 19 without it.
Without skill0%
With skill13%
3 fixed0 passed either way20 still failing0 broke
Pass-rate lift
+13 pp
Tokens
-22%
Agent turns
0%
Response time
-51%
Model gemini-3.6-flashMeasured 7/28/2026v13 of 23 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md38 linessingle file
PR Feedback Quality Gate
Use this when a PR has review feedback, merge conflicts, pending checks, or
needs a monitored follow-up after a fix.
Workflow
Inspect PR state first: comments, reviews, mergeability, checks, branch, and
local worktree status. Keep unrelated local changes out of the PR.
Use an isolated worktree for review fixes or conflict resolution when the
main checkout is dirty, behind remote, or being used by another agent.
Make the smallest safe fix. Preserve the original bug invariant and any
newer upstream structure introduced by main.
Run the narrow validation first, then the repository-required gates. For
this repo, include pnpm guard; add package typechecks/builds/tests when
touched files require them.
Before commit or push, run a read-only cross-review of the staged or proposed
diff. Forbid file edits and git write or coordination commands.
Treat cross-review as evidence, not authority. Accept only findings grounded
in the diff, repository rules, user goal, or validation results. Downgrade or
reject style preferences, broad scope expansion, and suggestions that conflict
with safety or ownership boundaries; record the reason briefly.
If accepted blockers remain, fix them, rerun validation, and repeat the
review. Commit and push only after validation passes and there are no
accepted blockers.
Monitoring cadence
Active review or failing checks: check often enough to unblock quickly.
Clean or approved PR waiting for merge: check about every 12 hours.
Merged PR: reduce to daily lightweight observation for CI, release, or
regression signals, and stop making code changes unless asked.
Report
Always report PR state, actions taken, cross-review verdict, accepted or
rejected findings, validation run, commits pushed, skipped checks with reasons,
remaining risks, and next step.