Turn a breaking change (an API rename, removed flag, changed default, or moved module) into concrete upgrade steps with before/after examples.
SkillScore64Maintained
Automatic
◆Doc Ops pack
Last verified 8/12/2026
What it changes
Passed 14 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill64%
Checks it passed that the model alone missed
Keeps overview text to a single paragraph.
Uses `## What changed` for the change summary.
Restricts overview text to a single paragraph.
and 20 more in the full report
11 fixed3 passed either way8 still failing0 broke
Pass-rate lift
+50 pp
Tokens
-17%
Agent turns
0%
Response time
-36%
Model gemini-3.6-flashMeasured 8/12/2026v114 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Our GraphQL service replaced field `user(id: ID!)` with `account(by: AccountInput!)` in schema version 2024.1. Write a migration guide covering why it changed, step-by-step queries to update, before/after query examples, and deprecation header fallback.
What was checked, without and with the skill
Checked
Without skill
With skill
Uses `## If you can't upgrade yet` as the header for fallback options.
Missed
Passed
Details explicit field query changes from `user(id:)` to `account(by:)`.
Passed
Passed
Annotates GraphQL snippet comparisons with `# before` and `# after`.
Missed
Passed
case-09 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md54 linessingle file
migration-guide — write upgrade steps for a breaking change
Produce a guide that lets a user on the old version land on the new one with the
least friction.
Pin down what actually broke
Identify the precise breaking change before writing a word. Get it from the diff
and history, not from the description alone:
git diff <old>..<new> on the affected surface, and gh pr view <n> for the
PR that introduced it.
Dispatch the researcher (purpose: explore) to confirm the exact old and new
shapes: the old name/signature/default, the new one, and whether a
compatibility shim or deprecation window exists.
Never document a rename or signature change from memory — the exact symbols are
what users will copy.
Structure
# Migrating to <version>
## What changed
<one paragraph: the change and why, in user terms>
## Upgrade steps
1. <ordered, mechanical steps>
## Before / after
```
# before
...
# after
...
```
## If you can't upgrade yet
<deprecation window, shim, or flag to opt out — if one exists>
Spin up a live local Omnigent server + runner and exercise the native Pi TUI harness (pi-native) end-to-end — launch the real `pi` CLI via `omnigent pi`, drive turns through the web/bridge, smoke-test, and bug-bash. Load when developing, testing, or debugging the pi-native harness (omnigent/inner/pi_native_executor.py, pi_native_harness.py, omnigent/pi_native.py, pi_native_bridge.py, pi_native_credentials.py) or its bridge / extension / auth / model behavior.