ankyr-reviewer

Reviews code diffs with specialist lenses and posts inline findings on GitHub pull requests.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/GuyErreich/AI_Agents --skill ankyr-reviewer-guyerreich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ankyr-reviewer
Source: https://github.com/GuyErreich/AI_Agents/tree/main/plugins/ankyr-review/skills/ankyr-reviewer
Command: npx skills add https://github.com/GuyErreich/AI_Agents --skill ankyr-reviewer-guyerreich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code reviews often miss domain-specific bugs, security threats, and regressions because a single shallow pass cannot cover frontend, backend, graphics, and TypeScript concerns at once. This Skill performs a rigorous single-pass staff-level review that routes changed files to specialist lenses and enforces logic, threat, and coverage gates before any clean verdict. ## Core Features & Use Cases - Capability-based routing: Maps changed files to standards and specialist lenses (frontend, backend, realtime-graphics, motion-vfx, typescript) so every diff gets domain-appropriate scrutiny without spawning nested subagents. - Multi-phase gates: Runs logic/regression, threat-model, and thoroughness passes that block false "Review passed" verdicts until every changed file is actually read and validated. - GitHub PR integration: Posts one review with concise inline comments per finding via gh CLI or GitHub MCP, while keeping the full findings table in chat and never posting noise on clean passes. - Use Case: Before opening a PR on a React + Supabase branch, run the reviewer to catch a missing RLS policy, a stale closure in a hook, and an undisposed Three.js geometry, then post the findings inline on the PR. ## Quick Start Ask the assistant to review the current branch as a PR using the ankyr-reviewer skill and post any findings inline on the open pull request.

Frequently Asked Questions about ankyr-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request with inline GitHub comments?▼

Run the review on the pr tier, which diffs merge-base...HEAD across the full branch. When findings exist, it posts one PR review with an inline comment per finding using gh CLI or GitHub MCP; clean passes stay in chat only.

What does a staff-level code review checklist cover?▼

It covers contracts between callers and callees, state and effect correctness, accessibility blockers, resource lifetime, security threat paths, and logic regressions. Each finding must name a concrete failure mode with severity and file location.

Can this review TypeScript, React, and Three.js code in one pass?▼

Yes. Changed files are routed to matching specialist lenses (typescript, frontend, backend, realtime-graphics, motion-vfx) that all activate in a single pass, so mixed-stack diffs get domain depth without nested subagents.

Why does the review refuse to declare "Review passed"?▼

The thoroughness gate blocks clean verdicts until every non-trivial changed file is opened and checked, matching lenses are activated, hotspots from prior fixes are verified, and the Validate suite passes or is legitimately skipped.

Does the reviewer post comments on a clean pull request?▼

No. With zero findings it posts nothing on GitHub — no APPROVE, no status comment, no checklist. The clean verdict is reported in chat only to avoid contaminating the PR timeline.

When should I use debug-like or security analysis modes?▼

Use debug-like for deeper semantic and causality analysis where each finding needs observed behavior, expected contract, and causal why. Use security for auth, data, or secrets-heavy diffs where findings must include an abuse path.