~ / rigs / NYTC69 / review-loop

NYTC69/review-loop

Automates plan → implement → review iteration loops using multiple AI agents.

↗ GitHub ★ 3 Apache-2.0 updated 24d ago project Claude Code Claude plugin
stack: Python
share on X
ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
CONTEXT TAX · EVERY TURN
~3.7k tokens
Moderate · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 0/100 Guardrails v2

Copy this rig

# review before running: this installs third-party code
$ npx degit NYTC69/review-loop/agents ./rig-review-loop/agents
$ npx degit NYTC69/review-loop/skills ./rig-review-loop/skills

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit NYTC69/review-loop/.agents/skills/guide .claude/skills/guide
$ npx degit NYTC69/review-loop/.agents/skills/paired-session .claude/skills/paired-session
$ npx degit NYTC69/review-loop/.agents/skills/review-loop .claude/skills/review-loop
$ npx degit NYTC69/review-loop/.agents/skills/review-pr .claude/skills/review-pr
$ npx degit NYTC69/review-loop/skills/code-quality-loop .claude/skills/code-quality-loop
$ npx degit NYTC69/review-loop/skills/reorganize .claude/skills/reorganize
$ curl -fsSL --create-dirs -o .claude/agents/code-reviewer.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/code-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/code-simplifier.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/code-simplifier.md
$ curl -fsSL --create-dirs -o .claude/agents/comment-analyzer.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/comment-analyzer.md
$ curl -fsSL --create-dirs -o .claude/agents/executor.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/executor.md
$ curl -fsSL --create-dirs -o .claude/agents/frontend-security-reviewer.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/frontend-security-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/go-reviewer.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/go-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/pr-test-analyzer.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/pr-test-analyzer.md
$ curl -fsSL --create-dirs -o .claude/agents/python-reviewer.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/python-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/reviewer.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/rust-reviewer.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/rust-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/silent-failure-hunter.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/silent-failure-hunter.md
$ curl -fsSL --create-dirs -o .claude/agents/type-design-analyzer.md https://raw.githubusercontent.com/NYTC69/review-loop/main/agents/type-design-analyzer.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

Skills (6)

Subagents (12)

code-reviewer
model: inherit
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially bef
code-simplifier
model: inherit
Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automa
comment-analyzer
model: inherit
Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes after generating large documentation comments, before finalizing code tha
executor
model: inherit
>
frontend-security-reviewer
model: inherit
Review frontend code for common web security vulnerabilities. Use before committing or creating PRs for frontend code.
go-reviewer
model: inherit
Run Go static analysis tools and generate a categorized review report. Use before committing or creating PRs for Go code.
pr-test-analyzer
model: inherit
Use this agent when you need to review code for test coverage quality and completeness. This agent should be invoked after code is written or updated to ensure tests adequately cover new functionality
python-reviewer
model: inherit
Run Python static analysis tools and generate a categorized review report. Use before committing or creating PRs for Python code.
reviewer
model: inherit
>
rust-reviewer
model: inherit
Run Rust static analysis tools and generate a categorized review report. Use before committing or creating PRs for Rust code.
silent-failure-hunter
model: inherit
Use this agent when reviewing code changes to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoked proactively after completing work that involves error ha
type-design-analyzer
model: inherit
Use this agent when you need expert analysis of type design in your codebase. Specifically use it when introducing a new type to ensure it follows best practices for encapsulation and invariant expres

Similar rigs

copied ✓