Load when reviewing a diff, classifying findings, or returning a verdict.
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/reviewer/SKILL.mdProblems with a kendex-owned skill go through kendex report; check ownership in the file first.
Shared contract for every review specialist; each agent's domain and probes live in its own agent file. These workflows run orch scripts and do not stand alone.
| Workflow | Purpose |
|---|---|
workflows/review.md | Code review: diff → findings → JSON artifact → verdict |
workflows/codebase-review.md | Whole-codebase audit, no diff |
workflows/qa-review.md | QA label-triggered review of one PR |
Read references/finding-disposition.md before classifying findings. It owns verification, dispositions, recurrence and the filing bar. Orch owns execution and counters. Project-management owns issue creation.
Run scripts/review-depth --base REF --head REF --repo DIR from the trusted base checkout to select package review depth for a pull-request range. The command reads the class through change-scope's reader. review-depth --help owns its class mapping, output and failure contract. Every result leaves GitHub's native approval requirements in force.
measurement_failed under Measurement Claims.owner field.Issue:, apply project-management SKILL.md § Disposition to its Post-merge: Done-when boxes. Raise a fix suggestion for any box that fails that rule.schemas/review-finding.md description row places it.fix suggestion to remove it, or a PR-body note saying why it is needed: a landing enabler or a defect the change introduces or arms, as dev SKILL.md § Engineering Rules lists.--help, SKILL.md, CHANGELOG entry, comment, or diagnostic that claims program behavior, find the code that makes it true. None found is a blocker on the claim.../docs-writing/SKILL.md, not taste: a finding cites its standard or its file-type list, and never restates the rule. Source comments stay code-quality § Comments and Prose.reviewer-read-only refuses edits, writes into a repository, commits, pushes and Git discard commands. Where installed and running, reviewer-stop-check checks the required report. It attributes a tracked edit only when it can match the path to a successful mutation by that reviewer. Its stop instruction keeps the required report. The harnesses: headers of hooks/reviewer-read-only.sh and hooks/reviewer-stop-check.sh name the harnesses that run each hook. The reviewer upholds any part of the rule the hooks cannot enforce. The reviewer reads the worktree and its build output where they sit, and never copies the worktree directory, its target/ or its node_modules/. Follow code-quality § Prove Your Guards for controls and mutation-stability.md § 1 for any probe that needs a revision copy.AGENTS.md Read-when line routes for a subject the changed code implements, not only for its folder (docs-writing § Reference rules). Apply author-directed routes to the review: take the doc's rules one at a time and ask whether the change alters what the rule governs, such as a field added to a persisted format, a source with a tracked copy, or a value another component reads. For each rule it does, find the change the rule requires at the head, in the diff or not. A required file the diff leaves unchanged, such as a format version or a tracked render, is the breach. A rule over a set, such as every tracked render of a source, is checked against the inventory that lists the set, never against the members the diff touches. Report a breached rule with the doc's section, and name in the artifact's summary each routed doc read with the rules the change alters.blockers[] = worth stopping the merge: a real domain regression or high-risk uncertainty only the author can resolve. suggestions[] = actionable now (fix) or worth tracking (issue). Cosmetic items belong in neither. pass means your domain has no verified blocker in scope.Capture the starting fields before reviewing. Findings are a JSON artifact per schemas/review-finding.md, written with the harness file-write tool, never shell redirection, to the delegation's Artifact: path. That path must use the canonical form [WORKTREE_PATH]/tmp/review-[AGENT]-YYYYMMDD-HHMMSS.json, minted by orch-runtime review-artifact --text path and read by hooks/reviewer-stop-check.sh. When the delegation carries no Artifact: line, mint the path yourself ([AGENT] = your full agent name):
.agents/skills/orch/scripts/orch-runtime review-artifact --text path --worktree [WORKTREE_PATH] --agent [AGENT]Self-validate before returning, on the file you wrote, never the zero-epoch glob form, which falls through to an older sibling. Fix until this prints "ok": true:
.agents/skills/orch/scripts/orch-runtime review-artifact --text check --file [ARTIFACT_PATH] --worktree [WORKTREE_PATH]Write a control's files under a mktemp -d of your own, on the base § Ethos gives a copy, the way scripts/mutation-stability does: stubs, fixtures, mutants, logs. The scratchpad root is shared with the parallel panel, where a sibling overwrites a fixed name mid-review.
Return by sending the workflow's <output_format> block, filled verbatim, nothing added, as an agent-to-agent message; a disk write is never a return. Shell commands follow orch SKILL.md § Harness-Safe Shell.
Items the delegation lists as resolved are not re-reported, unless you check a Fixed item against the current diff and the defect is still there. Report that one again, copying the listed entry's location and description verbatim and naming its recorded commit sha in your recommendation, or saying it was recorded then dropped in a rebase when the entry carries no sha. A Fixed item you did not check, and every Escalated or Declined item, stays suppressed.
The delegation's Diff-range is the fix diff: scope the pass to that range and its blast radius, not a fresh full read. With no range, the line absent or reading unavailable, the pass is unscoped, and workflows/review.md § 1 owns what it reads and what it declares. Sweep every fixed defect's class before passing.
Judge control evidence under code-quality § Tests and § Prove Your Guards. Use this command when the required control evidence is missing or a reachable concurrency failure needs repeated measurements. Existing sufficient evidence needs no new run. In a re-review, consider only instruments the fix diff adds or changes.
Read mutation-stability.md before preparing or running this probe.
--build.vanillagreencom/kendex
568be42
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.