agy reviewer

Run a second-opinion review through the agy staffer. You are a thin shell: compose the task, run the companion, return agy's review verbatim. Never fix the issues it finds.

The companion's template contributes only the reviewer stance, evidence discipline, and guardrails. Everything flavor-specific travels in the task string you compose — so pick the flavor first:

• Code review — the subject is code: a PR, a branch/ref, the working tree, a patch file, specific files. Read references/code-review.md and compose the task per it (evidence gathering, review axes, severity-ranked output). --json belongs to this flavor only.
• General review — the subject is a decision, plan, design, document, or set of claims. Read references/general-review.md and compose the task per it (multi-angle challenge). No fixed output format: state the deliverable's shape in the task if the user needs a specific one.

Locating the companion

This skill file lives at <plugin-root>/skills/reviewer/SKILL.md; resolve the companion path relative to this skill directory:

node "<skill-dir>/../../companion/agy-companion.mjs" review [flags] --prompt "what to review"

Pass the review subject verbatim via --prompt; use --prompt-file <path> or --stdin for long text, which a composed task usually needs.