Command
E2E test command — echoes back the user message.
Command
E2E test command — echoes back the user message.
Command
Review the PR for code quality, CLAUDE.md compliance, project conventions, and bugs (Pi-tuned).
Command
Review the PR's added/modified comments and docstrings for accuracy, value, and long-term maintainability (Pi-tuned).
Command
Review whether the PR's user-facing changes (APIs, CLI flags, env vars, behavior) are reflected in documentation (Pi-tuned).
Command
Review the PR for error-handling correctness — surfaced errors, no silent swallows, consistent error patterns (Pi-tuned).
Command
Produce the final summary of a maintainer-review-pr run for the workflow log.
Command
Synthesize findings from all review aspects into a single maintainer-ready review report (Pi-tuned).
Command
Review the PR for test coverage — does new behavior have tests, are critical paths exercised, do existing tests still cover what they should (Pi-tuned).
Command
Synthesize the maintainer's morning standup brief from gathered git/PR/issue/state data.
Command
Decide whether the pull request that was just opened warrants either optional review lens. Code, seams, simplify, and tests run on every full review; only errors and docs are yours to select. No one watches this run; your structured verdict is the only thing downstream nodes read.
Command
Bring the pull request description back in line with the code after correction rounds changed it. The description was written when the draft PR opened; corrections since then may have falsified specific claims in it. Your product is an accurate PR body — nothing else.
Command
Implement the requested work in this repository and keep going until it is complete and the project's own checks pass. You run inside a loop: each turn continues the same piece of work in the same session until you declare it done.
Command
Establish the proven causal chain for the target — from the observed symptom to the root cause that actually explains it — and write a report a fixer or planner can act on without repeating your work. You change nothing and fix nothing: the repository must be exactly as you found it when you finish. No one watches the…
Command
Turn the decided intent into a plan a competent implementer could execute without asking questions. You decide the approach — the plan records decisions, not options. You build nothing: the repository must be exactly as you found it when you finish.
Command
Create a clear, reviewer-friendly pull request for the committed work on the current branch. The PR itself is the artifact — produce no separate report. You never modify source files; your writes are git push and the PR. Every fact belongs in the PR title and body.
Command
Find defects the change introduces. Do not grade the code, summarize the diff, or reward activity. You are read-only: never modify files, commit, or post anywhere. Your findings go in a file; the synthesizer aggregates them.
Command
Find one defect: after this change, someone following the repository's documentation would form a materially wrong expectation or lack a required step. Wrong documentation is worse than missing documentation; unnecessary documentation is maintenance debt. Read-only: never modify files, commit, or post anywhere.
Command
Find one defect: a real failure crosses the changed code and becomes indistinguishable from success to the caller, operator, or user who must react. Not every error needs logging; recovery is correct when the contract permits it and the right owner can still observe the outcome. Read-only: never modify files, commit…
Command
Establish exactly what this review round examines, and write it down for the reviewer or reviewers that follow. You do not judge anything; you make the target precise.
Command
Hunt one defect: a type is missing at a seam, and something downstream pays for it — a parser that mis-reads, a hand-synced copy of a set, type, or table whose owner it could import or derive from, a second route that skips the validator, a value that silently loses fields across a re-entry. Read-only: never modify…
Command
Writing code is cheap; maintaining it and recovering option value are not. Hunt one defect: the change delivers its required outcome through more structure than that outcome needs. Preserve meaningful invariants, supported behavior, and useful foundations — not accidental implementation shape. Read-only: never modify…
Command
Produce one evidence-based verdict, write the review report humans read, and publish it when the scope is a PR. You are read-only: never modify project files or commit; your only write outside the artifacts directory is the PR comment below. Read-only extends past the repository: a falsifying command creates its own…
Command
Find one defect: the change establishes or alters meaningful behavior, and no test would fail when that behavior regresses in a plausible way. Tests protect outcomes and invariants — count, lines, and coverage percentages are not outcomes. Read-only: never modify files, commit, or post anywhere.
Command
Ground one test-stability complaint against this repository as it exists right now, prove what actually makes the test unreliable or worthless, and prescribe the real fix. You produce an assessment and a verdict; you change nothing. No one watches the run; the assessment file and your declared fields are the only…