# Park Ranger

> Independently review one exact stable candidate for introduced actionable defects in a fresh session at the end. Use for Park Ranger, code review, or defect adjudication. Do not use for implementation, automatic review, evidence scoring, user acceptance, author self-review, or slice/round boundaries.

- Skill: `alphazede/park-ranger` (Agent Skill)
- Install (CLI): `npx skillmds@latest add alphazede/park-ranger`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alphazede/park-ranger/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: alphazede (https://skillmd.com/u/alphazede)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alphazede/park-ranger

---


# Park Ranger

Independent defect assurance, outside the mutation-authority ladder.

## Inputs and match

- **Inputs:** approved baseline, exact candidate ref and diff, author identity,
  relevant evidence, declared phase or wave end boundary, review focus, and
  compact return schema.
- **Match:** Park Ranger is declared and the declared phase or wave's
  integrated candidate is stable at that end.
- **Non-match:** slice or round boundary, candidate is unstable/unchanged, or
  Surveyor/Test Engineer work is requested.

## Algorithm

1. Start a fresh session; reject author identity, author ancestry, candidate
   discontinuity, or any boundary other than the declared phase or wave end.
   Consume the Assurance
   Test Engineer receipt. Do not routinely invoke Test Engineering; use it
   only to adjudicate a specific suspected test defect.
2. Review only introduced correctness, security, performance, and meaningful
   maintainability defects plus applicable plan drift. When the candidate
   implements a published standard, compare the change against the cited text
   rather than neighbouring agreement.
3. Prove reachability and affected code, assign P0–P3, and cite precise changed
   locations. Avoid speculation and nits.
4. Return a patch verdict and repair targets. Never implement a finding.

## Return and recovery

Return `BLOCK`, `REPAIR_REQUIRED`, `ACCEPT_WITH_FINDINGS`, or `ACCEPT` with
verdict, candidate_ref, changed_paths, tests, findings, and blocker.
`ACCEPT`, `ACCEPT_WITH_FINDINGS`, and `BLOCK` are terminal. `REPAIR_REQUIRED`
permits bounded correction. `ACCEPT_WITH_FINDINGS` accepts residual findings;
do not follow it with another repair. Coordinators enforce
`max_assurance_rounds` of 1 per declared phase or wave. A repairable verdict
permits one repair; the coordinator then runs deterministic verification and
closes the gate without another review. Do not review or repair that declared
unit again. The next distinct declared phase or wave carries its own budget. A
failed repair or scope change returns to Owner Authority.

Never edit, self-review, duplicate general review, or grant publication rights.