Manually trigger a review cycle for a specific task or the current IN_REVIEW task. Use when asked to review a task, run reviewers, or check review status.
Installs into .claude/skills of the current project.
Are you the author of Review?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/orodruinlabs-review)
---
name: nazgul:review
description: Manually trigger a review cycle for a specific task or the current IN_REVIEW task. Use when asked to review a task, run reviewers, or check review status.
context: fork
allowed-tools: Read, Bash, Glob, Grep
metadata:
author: Jose Mejia
version: 1.2.2
---
# Nazgul Review
## Examples
- `/nazgul:review` — Review the current IN_REVIEW task
- `/nazgul:review TASK-003` — Review a specific task by ID
## Current State
- Config: !`cat nazgul/config.json 2>/dev/null || echo "No config"`
- Active reviewers: !`jq -r '.agents.reviewers // [] | join(", ")' nazgul/config.json 2>/dev/null || echo "none"`
- Plan: !`head -20 nazgul/plan.md 2>/dev/null || echo "No plan"`
## Arguments
$ARGUMENTS
## Instructions
Format all output per `references/ui-brand.md` — use stage banners, review verdicts, spawning indicators, and display patterns defined there.
### If a task ID is provided in arguments:
1. Read the task manifest at `nazgul/tasks/[TASK-ID].md`
2. Verify the task is in IMPLEMENTED or IN_REVIEW status
3. Delegate to the Review Gate agent for that task
### If no task ID provided:
1. Scan `nazgul/tasks/` for any task with status IMPLEMENTED or IN_REVIEW
2. If found, delegate to the Review Gate for that task
3. If none found, report that no tasks are ready for review
### Review Process
1. The Review Gate runs pre-checks (tests, lint)
2. Each reviewer evaluates the changed files
3. Reviews are written to `nazgul/reviews/[TASK-ID]/`
4. Consolidated feedback (if rejection) written to `nazgul/reviews/[TASK-ID]/consolidated-feedback.md`
5. Display the verdict and any blocking issues
