staff-review · diff
git:20260617.174aad8 to git:20260713.d210701
5 added, 7 removed. Audit A to A.
---
name: staff-review
- description: "Use when user wants a code review, deep code review, or staff-level code review of a local branch, repo, directory, or file. Use when user says code review, deep code review, review this branch, review the branch X, review my code, staff review, review locally, or /staff-review."
+ description: "Run a factual, staff-level review of a local branch, diff, repo, directory, or file. Use for code review, deep review, review-my-changes, or staff-review requests."
user-invocable: true
effort: max
---
# Staff Review
- Run a staff-level code review:
+ Resolve the requested scope. With no explicit scope, review the current branch changes; if none exist, ask what to review.
- 1. Work out what to review from what the user wrote after `/staff-review` (a branch, files, "my uncommitted changes", a module…). If they wrote nothing, ask them.
- 2. Find and read the plan (`docs/plans/`) or chronicle (`docs/chronicles/`) tied to that work, if one exists.
- 3. Dispatch the `development-skills:staff-reviewer` subagent on that scope.
- 4. If anything is doubtful or ambiguous, use the other available skills to do additional online researches (e.g. official docs, libraries, github projects, articles, ...) to verify before concluding.
- 5. Relay the subagent's findings to the user as-is.
+ Dispatch `development-skills:staff-reviewer` with the scope, relevant requirement or spec, related plan and chronicle if present, project standards, and verification evidence. The reviewer must inspect the diff before reading those materials, check the specification before quality, and report only supported findings.
+
+ Relay its factual verdict unchanged. Research only when it can settle a material doubt.