One command gives your AI-generated codebase a full senior engineering team. Saves $20-40/day in tokens. Finds and fixes every problem.
npx vibe-crew
From zero to a fully audited codebase in under 5 minutes. Follow every step below.
vibe-crew works inside Claude Code (Anthropic's CLI for Claude). Make sure you have these installed:
Required to run npx and the CLI
The AI coding CLI from Anthropic
Any project with code in it. We detect 15+ stacks automatically.
Claude Code needs this to run agents. Set it in your environment.
Pick a plan below and complete checkout. Your license key will be emailed to you immediately. It looks like this:
Check your inbox (and spam folder) for an email from noreply@picvaultpro.com with the subject "Your CodeCrew license key".
Want to preview first? Run npx vibe-crew --dry-run to see what agents would be generated for your project, without needing a license key.
Open your terminal, navigate to your project directory, and run:
This does three things at once:
1. Saves your license to ~/.vibe-crew/license so you never need to enter it again
2. Scans your codebase to detect your framework, database, auth, payments, and more
3. Generates your agent team with specialized agents tailored to your exact stack
Your key works on all your projects. Once activated, just run npx vibe-crew (no --key flag) in any new project. The license is stored globally.
The CLI will output everything it finds and creates. Here's what a typical run looks like:
The generated files go into your project's .claude/ directory:
Start Claude Code in your project directory. Your new slash commands are ready immediately:
This is where the magic happens. Inside Claude Code, type:
The audit team will:
1. Scan every file in your project for issues
2. Categorize findings: security, performance, dead code, patterns, architecture
3. Fix each issue automatically with the appropriate agent
4. Validate every fix passes build + tests via the build-gate agent
5. Report a summary of everything found and fixed
First audit can take 5-15 minutes depending on codebase size. Subsequent runs are much faster thanks to caching.
vibe-crew configures hooks so certain agents trigger without you doing anything:
You can customize which agents auto-trigger by editing .claude/settings.json in your project.
Reddit knows the feeling. Here's what developers are saying:
"I have this constant low-grade anxiety that somewhere in the codebase there's a function that's one wrong input away from catastrophic failure."
"Built my SaaS in 3 days. Last week I sat down to add one small feature. One day gone. 30k lines I can't navigate."
"Each fix introduces two new problems because the LLM has no memory of why it made those architectural decisions."
"If you've vibe coded Supabase Row Level Security and it actually works, you're lying."
ESLint is spell-check. This is an editorial board.
Three steps. Five minutes. Zero config.
Detects your language, framework, database, auth, payments, storage, mobile — everything. Works with Next.js, Python, Go, Rust, Swift, and 15+ stacks.
Creates specialized AI agents tailored to YOUR stack. Build gate, QA signoff, security reviewer, orchestrator — each knows your tools.
Sends the team through your codebase. Finds dead code, security holes, bad patterns. Fixes everything to 95% confidence. Writes a report.
/vibe-audit
Full codebase scan. Finds every problem. Fixes them all. Validates the build. 95% confidence.
/vibe-review
Quick check — are your agents right for this codebase? Coverage gaps? Wrong tiers?
/vibe-launch
Give it multiple problems. Each gets its own orchestrator with 3 solutions. Wake up to fixes.
/vibe-init
Re-run setup. Regenerate agents after your codebase evolves.
Your agents repeat each other's work. The cache fixes that.
The preview is free. The full tool pays for itself in an hour.
Everything you need to know about vibe-crew.
.claude/ directory in your project containing: agent definitions (Markdown files that tell Claude Code how each specialized agent behaves), a settings.json with auto-trigger hooks, and a CLAUDE.md with project-level instructions. These are plain text files you can read, edit, and commit to your repo.
npx vibe-crew setup command only writes files inside .claude/. It never touches your source code. However, when you run /vibe-audit inside Claude Code, the audit agents will make changes to fix the issues they find. You can review every change before accepting it, just like any Claude Code edit.
noreply@picvaultpro.com. The email is sent immediately after Stripe checkout completes. If you still can't find it after 5 minutes, email support@picvaultpro.com with your checkout email address and we'll resend your key.
~/.vibe-crew/license. Once activated, run npx vibe-crew in any project directory and it will generate agents for that project automatically. No per-project limits.
npx vibe-crew --dry-run in your project directory. This scans your codebase and shows you exactly which agents would be created, what they'd do, and which Claude model tier each would use — without writing any files or requiring a license key.
.claude/settings.json in your project. You'll see a hooks section that maps file patterns to agents. Remove an entry to stop that agent from auto-triggering, or add new patterns. You can also edit the agent Markdown files in .claude/agents/ to change what each agent does.
/vibe-init inside Claude Code, or run npx vibe-crew again from your terminal. Both will re-scan your codebase and update the agent definitions to match your current stack.
support@picvaultpro.com with your account email and we'll cancel immediately. Your agents and slash commands continue to work (those are local files), but the cache server will be deprovisioned at the end of your billing period.
support@picvaultpro.com. Starter licenses (one-time payment) never expire.
support@picvaultpro.com. Include the output of npx vibe-crew --dry-run so we can see your stack detection results.
One command. Zero config. Start in 30 seconds.
npx vibe-crew --dry-run