Individual skill

staff-review

Review a local branch, diff, repository, directory, or file for supported specification and quality findings.

plugins/reidemeister94/development-skills/skills/staff-review/SKILL.md

Read pinned source

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.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Staff review

Resolve the requested scope. With no explicit scope, review the current branch changes; if none exist, ask what to review.

Dispatch a separate `development-skills:staff-reviewer` subagent in a new context window with no parent conversation history.
Never fork or continue the implementation context.
Give it the change as an artifact, plus the requirement or plan, related chronicle, project standards, and verification evidence.
Do not narrate how the change was built, what you concluded, or what you suspect.
On Codex, state that the reviewer is read-only because a custom agent inherits the parent's live sandbox and approval state.
Wait for its verdict.

The reviewer must inspect the diff before those materials and return separate specification and quality verdicts.
No findings is a valid result.
For re-review, give it the prior findings and fix diff. It checks those findings and new breakage without reopening untouched code.