The codified ticket-handling policy from 'Skill Issue' — a skill, a script, and a rule packaged as one distributable context artifact.
58
67%
Does it follow best practices?
Impact
96%
1.60xAverage score across 1 eval scenario
Advisory
Suggest reviewing before use
Process steps in order. This skill owns ONE lane — code tickets that need a reviewed PR. Docs-only and context-artifact tickets are out of scope; let the agent handle those directly.
Make the code change for the ticket on a feature branch. Keep it focused.
Open a pull request. The tests-before-pr rule (always applied) will block this
if the project has no tests — satisfy it first; do not work around it.
Run scripts/await_review.py <pr-number>. It requests a Copilot review via the
GitHub GraphQL API, then polls on a fixed interval until the review posts or the
timeout elapses. This is deterministic work — never hand-roll the summon/poll in
the model; call the script so it costs the same (cheap) every time.
Read the review. Address every comment, push fixes, and re-run Step 3. When the review is clean, merge. If the review never clears, stop and report — do not force the merge.