npx claudepluginhub izzzzzi/izteam --plugin auditExecutes cleanup actions after user confirms what to delete. Handles safe removal with git backup. <example> Context: User confirmed features to delete user: "Delete rat-hypothesis" assistant: "Launching cleanup-executor for safe removal with git backup" </example>
Scans codebase for potentially unused or experimental features. Returns structured list for interactive review. <example> Context: User wants to clean up their vibe-coded project user: "Find dead code" assistant: "Launching feature-scanner to find potentially unused features" </example>
This agent should be used when auditing src/features/ directory for dead code, unused exports, and duplication. Triggers on: "audit features", "find dead code in features", "clean up features/", "check features for unused code". <example> Context: User wants to audit feature modules for cleanup user: "Check features for dead code" assistant: "Launching features-auditor to analyze unused exports and duplicates" </example>
This agent should be used when auditing src/server/ directory for dead code, API inconsistencies, and unused routers. Triggers on: "audit server", "find dead code in server", "clean up routers", "check API for unused endpoints". <example> Context: User wants to clean up server-side code user: "Check server for dead code" assistant: "Launching server-auditor to audit tRPC routers and services" </example>
This agent should be used when auditing src/stores/ directory for unused stores, redundant state, and Zustand patterns. Triggers on: "audit stores", "find unused stores", "clean up state management", "check Zustand stores".
This agent should be used when auditing src/design-system/ and UI components for unused components, style inconsistencies, and duplication. Triggers on: "audit design system", "find unused components", "clean up UI", "check design-system for dead code".
Deep analysis of a specific feature's usage across the codebase. Called when user needs more details before deciding. <example> Context: User said "not sure" about a feature user: "Tell me more about rat-hypothesis" assistant: "Launching usage-analyzer for detailed usage analysis" </example>
Architecture analysis, brainstorming, 12-Factor compliance, ADR generation, and LLM-as-judge comparison.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Adversarial multi-agent pipeline for Claude Code. GAN-style loops where generators produce artifacts, discriminators validate them, and feedback drives convergence.
AI-powered development workflow automation - Phase-based planning, implementation orchestration, preflight code quality checks with security scanning, ship-it workflow, and development principles generator for CLAUDE.md
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix)
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams