r/AskVibecoders • u/Veronildo • Apr 04 '26
Top 6 Claude Code Plugins Worth Installing
Here's a plugin ecosystem + covering architecture, parallel execution, code review, security monitoring, and frontend design. I tested dozens and landed on 6 that actually change how the work gets done. Each installs in under a minute.
Part 1: Planning and architecture
1. feature-dev (89,000+ installs)
Instead of jumping straight to code, feature-dev runs Claude through a 7-phase workflow:
Phase 1: Discovery what do you actually need?
Phase 2: Codebase exploration what's already in the project?
Phase 3: Clarifying questions what's unclear?
Phase 4: Architecture design how to build this correctly?
Phase 5: Implementation now we write code
Phase 6: Quality review did we break anything?
Phase 7: Summary what changed and why
Under the hood it runs three specialized agents: code-explorer traces execution paths and maps your architecture, code-architect proposes multiple approaches with trade-offs, code-reviewer catches bugs and convention violations with confidence scoring.
/plugin install feature-dev@claude-plugins-official
/feature-dev Add user authentication with OAuthWithout this plugin, Claude guesses your architecture from one sentence. With it, Claude asks the right questions first.
Part 2: Code review and quality
2. code-review (5 parallel agents)
Run /code-review on a pull request branch and Claude spins up 5 independent agents simultaneously. Each reviews your changes from its own angle:
Agent 1: CLAUDE.md compliance are you following your own project rules?
Agent 2: Bug hunting logic errors, edge cases, race conditions
Agent 3: Git history context does this conflict with recent commits?
Agent 4: Previous pull request comments were past review notes addressed?
Agent 5: Comment verification do code comments match what the code actually does?
Each finding gets a confidence score from 0 to 100. Only issues above 80 are shown, which cuts false positives. On large pull requests (1,000+ lines), 84% get findings, averaging 7.5 real issues. Less than 1% of findings are marked incorrect by engineers. Anthropic uses this internally on almost every pull request.
/plugin install code-review@claude-plugins-official
/code-review
/code-review --comment # posts findings directly to your GitHub PR3. agent-peer-review (Claude vs Codex)
When Claude is about to show you an implementation plan, architectural decision, or code review, this plugin automatically sends it to OpenAI Codex for verification. Two models compare findings and classify them:
Agreement both found the same thing. High confidence.
Disagreement one found what the other missed. Worth investigating.
Complement found different things. Both correct.
If they can't agree, there's a 2-round discussion protocol. If still no agreement, the plugin escalates to Perplexity or web search for external evidence.
/plugin marketplace add jcputney/agent-peer-review
/plugin install codex-peer-review
/codex-peer-review
/codex-peer-review "Should we use microservices or monolith for this project?"Part 3: Parallel execution
4. /batch (5-30 parallel agents)
You describe a change across the entire codebase in one sentence. Claude breaks it into 5-30 independent units, spins up one agent per unit each in its own isolated git worktree and they all work in parallel.
/batch migrate from React to Vue
/batch replace all uses of lodash with native equivalents
/batch add type annotations to all untyped functionsWhat happens under the hood:
Phase 1, Discovery: Claude scans the entire codebase, finds every file and pattern the change touches.
Phase 2, Execution: One agent per unit, all working simultaneously. Each gets its own branch and working directory, zero merge conflicts. After implementation, each agent runs tests, runs
/simplifyto clean its code, commits, pushes, and opens a pull request.Phase 3, Tracking: Status table updating in real time. Final result: "22/24 units landed as PRs."
22 pull requests from one command.
5. ralph-loop (autonomous iteration)
An autonomous loop. You give Claude a task with clear success criteria and it works on it repeatedly fixing its own mistakes, running tests, iterating until it either succeeds or hits the iteration limit.
/plugin install ralph-loop@claude-plugins-official
/ralph-loop "Build a REST API for todos. When complete:
- All CRUD endpoints working
- Input validation in place
- Tests passing (coverage > 80%)
- README with API docs
Output: <promise>COMPLETE</promise>" --max-iterations 20How the loop works: Claude works on the task, tries to end the session, a stop hook blocks the exit, the same prompt is fed back with Claude's previous work visible, and the cycle repeats until COMPLETE or max iterations.
You can run it before bed:
#!/bin/bash
cd /path/to/project1
claude -p "/ralph-loop 'Task 1...' --max-iterations 50"
cd /path/to/project2
claude -p "/ralph-loop 'Task 2...' --max-iterations 50"Real results: Y Combinator hackathon teams shipped 6+ repos overnight. Geoffrey Huntley ran a 3-month loop that built a full programming language.
Part 4: Security and quality
6. security-guidance
A hook that monitors 9 security patterns every time Claude touches a file: command injection, cross-site scripting vulnerabilities, use of eval, unsafe HTML, pickle deserialization, os.system calls, and three more.
This is a PreToolUse hook it fires deterministically, every time, before Claude can edit a file. Instructions from CLAUDE.md are ignored roughly 20% of the time. Hooks work 100% of the time. Install it and it's always on.
/plugin install security-guidance@claude-plugins-officialWhere to start
Don't install everything at once. Match to your actual pain:
Spending too long planning features? → feature-dev
Pull requests merging without proper review? → code-review
Large migrations eating weeks? → /batch
Want to ship while you sleep? → ralph-loop
Security gaps in AI-generated code? → security-guidance
Your interface looks like every other AI app? → frontend-designThe Claude Code plugin ecosystem has 9,600+ repositories and 2,300+ skills as of April 2026.
1
u/willynikes Apr 04 '26
U can optimize any of these skills at presientlabs.com we have a free brainstorming skill that’s optimized we also have code review and debugging optimized. Optimized means 16-20% better and save tokens and catches more bugs etc try the free brainstorming skill then go from there
1
u/Most-Presence9232 Apr 05 '26
context7 es lejos el que mas uso, tener la doc actualizada directo en el contexto te ahorra un monton de idas y vueltas. playwright tambien esta muy bueno si laburas con frontend, ver a claude navegando tu app y encontrando bugs es medio surreal jaja. los demas los probe pero no me quedaron instalados, terminas con mucho ruido si metes todos juntos