Menu
OBPI-scoped code review for reuse, quality, and efficiency. Resolves scope from the brief's Allowed Paths, reviews across three dimensions, and applies fixes. Use after implementation, before reconcile.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Validate and stage a candidate rendition from the corpus via gz content compose. Use when the agent has made compression decisions (drop/combine/rewrite of compressible corpus entries toward the declared setpoint) and wants the tool to validate invariant-floor compliance, compute byte evidence, write the candidate artifact, and emit a ledger event.
Enter and exit the MX Maintenance Hangar — operator's interface to gz mx. Use when entering the hangar to perform governance repair, checking hangar status mid-session, or cleanly exiting when repair is complete. Operator operates the skill; the skill invokes gz mx; nobody shells out.
Create and resume session handoff documents for agent context preservation across engineering sessions.
Create and resume session handoff documents for agent context preservation across engineering sessions.
Collaborative design dialogue that produces GovZero ADR artifacts. Use when exploring a new feature, capability, or architectural change before implementation — replaces superpowers brainstorming for this project. Triggers on "design X", "let's design", "brainstorm X", "I want to build X", "gz-design".
Cross the airlock membrane — the entry/exit gate every unit of work passes through (ADR-0.33.0). Use to inspect a target's seam-map before touching it (`gz airlock in`), account for what a transit disturbed (`gz airlock out`), or make a governed ad-hoc reconnaissance entry with light repair at most (`gz permitted-entry`). Diagnostic-only for now — a staged posture, not the declared end state; never writes L1 canon.
| name | gz-obpi-simplify |
| persona | quality-reviewer |
| description | OBPI-scoped code review for reuse, quality, and efficiency. Resolves scope from the brief's Allowed Paths, reviews across three dimensions, and applies fixes. Use after implementation, before reconcile. |
| category | obpi-pipeline |
| lifecycle_state | active |
| owner | gzkit-governance |
| last_reviewed | "2026-07-26T00:00:00.000Z" |
| metadata | {"skill-version":"6.1.0"} |
| model | sonnet |
OBPI-scoped code review: resolve scope from the brief, review across three dimensions (reuse, quality, efficiency), fix issues found.
Position in workflow: After implementation (pipeline Stage 2-3), before reconcile. This is the implementation quality gate — the pipeline verifies correctness; simplify verifies craft.
These thoughts mean STOP — you are about to skip the craft gate:
| Thought | Reality |
|---|---|
| "The code is working fine, no simplification needed" | Working code that is hard to read will be hard to fix when it breaks. Simplification is about future maintainability. |
| "Changing this code is too risky" | Every fix is behavior-preserving and validated by tests. Risk is an excuse to leave technical debt. |
| "This is just formatting, ruff handles it" | Ruff handles syntax formatting. Semantic simplification (dead code, poor naming, unnecessary complexity) is this skill's domain. |
| "The OBPI is done, simplification is optional" | Simplification is the craft gate between pipeline completion and reconciliation. Skipping it ships unreviewed complexity. |
| "I don't understand this code well enough to simplify it" | Step 1 is "understand before touching." If you cannot understand it, that is a red flag for the code, not a reason to skip. |
/gz-obpi-simplify OBPI-0.5.0-01
/gz-obpi-simplify 0.5.0-01
/gz-obpi-simplify OBPI-0.5.0-01 focus on error handling
The first token is the OBPI ID. Remaining tokens are an optional focus directive.
Find the brief file using the Glob tool:
Glob(pattern="docs/design/adr/**/obpis/OBPI-{id}*.md")
Glob is the cross-platform native answer; find is Bash-only and
fails on Windows-native shells.
Read the brief and extract the ## Allowed Paths section.
Expand those patterns against the working tree to produce the concrete file list.
If the brief has an ### Implementation Summary section with explicit file paths,
include those too — they capture files actually touched.
Filter to source/test code (.py, .md in docs/, config files). Exclude binaries.
If no brief is found, abort with an error message.
The file list is the review scope. Do not review files outside it.
Before reviewing, scan scoped files for simplify-ignore annotations. Code
within these annotations is excluded from all three review dimensions.
# simplify-ignore-start: governance-critical
# ... code that must not be simplified ...
# simplify-ignore-end
Supported reasons:
| Reason | When to use |
|---|---|
governance-critical | Code that enforces governance invariants (ledger writes, gate checks) |
performance-sensitive | Code where clarity was intentionally traded for performance |
external-contract | Code that implements an external API or protocol exactly |
intentional-complexity | Code where the complexity is inherent to the problem domain |
Rules:
Review the scoped files from three independent lenses. Agents that support parallel dispatch should run all three concurrently. Sequential execution is acceptable when parallel dispatch is not available.
Look for:
Look for:
Look for:
For each finding: fix it directly. Skip false positives silently. Apply the optional focus directive (if provided) to weight review attention.
After all reviews complete:
uv run ruff check . --fix && uv run ruff format .
uv run -m unittest -q
simplify-ignore annotations. Do not modify code within annotated protected regions.| Skill | Relationship |
|---|---|
gz-obpi-pipeline | Pipeline verifies correctness; simplify verifies craft |
gz-obpi-sync | Run after simplify to catch any status drift |
gz-check | Simplify runs quality checks as part of Step 3 |