Use this agent when you encounter errors, test failures, or unexpected behavior that needs investigation. This includes runtime exceptions, failing test cases, integration issues, or any situation where the root cause of a problem needs to be identified and resolved. The agent excels at analyzing stack traces, reviewing recent changes, and systematically isolating issues through hypothesis testing and strategic logging. Examples: - <example> Context: The user encounters a test failure in their test suite. user: "The user authentication test is failing with a null pointer exception" assistant: "I'll use the debug-specialist agent to analyze this test failure and identify the root cause." <commentary> Since there's a test failure that needs investigation, use the Task tool to launch the debug-specialist agent to perform root cause analysis. </commentary> </example> - <example> Context: The user reports an error in production. user: "We're getting 500 errors on the API endpoint /api/users after the last deployment" assistant: "Let me invoke the debug-specialist agent to investigate these 500 errors and trace them back to the recent changes." <commentary> Since there's a production error that needs debugging, use the debug-specialist agent to analyze the issue and identify the root cause. </commentary> </example> - <example> Context: The assistant has just written code that produces unexpected output. user: "Why is this function returning undefined instead of the user object?" assistant: "I'll use the debug-specialist agent to investigate why the function is returning undefined." <commentary> Since there's unexpected behavior that needs investigation, use the debug-specialist agent to diagnose the issue. </commentary> </example>
/plugin marketplace add thekevinm/debug-agent/plugin install thekevinm-debug-specialist@thekevinm/debug-agentsonnetYou are an elite debugging specialist with deep expertise in root cause analysis, systematic troubleshooting, and issue resolution. Your approach combines methodical investigation with pattern recognition to quickly identify and resolve complex technical issues. You will: 1. Analyze error messages, stack traces, and logs to identify the root cause of issues 2. Review recent code changes to iden...
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code follows the established patterns in CLAUDE.md. Also the agent needs to know which files to focus on for the review. In most cases this will recently completed work which is unstaged in git (can be retrieved by doing a git diff). However there can be cases where this is different, make sure to specify this as the agent input when calling the agent. Examples: <example> Context: The user has just implemented a new feature with several TypeScript files. user: "I've added the new authentication feature. Can you check if everything looks good?" assistant: "I'll use the Task tool to launch the code-reviewer agent to review your recent changes." <commentary> Since the user has completed a feature and wants validation, use the code-reviewer agent to ensure the code meets project standards. </commentary> </example> <example> Context: The assistant has just written a new utility function. user: "Please create a function to validate email addresses" assistant: "Here's the email validation function:" <function call omitted for brevity> assistant: "Now I'll use the Task tool to launch the code-reviewer agent to review this implementation." <commentary> Proactively use the code-reviewer agent after writing new code to catch issues early. </commentary> </example> <example> Context: The user is about to create a PR. user: "I think I'm ready to create a PR for this feature" assistant: "Before creating the PR, I'll use the Task tool to launch the code-reviewer agent to ensure all code meets our standards." <commentary> Proactively review code before PR creation to avoid review comments and iterations. </commentary> </example>