ln-513-agent-reviewer
Runs parallel agent reviews on code changes to provide verified, filtered improvements.
Install
mkdir -p .claude/skills/ln-513-agent-reviewer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14475" && unzip -o skill.zip -d .claude/skills/ln-513-agent-reviewer && rm skill.zipInstalls to .claude/skills/ln-513-agent-reviewer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Runs parallel external agent reviews (Codex + Gemini) on code changes. Process-as-arrive, critical verification with debate. Returns filtered suggestions.Key capabilities
- →Run parallel external agent reviews on code changes
- →Critically verify suggestions from review agents
- →Deduplicate and filter verified suggestions
- →Score improvements with confidence and impact
- →Health check and prompt execution in a single invocation
- →Resolve story IDs from arguments, git branches, or kanban
How it works
This skill orchestrates parallel code reviews by external agents (Codex + Gemini), processes their suggestions as they arrive, and critically verifies them before returning a filtered list.
Inputs & outputs
When to use ln-513-agent-reviewer
- →Reviewing code changes for quality
- →Ensuring implementation matches requirements
- →Automating technical debt cleanup verification
About this skill
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.
Agent Reviewer (Code)
Runs parallel external agent reviews on code implementation, critically verifies suggestions, returns filtered improvements.
Purpose & Scope
- Worker in ln-510 quality coordinator pipeline (invoked by ln-510 Phase 4)
- Run codex-review + gemini-review as background tasks in parallel
- Process results as they arrive (first-finished agent processed immediately)
- Critically verify each suggestion; debate with agent if Claude disagrees
- Return filtered, deduplicated, verified suggestions with confidence scoring
- Health check + prompt execution in single invocation
When to Use
- Invoked by ln-510-quality-coordinator Phase 4 (Agent Review)
- All implementation tasks in Story status = Done
- Code quality (ln-511) and tech debt cleanup (ln-512) already completed
Parameters
| Parameter | Value |
|---|---|
review_type | codereview |
skill_group | 513 |
prompt_template | shared/agents/prompt_templates/code_review.md |
verdict_acceptable | CODE_ACCEPTABLE |
Inputs
| Input | Required | Source | Description |
|---|---|---|---|
storyId | Yes | args, git branch, kanban, user | Story to process |
Resolution: Story Resolution Chain. Status filter: In Progress, To Review
Workflow
MANDATORY READ: Load shared/references/input_resolution_pattern.md, shared/references/tools_config_guide.md, shared/references/storage_mode_detection.md, shared/references/agent_review_workflow.md, and shared/references/agent_delegation_pattern.md.
Phase 0: Resolve Inputs & Tools Config
-
Resolve storyId (per input_resolution_pattern.md):
- IF args provided → use args
- ELSE IF git branch matches
feature/{id}-*→ extract id - ELSE IF kanban has exactly 1 Story in [In Progress, To Review] → suggest
- ELSE → AskUserQuestion: show Stories from kanban filtered by [In Progress, To Review]
-
Extract:
task_providerfromdocs/tools_config.md(per tools_config_guide.md).
Unique Steps (before shared workflow)
-
Health check: per shared workflow, filter by
skill_group=513. -
Get references:
- IF
task_provider=linear:get_issue(storyId)→ extract URL + identifier.list_issues(filter: {parent: {id: storyId}, status: "Done"})→ extract Done implementation Task URLs/identifiers (exclude label "tests"). - IF
task_provider=file:Read story.md→ extract path.Glob("docs/tasks/epics/*/stories/*/tasks/*.md")→ filter Done tasks (check**Status:** Done), exclude label "tests".
- IF
-
Ensure .agent-review/: per shared workflow.
-
Build prompt: Read template
shared/agents/prompt_templates/code_review.md.- Replace
{story_ref}with- Linear: {url}or- File: {path} - Replace
{task_refs}with bullet list:- {identifier}: {url_or_path}per task - Save to
.agent-review/{identifier}_codereview_prompt.md(single shared file -- both agents read the same prompt)
- Replace
Shared Workflow Steps
5-8) Load Review Memory, Run agents, Critical Verification + Debate, Aggregate + Return: per shared workflow.
{review_type}= "Code Implementation" (for challenge template)
- Save Review Summary: per shared workflow "Step: Save Review Summary".
Output Format
verdict: CODE_ACCEPTABLE | SUGGESTIONS | SKIPPED
suggestions:
- area: "security | performance | architecture | correctness | best_practices"
issue: "What is wrong"
suggestion: "Specific fix"
confidence: 95
impact_percent: 15
source: "codex-review"
resolution: "accepted | accepted_after_debate | accepted_after_followup | rejected"
Agent stats and debate log per shared workflow output schema.
Fallback Rules
Per shared workflow, plus:
| Condition | Action |
|---|---|
| Parent skill (ln-510) | Falls back to Self-Review (native Claude) |
Verdict Escalation
- Findings with
area=securityorarea=correctness-> parent skill can escalate PASS -> CONCERNS - This skill returns raw verified suggestions; escalation decision is made by ln-510
Critical Rules (additional)
- MANDATORY INVOCATION: Parent skills MUST invoke this skill. Returns SKIPPED gracefully if agents unavailable. Parent must NOT pre-check and skip.
Reference Files
- Tools config:
shared/references/tools_config_guide.md - Storage mode operations:
shared/references/storage_mode_detection.md - Shared workflow:
shared/references/agent_review_workflow.md - Agent delegation pattern:
shared/references/agent_delegation_pattern.md - Prompt template (review):
shared/agents/prompt_templates/code_review.md - Challenge schema:
shared/agents/schemas/challenge_review_schema.json
Version: 2.0.0 Last Updated: 2026-02-11
When not to use it
- →When the implementation tasks are not in 'Done' status
- →When code quality and tech debt cleanup are not yet completed
- →When not invoked by `ln-510-quality-coordinator` Phase 4
Limitations
- →This skill is invoked specifically by `ln-510-quality-coordinator` Phase 4.
- →It requires all implementation tasks to be in 'Done' status.
- →It expects code quality and tech debt cleanup to be completed prior to invocation.
How it compares
This workflow automates and parallelizes code review with critical verification, providing structured feedback unlike manual or single-agent reviews.
Compared to similar skills
ln-513-agent-reviewer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ln-513-agent-reviewer (this skill) | 0 | 5mo | No flags | Advanced |
| requesting-code-review | 5 | 3mo | Review | Intermediate |
| bat | 0 | 6mo | Review | Intermediate |
| flow-next-prime | 0 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Rieki777
View all by Rieki777 →You might also like
requesting-code-review
obra
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
bat
homeassistant-ai
Run bot acceptance tests to validate MCP tools work correctly from a real AI agent's perspective. Use when testing PRs, detecting regressions, or verifying tool changes end-to-end with Claude/Gemini CLIs.
flow-next-prime
gmickel
Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.
skill-creator
anthropics
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.