workflows-review

Identify code quality, security, and architectural issues across branch diffs.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/The-Rabak/naysmith --skill workflows-review-the-rabak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflows-review
Source: https://github.com/The-Rabak/naysmith/tree/main/.github/skills/workflows-review
Command: npx skills add https://github.com/The-Rabak/naysmith --skill workflows-review-the-rabak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines exhaustive code reviews by coordinating multiple AI agents and worktrees to surface issues and ensure high-quality diffs.

Core Features & Use Cases

  • Multi-agent analysis for comprehensive reviews across branches and files
  • Ultra-thinking synthesis to surface risks, security, and architectural concerns
  • Isolated analysis via git worktrees to keep reviews clean and reproducible
  • Structured findings and triage workflows with actionable TODOs

Quick Start

Specify the target branch or file and run the workflows-review skill to start a full multi-agent code review.

Frequently Asked Questions about workflows-review

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

FAQPage Schema
How do I automate multi-agent code reviews for a specific git branch?▼

Multi-agent code review is automated by coordinating isolated git worktrees to analyze diffs between the target and default branches. This process surfaces code quality issues, security concerns, and architectural risks while generating actionable TODOs.

Can I run an AI code review on specific files instead of an entire branch?▼

AI code review can target specific files or the full diff between the default and target branches. The multi-agent analysis evaluates the selected scope to identify and summarize security concerns and structural risks.

How does git worktree isolation improve AI code triage?▼

Git worktree isolation improves AI code triage by keeping the review environment clean and reproducible. By evaluating branches in isolated worktrees, parallel agents can safely analyze diffs without interfering with your primary working directory.

What is the best way to triage architectural risks in a pull request diff?▼

The best way to triage architectural risks in a pull request diff is using ultra-thinking synthesis to evaluate the changes. This approach surfaces deep structural concerns across the target branch and outputs structured recommendations.

Do I need any special dependencies to perform automated security reviews with worktrees?▼

No special dependencies are required to perform automated security reviews, but the environment must support git worktrees. The skill enforces safety by outlining required tooling and producing reproducible output artifacts like todo files.

What limitations exist when using parallel agents for code analysis?▼

A limitation of using parallel agents for code analysis is that the evaluation is strictly scoped to the diff between the default branch and the target branch, or specifically selected files, rather than evaluating the entire repository context.