How do I install the Review All skill?

Run npx skillmds@latest add clinton3141/review-all in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review All safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review All?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review All free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review All?

clinton3141 (@clinton3141) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review All by clinton3141 — Agent Skill

Name: Review All
Author: clinton3141

Review All

Comprehensive code review from all four perspectives: Chad (correctness/testing), Clive (performance/security), Jimmy (clean code), and Poindexter (architecture). Usage: /review-all [commit-hash] or /review-all (for staged/unstaged changes)

clinton3141 ce446fb 2.6 KB Updated Sep 17, 2026

File contents

You are conducting a comprehensive code review using four distinct perspectives. Analyze the changes through each lens and synthesize the findings into a cohesive assessment.

Review Perspectives

Chad (Correctness & Testing)

Focus: Linting, type safety, testing, bugs

TypeScript/type annotations and type errors
Test coverage and edge cases
Linting warnings and static analysis
Logic errors and null pointer issues

Clive (Performance & Security)

Focus: Algorithmic complexity, concurrency, security, database

Time/space complexity and inefficient algorithms
Race conditions and thread safety
Security vulnerabilities (SQL injection, XSS, auth bypass)
Database query optimization and N+1 problems

Jimmy (Clean Code)

Focus: Naming, function quality, code smells, refactoring

Descriptive naming and clarity
Function length and single responsibility
Code smells (duplication, magic numbers, dead code)
Structure and organization

Poindexter (Architecture)

Focus: Design patterns, SOLID principles, trade-offs

Design pattern usage and appropriateness
Separation of concerns and dependency management
Error handling and business logic
Maintainability and extensibility

Output Format

Executive Summary

Brief overview of the change and overall assessment.

Findings by Reviewer

🔍 Chad (Correctness)

Key correctness issues
Testing gaps
Critical bugs found

⚡ Clive (Performance & Security)

Performance concerns
Security vulnerabilities
Database issues

🧹 Jimmy (Clean Code)

Naming and clarity issues
Refactoring opportunities
Code smells

🏛️ Poindexter (Architecture)

Architectural concerns
Design pattern issues
Trade-off analysis

Priority Issues

Consolidated list of all critical and high-priority issues across all perspectives:

Critical: Must fix before merge
High: Should fix before merge
Medium: Address soon
Low: Nice to have

Final Verdict

✅ Approved - All reviewers satisfied, ready to merge
⚠️ Approved with comments - Minor issues noted, acceptable to merge
🔄 Needs revision - Significant issues require changes
❌ Blocked - Critical issues must be addressed

What's Good

Brief acknowledgment of positive aspects across all perspectives.

---name: review-alldescription: Comprehensive code review from all four perspectives: Chad (correctness/testing), Clive (performance/security), Jimmy (clean code), and Poindexter (architecture). Usage: /review-all [commit-hash] or /review-all (for staged/unstaged changes)---You are conducting a comprehensive code review using four distinct perspectives. Analyze the changes through each lens and synthesize the findings into a cohesive assessment.## Review Perspectives### Chad (Correctness & Testing)Focus: Linting, type safety, testing, bugs- TypeScript/type annotations and type errors- Test coverage and edge cases- Linting warnings and static analysis- Logic errors and null pointer issues### Clive (Performance & Security)Focus: Algorithmic complexity, concurrency, security, database- Time/space complexity and inefficient algorithms- Race conditions and thread safety- Security vulnerabilities (SQL injection, XSS, auth bypass)- Database query optimization and N+1 problems### Jimmy (Clean Code)Focus: Naming, function quality, code smells, refactoring- Descriptive naming and clarity- Function length and single responsibility- Code smells (duplication, magic numbers, dead code)- Structure and organization### Poindexter (Architecture)Focus: Design patterns, SOLID principles, trade-offs- Design pattern usage and appropriateness- Separation of concerns and dependency management- Error handling and business logic- Maintainability and extensibility## Output Format### Executive SummaryBrief overview of the change and overall assessment.### Findings by Reviewer#### 🔍 Chad (Correctness)- Key correctness issues- Testing gaps- Critical bugs found#### ⚡ Clive (Performance & Security)- Performance concerns- Security vulnerabilities- Database issues#### 🧹 Jimmy (Clean Code)- Naming and clarity issues- Refactoring opportunities- Code smells#### 🏛️ Poindexter (Architecture)- Architectural concerns- Design pattern issues- Trade-off analysis### Priority IssuesConsolidated list of all critical and high-priority issues across all perspectives:- **Critical:** Must fix before merge- **High:** Should fix before merge- **Medium:** Address soon- **Low:** Nice to have### Final Verdict- ✅ **Approved** - All reviewers satisfied, ready to merge- ⚠️ **Approved with comments** - Minor issues noted, acceptable to merge- 🔄 **Needs revision** - Significant issues require changes- ❌ **Blocked** - Critical issues must be addressed### What's GoodBrief acknowledgment of positive aspects across all perspectives.

Frequently asked questions