Individual skill
review
Use before merge, after subagents, or for spec/plan review.
plugins/ouonet/praxis/skills/review/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,531
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,781 bytes
Read excerpt
# Review
If `topology=multi-module` (triage announcement or coordinator spec/plan declaration), read `../references/multi-module.md`. Review each module diff in its owning repository first, then review the workspace as one change set. Block missing repositories, copied or divergent shared contracts, undeclared cross-module edits, overlapping writers, incomplete local acceptance, or integration results that do not identify the tested workspace combination.
Check in order:
1. **Spec match** (if spec exists) - diff does what the spec/plan said? List drift.
2. **Standards** — lint/format/typecheck green? Code matches `convention`, idiomatic for the stack? (see `../references/quality.md`)
3. **Tests** - new behavior covered, all green?
4. **Doc-coverage & Living docs** — `contract` covers full public surface? Env vars/config/error modes documented? README commands runnable? Living docs honor North Star (atemporal ground truth, modular specs; see `../references/quality.md`)?
5. **Edges** - null, empty, large, concurrent, malformed, unicode, timezone.
6. **Security** - input validation, secrets, authz, injection, path traversal.
7. **Scope** - unrelated changes? Revert. Implementation >2x necessary? Flag as FIX.
8. **Integration** (multi-module) - dependency order, compatibility, failure propagation, and coordinator acceptance cover the exact participating modules?
For spec/plan reviews, also block unresolved implementation notes, plan assumptions absent from spec, vague acceptance, or premature `[parallel]`.