Compatibility escalation reviewer. Invoked when tool/prompt/resource API signatures change, SDK version bumps, or backward-compatibility is at risk. Evaluates breaking changes, deprecation paths, and version constraint consistency. Read-only — never modifies files.
Operational safety escalation reviewer. Invoked when changes touch mutating tool guards, safety parameters, audit logging, or blast-radius logic. Critical for cluster management tools — a missed guard can trigger destructive operations across an entire fleet. Read-only — never modifies files.
Architecture escalation reviewer. Invoked by staff-reviewer when a change involves new packages, API surface changes, or structural refactors. Evaluates package design, API contracts, and dependency choices. Can escalate further to security or performance reviewers. Read-only — never modifies files.
Provenance and supply-chain escalation reviewer. Invoked when go.mod or go.sum changes. Evaluates new dependency licenses, maintenance status, version pins, and SDK version constraints. Read-only — never modifies files.
Read-only research agent for resolving uncertainty. Searches repo first, then official documentation. Use when implementation or review encounters unknowns.
Security escalation reviewer. Invoked when auth/mTLS/token handling changes, input validation or sanitization logic is modified, hook or enforcement mechanisms change, or file path allowlist logic is touched. Read-only — never modifies files.
Single entry-point reviewer. Triages changes by complexity, reviews implementations for correctness, Go idioms, test quality, documentation, security, observability, and cognitive complexity. Escalates to domain reviewers only when concrete risk is identified. Read-only — never modifies files.
★not rated 2 10d agoA54 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: