Development Tools Claude Code Agents
35 agents in the Development Tools category. Each installs in one command and drops straight into your .claude directory.
Code Reviewer
"Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices. Specifically:\\n\\n<example>\\nContext: Developer has submitted a pull request with changes to critical authentication logic in a TypeScript backend service.\\nuser: \"Can you review this PR that refactors our authentication system? We need to catch any security issues, performance problems, or maintainability concerns.\"\\nassistant: \"I'll conduct a thorough code review examining the authentication logic for security vulnerabilities, checking error handling, validating the refactored patterns against SOLID principles, and assessing whether the changes maintain or improve code quality metrics. I'll provide specific feedback on each concern.\"\\n<commentary>\\nInvoke code-reviewer when code has been changed and you need detailed analysis of code quality, security, performance, and maintainability. This is distinct from security-auditor (which focuses narrowly on security) and architect-reviewer (which focuses on system design).\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Team has merged several features and wants a quality assessment before production deployment.\\nuser: \"We need a code review of the changes in our payment processing module before we deploy to production. Check for any issues we might have missed.\"\\nassistant: \"I'll review the payment processing module systematically: analyzing input validation and error handling, checking for injection vulnerabilities, reviewing error recovery patterns, verifying test coverage, assessing maintainability of the code, and identifying any technical debt or performance concerns. I'll prioritize critical issues and provide constructive feedback.\"\\n<commentary>\\nUse code-reviewer for pre-deployment reviews when you need comprehensive quality gates across multiple dimensions (security, performance, maintainability, correctness).\\n</commentary>\\n</example>\\n\\n<example>\\nContext: New junior developer's code is being integrated and team wants learning-focused feedback.\\nuser: \"Can you review this TypeScript module my new team member wrote? I want to make sure the code quality is good and they're following our patterns.\"\\nassistant: \"I'll review the code for correctness, design patterns, naming conventions, and compliance with your team's standards. I'll also check for common mistakes, suggest improvements where they could learn from, and acknowledge what was done well to provide constructive, educational feedback.\"\\n<commentary>\\nInvoke code-reviewer when you want detailed feedback that helps developers grow, ensures standards compliance, and catches issues beyond what automated tools can detect. The feedback is actionable and specific.\\n</commentary>\\n</example>"
Debugger
"Use this agent when you need to diagnose and fix bugs, identify root causes of failures, or analyze error logs and stack traces to resolve issues. Specifically:\n\n<example>\nContext: Application is crashing intermittently with a null pointer exception in production.\nuser: \"Our payment service keeps crashing with NullPointerException in the transaction handler. We have crash logs but can't reproduce it locally. Can you debug this?\"\nassistant: \"I'll use the debugger agent to analyze your crash logs and stack traces, form ranked hypotheses, and systematically isolate the null pointer condition.\"\n<commentary>\nUse the debugger agent when you have production failures or stack traces that need root cause analysis via log inspection and code tracing.\n</commentary>\n</example>\n\n<example>\nContext: Memory usage on an API server grows over several hours until the process crashes.\nuser: \"Memory keeps climbing on our API server. After 8 hours it hits 4 GB and crashes. How do we find the leak?\"\nassistant: \"The debugger agent will grep heap dump snapshots and scan allocation call sites to identify which objects are accumulating and locate the leak source.\"\n<commentary>\nInvoke the debugger for resource leaks or memory issues that require code-level tracing to isolate the accumulating object type.\n</commentary>\n</example>\n\n<example>\nContext: A race condition is causing data corruption in a multi-threaded order processor under load.\nuser: \"Our concurrent order processing sometimes produces duplicate orders randomly under high load.\"\nassistant: \"I'll use the debugger agent to trace thread interactions, identify shared-state access without synchronization, and design a targeted test to reproduce the race condition reliably.\"\n<commentary>\nUse the debugger for intermittent concurrency bugs; it applies falsification-based hypothesis testing and minimal reproduction to isolate elusive timing issues.\n</commentary>\n</example>"
Context Manager
Context management specialist for multi-agent workflows and long-running tasks. Use PROACTIVELY for complex projects, session coordination, and when context preservation is needed across multiple agents.
Test Engineer
Test automation and quality assurance specialist. Use PROACTIVELY for test strategy, test automation, coverage analysis, CI/CD testing, and quality engineering practices.
Error Detective
"Use this agent when you need to diagnose why errors are occurring in your system, correlate errors across services, identify root causes, and prevent future failures. Specifically:\\n\\n<example>\\nContext: Production system is experiencing intermittent failures across multiple microservices with unclear root cause.\\nuser: \"We have 50+ errors per minute in production with timeout exceptions in the API gateway, database connection errors, and queue failures. The incidents started after a deployment 2 hours ago but we can't figure out what's causing the cascade.\"\\nassistant: \"I'll analyze the error patterns across all services to find the correlation. I'll examine error frequency, timing, service dependencies, recent deployments, and resource metrics to identify what triggered the cascade. Once I find the root cause, I'll explain the failure chain and recommend immediate mitigation and long-term prevention strategies.\"\\n<commentary>\\nInvoke error-detective when production is experiencing failures and you need systematic analysis of error patterns across multiple services to understand causation. This is distinct from code-reviewer (which analyzes code quality) or performance-engineer (which focuses on optimization). Error-detective specializes in understanding failure cascades.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Development team wants to understand why a specific error appears frequently in error logs and whether it indicates a deeper problem.\\nuser: \"Our error tracking shows we get a 'Connection Timeout' error about 100 times per day. Is this normal? Does it indicate a real problem or just flaky tests? Should we be worried?\"\\nassistant: \"I'll investigate the error frequency, when it occurs, which services are affected, correlations with deployments or load spikes, and patterns in affected users or endpoints. I'll determine if this is expected behavior, a symptom of an underlying issue, or an early warning sign of a problem that will worsen under load.\"\\n<commentary>\\nUse error-detective when you need to assess whether a recurring error represents a real problem or is benign, and whether it signals deeper systemic issues. This requires pattern analysis and anomaly detection, not just code inspection.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Team has resolved an incident but wants to prevent similar failures in the future.\\nuser: \"We just had an incident where database connection pool exhaustion caused cascading failures across our payment and order services. How do we prevent this from happening again? What should we monitor?\"\\nassistant: \"I'll map how the connection pool exhaustion propagated through your services, identify which circuit breakers and timeouts failed to prevent the cascade, recommend preventive measures (connection pool monitoring, circuit breaker tuning, graceful degradation), and define alerts to catch early warning signs before the next incident occurs.\"\\n<commentary>\\nInvoke error-detective for post-incident analysis when you need to understand the failure cascade, prevent similar patterns, and enhance monitoring and resilience. This goes beyond root cause to prevent future incidents through systematic improvement.\\n</commentary>\\n</example>"
Mcp Expert
Model Context Protocol (MCP) integration specialist for the cli-tool components system. Use PROACTIVELY for MCP server configurations, protocol specifications, and integration patterns.
Command Expert
CLI command development specialist for the claude-code-templates system. Use PROACTIVELY for command design, argument parsing, task automation, and CLI best practices implementation.
Unused Code Cleaner
Detects and removes unused code (imports, functions, classes) across multiple languages. Use PROACTIVELY after refactoring, when removing features, or before production deployment.
Performance Profiler
Performance analysis and optimization specialist. Use PROACTIVELY for performance bottlenecks, memory leaks, load testing, optimization strategies, and system performance monitoring.
Dx Optimizer
"Use this agent when optimizing the complete developer workflow including build times, feedback loops, testing efficiency, and developer satisfaction metrics across the entire development environment. Specifically:\\n\\n<example>\\nContext: A team reports slow development cycles with 3-minute build times, 2-minute test runs, and frustration with development server startup.\\nuser: \"Our developers are losing productivity due to slow builds and feedback loops. Build time is 3 minutes, tests take 2 minutes, and HMR is inconsistent. Can you optimize our entire DX?\"\\nassistant: \"I'll conduct a comprehensive DX analysis. First, I'll profile the build system to identify bottlenecks, analyze test suite execution for parallelization opportunities, and review development server configuration. Then I'll implement incremental compilation, parallel test execution, HMR optimization, and caching strategies. I'll measure improvements across all metrics and establish ongoing monitoring for developer satisfaction.\"\\n<commentary>\\nInvoke dx-optimizer when you need holistic improvements to developer experience spanning multiple areas: build performance, test execution, feedback speed, workflow automation, and environment setup. This is broader than build-engineer (focused only on build systems) or tooling-engineer (focused on tools).\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Onboarding new developers takes 3 hours due to environment setup complexity, and manual workflow steps are creating friction.\\nuser: \"New developers take hours to set up their environment and frequently make mistakes in our development workflows. Can you streamline this and reduce onboarding friction?\"\\nassistant: \"I'll analyze the current onboarding flow and identify friction points. I'll automate environment setup scripts, create dev container configurations, implement pre-commit hooks to prevent common mistakes, and document our development workflows. I'll also set up IDE configurations for instant code completion and proper tooling, reducing manual setup time from hours to minutes.\"\\n<commentary>\\nUse dx-optimizer when developer satisfaction is impacted by workflow friction, onboarding complexity, or manual processes that consume productive time. The agent optimizes the entire development experience beyond just code execution speed.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: After product growth, the engineering team has grown from 5 to 25 developers, but developer satisfaction scores dropped from 4.2 to 2.8 due to scaling friction.\\nuser: \"Our team scaled rapidly and developer satisfaction plummeted. We need to fix build bottlenecks, improve CI/CD feedback, set up monorepo tooling, and help developers work efficiently at scale.\"\\nassistant: \"I'll assess current pain points across the scaled team and implement solutions systematically. I'll configure monorepo workspace tools, set up distributed caching, implement smart test selection to reduce feedback time, optimize CI/CD parallelization, and establish developer metrics dashboards. I'll measure satisfaction improvements and create feedback loops for continuous optimization.\"\\n<commentary>\\nInvoke this agent when optimizing DX across distributed teams or at scale, where small friction multiplied across many developers significantly impacts productivity. The agent handles comprehensive workflow optimization from development environment to deployment feedback.\\n</commentary>\\n</example>"
Playwright Tester
Testing mode for Playwright tests
Qa Expert
"Use this agent when you need comprehensive quality assurance strategy, test planning across the entire development cycle, or quality metrics analysis to improve overall software quality. Specifically:\\n\\n<example>\\nContext: A development team is about to start a critical 6-month feature development and needs a complete QA strategy before coding begins.\\nuser: \"We need a comprehensive QA strategy for our upcoming project. What should our testing approach be for a complex e-commerce platform?\"\\nassistant: \"I'll develop a complete QA strategy addressing test planning, resource allocation, risk assessment, automation approach, and quality metrics. I'll analyze your architecture, identify critical test areas, recommend manual vs automated testing split, design test coverage targets, and establish quality gates for each release phase.\"\\n<commentary>\\nInvoke qa-expert when you need strategic QA planning across the full development lifecycle. This agent designs the overall quality approach, unlike test-automator which focuses specifically on automation implementation.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A team's current quality metrics show declining quality: defect escape rate is 15%, test coverage is only 52%, and production issues are increasing.\\nuser: \"Our quality metrics are getting worse. Defect escape rate is up, coverage is down, and we're getting customer complaints. How do we fix this?\"\\nassistant: \"I'll analyze your defect patterns, test coverage gaps, and quality process breakdowns. I'll conduct a comprehensive quality audit to identify root causes, recommend specific improvements to your testing strategy, suggest coverage targets, and implement quality metrics tracking to prevent regression.\"\\n<commentary>\\nUse the qa-expert when you need to diagnose systemic quality problems and develop a quality improvement plan. This agent conducts deep analysis and recommends strategic changes, not just automation or code review feedback.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A team is preparing for a major release and needs to validate that all quality standards are met before deployment.\\nuser: \"We're about to release a critical update. How do we ensure quality is acceptable for production release?\"\\nassistant: \"I'll conduct a comprehensive pre-release quality assessment: review test coverage against requirements, validate defect severity and resolution, check test execution results, assess risk areas, verify automated test reliability, and provide a go/no-go recommendation based on established quality gates.\"\\n<commentary>\\nInvoke qa-expert for pre-release quality validation and release readiness assessments. This agent provides holistic quality evaluation and release recommendation, complementing the detailed code review feedback from other agents.\\n</commentary>\\n</example>"
Code Simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Architect Reviewer
"Use this agent when you need to evaluate system design decisions, architectural patterns, and technology choices at the macro level. Specifically:\\n\\n<example>\\nContext: Team has proposed a microservices migration strategy but is uncertain about service boundaries and data ownership model.\\nuser: \"We're planning to migrate from a monolith to microservices. Can you review our proposed architecture for technical soundness and scalability?\"\\nassistant: \"I'll conduct a comprehensive architecture review examining your service boundaries, data ownership patterns, communication strategies, and evolution path. I'll assess whether the microservices design meets your scalability goals, validate that dependencies are minimized, verify security implications, and identify risks like distributed transaction complexity and team coordination needs. I'll provide concrete recommendations for refactoring if needed.\"\\n<commentary>\\nInvoke architect-reviewer when evaluating major architectural decisions like transitioning between architectural patterns. This differs from code-reviewer (handles code quality) and focuses on system-level design rather than individual component implementation.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Engineering team is selecting between different technology stacks for a new system (monolithic Node.js, serverless with Lambda, or containerized microservices).\\nuser: \"We need to decide on our technology stack for a new payment processing system. Which approach is best for our team and requirements?\"\\nassistant: \"I'll evaluate each option against your specific constraints: team expertise, scalability requirements, operational complexity, cost implications, and long-term maintainability. I'll analyze trade-offs like deployment complexity vs. auto-scaling benefits, monolithic simplicity vs. microservices flexibility, and help you understand the organizational implications of each choice. I'll provide a recommendation with risk mitigation strategies.\"\\n<commentary>\\nUse architect-reviewer for technology selection decisions where you need evaluation of long-term implications and trade-offs between different architectural approaches.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: System is growing complex with tightly coupled modules and the team struggles with deployment and testing velocity.\\nuser: \"Our system is becoming hard to maintain and deploy. Can you analyze our current architecture and suggest how we should restructure it?\"\\nassistant: \"I'll analyze your current architecture to identify coupling issues, evaluate whether modularization is needed, assess technical debt impact, and recommend a phased modernization strategy. I'll examine component boundaries, data flow, dependency trees, and deployment topology. I'll propose an evolutionary path using patterns like strangler fig, branch by abstraction, or incremental refactoring to improve maintainability while minimizing risk.\"\\n<commentary>\\nInvoke architect-reviewer when you need guidance on restructuring existing systems, identifying architectural debt, or planning major architectural evolution. This focuses on the macro system design and long-term sustainability rather than individual code quality.\\n</commentary>\\n</example>"
Refactoring Specialist
"Use when you need to transform poorly structured, complex, or duplicated code into clean, maintainable systems while preserving all existing behavior. Specifically:\\n\\n<example>\\nContext: A codebase has methods exceeding 200 lines, deeply nested conditionals, and 15% code duplication across similar functions.\\nuser: \"Help me refactor this legacy payment processing module. The methods are too long and the logic is hard to follow.\"\\nassistant: \"I'll analyze the code for smells like long methods and duplicated logic, create comprehensive characterization tests to verify behavior, then systematically apply extract method, inline temporary variables, and consolidate duplicate code while tracking complexity metrics.\"\\n<commentary>\\nInvoke this agent when code quality metrics show complexity issues, code smells are detected, or maintainability is suffering despite tests passing. The agent excels at safe, incremental refactoring with continuous test verification.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A team is modernizing a legacy system with 40% code duplication and multiple overlapping design patterns that should be consolidated.\\nuser: \"We have three similar service classes that do almost the same thing. Can you refactor them to use a single abstract base class and strategy pattern?\"\\nassistant: \"I'll extract the common interface, create a template method for shared behavior, break dependencies, apply the strategy pattern to the divergent parts, then run the full test suite to ensure zero behavior changes while dramatically reducing duplication.\"\\n<commentary>\\nUse this agent for design pattern refactoring that improves architecture and eliminates duplicate logic. The agent applies SOLID principles and can handle complex structural transformations with safety guarantees.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Performance monitoring shows a database-heavy API endpoint performing 300 queries per request due to inefficient data access patterns.\\nuser: \"This endpoint is running way too many database queries. How can we refactor the data access layer?\"\\nassistant: \"I'll profile the queries, identify the N+1 query problems and missing indexes, refactor the data loading strategy with batch operations, introduce caching where appropriate, and validate with performance benchmarks that we've reduced queries to under 5 per request.\"\\n<commentary>\\nInvoke the refactoring specialist when performance issues stem from structural inefficiencies (not just algorithmic) that require safe refactoring of data access, query patterns, or architectural layers.\\n</commentary>\\n</example>"
Technical Debt Manager
Expert technical debt analyst for code health, maintainability, and strategic refactoring planning. Use PROACTIVELY when codebase shows complexity growth, when planning sprints, or when prioritizing engineering work.
Performance Engineer
"Use this agent when you need to identify and eliminate performance bottlenecks in applications, databases, or infrastructure systems, and when baseline performance metrics need improvement. Specifically:\\n\\n<example>\\nContext: An API is responding slowly in production with response times averaging 2.5 seconds, and users are complaining about lag.\\nuser: \"We're seeing slow API response times. Can you help identify what's causing the bottleneck?\"\\nassistant: \"I'll profile the application, analyze database queries, check resource utilization, and run load tests to identify the root cause. Let me start by collecting performance baselines and examining CPU, memory, and I/O patterns.\"\\n<commentary>\\nUse the performance-engineer agent when you need systematic bottleneck identification and have measurable performance problems. This agent conducts detailed profiling and load testing to pinpoint root causes.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A database query that previously took 100ms now takes 800ms after a data migration, and the team needs the database optimized.\\nuser: \"Our main query got much slower after migrating data. How do we fix this?\"\\nassistant: \"I'll analyze the execution plan, check index efficiency, review query optimization, and test different approaches. I can profile the database workload and implement targeted indexing and caching strategies.\"\\n<commentary>\\nInvoke the performance-engineer for database-specific performance issues like slow queries, connection pooling problems, or cache inefficiency. This agent specializes in query analysis and database tuning.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: An e-commerce site experiences a 40% slowdown during peak traffic, and the team wants to ensure scalability for expected growth.\\nuser: \"We need to handle 10x our current traffic without performance degradation. What's our scalability plan?\"\\nassistant: \"I'll design load tests to simulate peak traffic, profile system behavior under stress, and implement horizontal scaling, auto-scaling policies, and load balancing strategies. Let me establish performance baselines and create a capacity plan.\"\\n<commentary>\\nUse the performance-engineer when you need scalability engineering, capacity planning, or validation that infrastructure can handle projected growth. This agent designs comprehensive load testing and scaling strategies.\\n</commentary>\\n</example>"
Test Automator
"Use this agent when you need to build, implement, or enhance automated test frameworks, create test scripts, or integrate testing into CI/CD pipelines. Specifically:\\n\\n<example>\\nContext: A team has identified a set of manual test cases that need to be automated to reduce regression testing time from 3 days to hours.\\nuser: \"We have 200+ manual test cases that we need to automate. Our QA team spends 3 days on regression testing each sprint. Can you build an automation framework?\"\\nassistant: \"I'll design and implement a complete test automation framework. First, I'll analyze your manual test cases to identify automation candidates, select appropriate frameworks and tools for your tech stack, design the framework architecture with reusable components, create test scripts for your priority cases, and integrate everything into your CI/CD pipeline. We'll focus on maintainability and execution speed.\"\\n<commentary>\\nUse test-automator when you have an automation strategy in place (from qa-expert) and need hands-on implementation of test frameworks and scripts. This agent builds the actual automation solution, not the strategic quality plan.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: An existing test automation suite is brittle, has flaky tests, and is difficult to maintain. The team wants to refactor and improve the framework.\\nuser: \"Our automated tests are failing randomly, taking too long to run, and the code is hard to maintain. How do we fix our test framework?\"\\nassistant: \"I'll audit your current framework, identify maintenance issues and flaky test causes, refactor the architecture using best practices like page object models, improve wait strategies and error handling, optimize test execution for speed and parallelization, add comprehensive logging and reporting, and document patterns for your team.\"\\n<commentary>\\nInvoke test-automator to improve existing automation infrastructure. This agent specializes in framework optimization, addressing flakiness, improving maintainability, and scaling test execution—the implementation-level work.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A development team is building a new microservices platform and needs to automate API testing as part of their CI/CD pipeline.\\nuser: \"We're building microservices with APIs. We need automated API testing integrated into CI/CD so we can catch integration issues early. How should we set this up?\"\\nassistant: \"I'll design an API-specific test automation strategy using contract testing and data-driven approaches. I'll create a framework for request building, response validation, and error scenario testing. I'll handle authentication, mock services, performance assertions, and CI/CD integration with result reporting and failure analysis.\"\\n<commentary>\\nUse test-automator for specific automation implementation work like API testing, UI automation, or mobile testing. This agent takes the testing requirements and builds working automation infrastructure and test scripts.\\n</commentary>\\n</example>"
Laravel Expert Agent
Expert Laravel development assistant specializing in modern Laravel 12+ applications with Eloquent, Artisan, testing, and best practices
Accessibility Tester
"Use this agent when you need comprehensive accessibility testing, WCAG compliance verification, or assessment of assistive technology support. Specifically:\\n\\n<example>\\nContext: A web application is preparing for launch and needs to ensure compliance with accessibility standards before release.\\nuser: \"Can you test our web app for accessibility issues? We need to know if it works with screen readers and keyboard navigation, and if we meet WCAG standards.\"\\nassistant: \"I'll conduct a comprehensive accessibility audit covering WCAG 2.1 Level AA compliance, screen reader compatibility (NVDA, JAWS, VoiceOver), full keyboard navigation testing, color contrast verification, focus management, and ARIA implementation. I'll identify violations, prioritize by severity, and provide specific remediation guidance.\"\\n<commentary>\\nInvoke accessibility-tester when an application needs formal accessibility testing and compliance verification. This agent conducts systematic testing across multiple accessibility dimensions, unlike qa-expert which focuses on general quality assurance.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Users with disabilities reported difficulty using the mobile app, and the team wants to understand and fix accessibility barriers.\\nuser: \"We're getting feedback that disabled users can't use our mobile app properly. Some can't navigate with the keyboard and others have trouble with the screen reader. What's wrong?\"\\nassistant: \"I'll test your mobile app with assistive technologies to identify specific accessibility barriers. I'll check touch target sizing, gesture alternatives, screen reader compatibility, keyboard navigation logic, and platform-specific accessibility features. I'll document each barrier with a clear explanation of the impact on users and concrete fixes needed.\"\\n<commentary>\\nUse accessibility-tester to diagnose accessibility problems reported by users and design solutions. This agent traces user complaints to specific accessibility failures and recommends fixes.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A development team has built a complex form with dynamic validation and wants to ensure it's accessible before merging the feature.\\nuser: \"We built a new checkout form with real-time validation. Can you check if it's accessible? We want to make sure errors are announced properly and the keyboard flow works.\"\\nassistant: \"I'll review the form's accessibility including label associations, error identification and announcement, field instructions, focus management during validation, keyboard navigation flow, and screen reader announcements. I'll identify any ARIA violations, test with actual assistive technologies, and verify the form meets WCAG standards.\"\\n<commentary>\\nInvoke accessibility-tester for component or feature-level accessibility validation before integration. This agent verifies specific UI patterns work correctly with assistive technology, catching issues before they reach users.\\n</commentary>\\n</example>"
Flutter Go Reviewer
|
Dependency Manager
"Use this agent when you need to audit dependencies for vulnerabilities, resolve version conflicts, optimize bundle sizes, or implement automated dependency updates. Specifically:\\n\\n<example>\\nContext: A project has accumulated security vulnerabilities in its dependency tree that need immediate remediation.\\nuser: \"We have 12 high-severity CVEs in our dependencies. Can you help fix them?\"\\nassistant: \"I'll use the dependency-manager agent to scan all vulnerabilities, assess their impact, and create a prioritized remediation plan with safe update strategies.\"\\n<commentary>\\nInvoke the dependency-manager agent when security vulnerabilities are discovered and you need systematic scanning, assessment, and patching guidance across the entire dependency tree.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A team wants to optimize bundle size and build performance across a monorepo with multiple workspaces.\\nuser: \"Our JavaScript bundle is 2.8MB and build times are slow. How can we reduce dependencies?\"\\nassistant: \"I'll use the dependency-manager agent to analyze the dependency tree for duplicates, unused packages, and optimization opportunities, then propose bundle size reductions.\"\\n<commentary>\\nUse the dependency-manager agent when you need to analyze dependency trees, detect duplication, and implement optimization strategies like tree shaking and lazy loading.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A project experiencing version incompatibilities between packages that are preventing updates.\\nuser: \"React 18 won't install because our other packages have conflicting peer dependencies. How do we resolve this?\"\\nassistant: \"I'll use the dependency-manager agent to map the dependency conflicts, identify resolution paths, and implement a strategy to upgrade without breaking the build.\"\\n<commentary>\\nInvoke the dependency-manager agent when facing version conflicts that block updates, requiring conflict resolution strategies and compatibility analysis across the ecosystem.\\n</commentary>\\n</example>"
Build Engineer
"Use this agent when you need to optimize build performance, reduce compilation times, or scale build systems across growing teams. Specifically:\\n\\n<example>\\nContext: A development team's build times have degraded from 30 seconds to 2+ minutes, blocking developer productivity.\\nuser: \"Our build is too slow. It used to take 30 seconds but now it's over 2 minutes. We need to fix this urgently.\"\\nassistant: \"I'll analyze your build configuration, profile the compilation process to identify bottlenecks, and implement optimizations like incremental compilation, parallel builds, and strategic caching.\"\\n<commentary>\\nUse the build-engineer when facing performance regressions or excessive build times. They can diagnose root causes and implement targeted optimizations.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A monorepo is growing with multiple teams, but the build system doesn't scale efficiently and cache hit rates are low.\\nuser: \"We're expanding to 5 teams, but our build system is getting worse. How do we scale it?\"\\nassistant: \"I'll architect a distributed caching layer, implement workspace optimization for your monorepo structure, and configure parallel task execution across affected modules.\"\\n<commentary>\\nUse the build-engineer when scaling build infrastructure for growing teams or transitioning to monorepos. They design systems that maintain performance as complexity increases.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Bundle sizes are bloating the application and causing slow deployments and poor user experience.\\nuser: \"Our bundle is 5MB and it's killing our page load times. We need to cut it down.\"\\nassistant: \"I'll analyze your dependencies, implement code splitting strategies, configure tree-shaking and minification, and set up bundle analysis to track regressions.\"\\n<commentary>\\nUse the build-engineer when optimizing bundle sizes or improving deployment efficiency. They apply proven bundling techniques to reduce output size while maintaining functionality.\\n</commentary>\\n</example>"
Tooling Engineer
"Use this agent when you need to build or enhance developer tools including CLIs, code generators, build tools, and IDE extensions. Specifically:\\n\\n<example>\\nContext: Team has recurring manual tasks that could be automated with a custom CLI tool.\\nuser: \"We spend 30 minutes daily on repetitive deployment checks and configuration validation. Can you design and build a CLI tool that automates this?\"\\nassistant: \"I'll design a performant CLI tool with subcommands for your common workflows, built-in configuration management, interactive prompts for validation, and progress indicators. I'll ensure startup time is under 100ms, make it cross-platform compatible, add shell completion support, and include comprehensive error handling with helpful messages. The tool will be distributed via npm with auto-update capability.\"\\n<commentary>\\nInvoke tooling-engineer when you need to build new developer tools, CLIs, code generators, or enhance tool architecture. This is distinct from build-engineer (who optimizes existing build systems) and dx-optimizer (who improves workflows without necessarily building new tools). Tooling-engineer creates new tools from scratch or significantly extends existing ones.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Organization wants to standardize code generation and scaffolding across multiple projects.\\nuser: \"We need a code generation tool that can scaffold new services following our architecture patterns. It should generate TypeScript types, database migrations, API routes, and tests automatically.\"\\nassistant: \"I'll build a schema-driven code generator with plugin support for different code types. It will include template engines for customization, AST manipulation for type generation, scaffold commands for service creation, configuration management for project-specific settings, and comprehensive documentation. I'll ensure extensibility so teams can add custom generators, and include validation to guarantee generated code follows your standards.\"\\n<commentary>\\nUse tooling-engineer for specialized code generation tools, scaffolding systems, and generators that reduce boilerplate and enforce architectural patterns across teams. These tools typically integrate with CI/CD and require careful design for extensibility.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Team needs to build IDE extensions and language server protocols for better developer experience.\\nuser: \"We want to build a VS Code extension that provides code completion, refactoring, and debugging capabilities for our custom DSL. Can you design the architecture and implementation?\"\\nassistant: \"I'll design the extension with a language server protocol implementation for cross-editor compatibility, create syntax highlighting and code completion providers, build refactoring tools, integrate debugging support, and design the plugin architecture for extensibility. I'll optimize for performance, ensure users can configure the extension through settings, and provide clear error messages with recovery suggestions.\"\\n<commentary>\\nInvoke tooling-engineer when creating IDE extensions, language servers, or sophisticated tools that require plugin systems, event-driven architecture, and careful performance optimization. These tools enhance the development environment itself rather than build processes.\\n</commentary>\\n</example>"
Cli Developer
"Use this agent when building command-line tools and terminal applications that require intuitive command design, cross-platform compatibility, and optimized developer experience. Specifically:\\n\\n<example>\\nContext: A development team needs a new CLI tool for managing local database migrations and seeding with interactive workflows.\\nuser: \"We need a CLI tool that lets developers manage database migrations. It should support interactive prompts, show migration status, handle rollbacks, and work on macOS, Linux, and Windows.\"\\nassistant: \"I'll design and build this CLI with excellent UX. First, let me check your database setup. Then I'll implement commands for migrate, rollback, seed, and status with color-coded output, interactive mode for beginners, and automation mode for CI/CD. I'll add shell completions and ensure sub-50ms startup time.\"\\n<commentary>\\nUse the cli-developer when creating developer-focused CLI tools that need strong UX, interactive workflows, cross-platform support, and integration with existing development workflows.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: An open-source project needs a CLI tool with plugin architecture for extensibility and community contributions.\\nuser: \"We want to build a pluggable CLI tool where community members can write plugins. Need plugin discovery, version compatibility, API contracts, and easy installation.\"\\nassistant: \"I'll architect the plugin system with proper API contracts, dynamic discovery mechanisms, and version compatibility handling. I'll implement secure plugin sandboxing, auto-update mechanisms, and comprehensive documentation for plugin authors. I'll include example plugins and templates to encourage community participation.\"\\n<commentary>\\nInvoke this agent when building extensible CLI tools with plugin systems, needing to define plugin APIs, manage compatibility, and support community-driven development.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A production deployment tool needs to provide real-time feedback, handle complex workflows, and work offline.\\nuser: \"Our deployment CLI needs beautiful progress indicators for multi-step deployments, real-time status updates, error recovery, and offline capability when network is unavailable.\"\\nassistant: \"I'll implement a sophisticated CLI with progress bars, spinners, and task tree visualization. I'll add graceful error handling with recovery suggestions, offline-first architecture with sync when reconnected, and comprehensive logging. I'll optimize for <50ms startup and test across platforms.\"\\n<commentary>\\nUse this agent for building production-grade CLI tools that handle complex workflows, provide detailed feedback, support error recovery, and maintain high performance.\\n</commentary>\\n</example>"
Codebase Explorer
|
Codebase Pattern Finder
Specialist for finding code patterns and examples in the codebase, providing concrete implementations that can serve as templates for new work
Slack Expert
"Use this agent when developing Slack applications, implementing Slack API integrations, or reviewing Slack bot code for security and best practices. Specifically:\\n\\n<example>\\nContext: Developer is building a new Slack bot using @slack/bolt that needs to handle app mentions, respond to slash commands, and display Block Kit modals.\\nuser: \"I'm building a Slack bot that handles app mentions, slash commands, and interactive modals. Can you help me set it up with proper error handling and event subscriptions?\"\\nassistant: \"I'll help you build this bot using @slack/bolt best practices. I'll set up proper event handlers with error handling, configure your slash commands, design Block Kit modals with proper state management, implement request signature verification, and ensure OAuth V2 flow is correctly configured. I'll also add rate limit handling and test everything before deployment.\"\\n<commentary>\\nInvoke slack-expert when building new Slack bots or applications, especially when you need guidance on @slack/bolt patterns, event handling architecture, or Block Kit UI design. This agent excels at setting up production-ready bots with security and scalability.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Team has existing Slack integration code that needs security and efficiency review before production deployment.\\nuser: \"We have a Slack app that posts notifications to channels. Can you review it for security issues, rate limiting problems, and deprecated API usage?\"\\nassistant: \"I'll review your Slack code for request signature verification, secure token management, rate limit handling with exponential backoff, deprecated API calls, and Block Kit migration opportunities. I'll verify OAuth scopes follow principle of least privilege, check error handling patterns, and ensure it follows production readiness standards.\"\\n<commentary>\\nUse slack-expert for code reviews of existing Slack integrations when you need to verify security practices, identify deprecated APIs, ensure rate limiting is implemented correctly, or prepare for production deployment.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Developer is implementing OAuth authentication and webhook handling for a Slack app that will be distributed to multiple workspaces.\\nuser: \"I need to implement OAuth V2 authentication for our Slack app that will be installed in different workspaces. How should I handle token storage, socket mode vs HTTP webhooks, and event acknowledgment?\"\\nassistant: \"I'll help you set up OAuth V2 flow with secure token storage in environment variables, guide you on choosing Socket Mode for development vs HTTP webhooks for production, implement proper event acknowledgment to avoid duplicates, and ensure your app scales properly with multiple workspace installations. I'll also add monitoring and logging for production reliability.\"\\n<commentary>\\nInvoke slack-expert when implementing authentication flows, webhook handling, or preparing a Slack app for distribution to multiple workspaces. This agent specializes in security-first OAuth implementation and production-ready architectures.\\n</commentary>\\n</example>"
Chaos Engineer
"Use this agent when you need to design and execute controlled failure experiments, validate system resilience before incidents occur, or conduct game day exercises to test your team's incident response capabilities. Specifically:\\n\\n<example>\\nContext: A microservices platform has recently experienced two unexpected service failures that took 2 hours to recover from. Leadership wants confidence that the system won't fail again without warning.\\nuser: \"We need to test if our system can handle failures gracefully. What failures should we simulate and how do we run the experiments safely?\"\\nassistant: \"I'll design a controlled chaos experiment program starting with low-impact tests in non-production. We'll simulate service failures, network partitions, and database issues while monitoring metrics continuously. Each experiment includes automatic rollback, blast radius controls, and documentation of learnings.\"\\n<commentary>\\nInvoke chaos-engineer when you need systematic failure validation before incidents occur in production, or when past incidents reveal gaps in resilience. This agent designs safe, controlled experiments that build confidence in system robustness.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: An e-commerce platform runs a quarterly \"game day\" exercise where the team simulates a major outage. The team needs help planning and executing the exercise to uncover operational gaps.\\nuser: \"We want to run a game day scenario simulating a regional failure. How should we plan this and what should we test?\"\\nassistant: \"I'll help you design the game day scenario including failure timeline, team roles, communication protocols, success criteria, and observation points. We'll document the steady state, define the hypothesis, plan recovery procedures, and schedule post-mortems to extract learnings about your incident response process.\"\\n<commentary>\\nUse chaos-engineer for planning and executing game day exercises and organizational resilience drills. This agent specializes in designing realistic failure scenarios that test team coordination, decision-making, and incident response procedures.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A team has made several infrastructure improvements (better monitoring, circuit breakers, improved runbooks) and wants to verify these actually improve system resilience compared to before.\\nuser: \"We've made reliability improvements. How do we verify our changes actually made the system more resilient to failures?\"\\nassistant: \"I'll design a targeted chaos experiment program that tests your key improvements against your baseline. We'll measure MTTR, system behavior during failures, monitoring effectiveness, and team response time. I'll establish metrics that show whether your resilience score improved and document specific failure modes you've made safer.\"\\n<commentary>\\nInvoke chaos-engineer when you need to measure the impact of reliability improvements or validate that changes have actually increased system resilience. This agent designs experiments with measurable metrics showing improvement over time.\\n</commentary>\\n</example>"
General Purpose
Default agent for handling complex, multi-step tasks with automatic delegation capabilities
Ascii Ui Mockup Generator
Specialist in creating ASCII mockups for UI concepts, generating multiple visualization options for layouts, forms, dashboards, and interfaces before implementation
Launchdarkly Flag Cleanup
A specialized GitHub Copilot agent that uses the LaunchDarkly MCP server to safely automate feature flag cleanup workflows. This agent determines removal readiness, identifies the correct forward value, and creates PRs that preserve production behavior while removing obsolete flags and updating stale defaults.
Pagerduty Incident Responder
Responds to PagerDuty incidents by analyzing incident context, identifying recent code changes, and suggesting fixes via GitHub PRs.
Rootly Incident Responder
|
Thinking Beast Mode
Use this agent for long-running, autonomous multi-step engineering tasks that must be driven to full completion without handing control back early — e.g., "fix this failing test suite and don't stop until every test passes," "implement this feature end-to-end including tests," or "track down this intermittent bug." The agent plans, investigates the codebase (and the web when needed), implements, and rigorously verifies before ending its turn, checking off a visible todo list as it goes.
Other Agents Categories
Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.