diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index d060141..6709854 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -1,12 +1,13 @@ { - "$schema": "https://anthropic.com/claude-code/marketplace.schema.json", "name": "claude-code-plugins", - "version": "1.0.0", - "description": "Bundled plugins for Claude Code including Agent SDK development tools, PR review toolkit, and commit workflows", "owner": { "name": "Anthropic", "email": "support@anthropic.com" }, + "metadata": { + "version": "1.0.0", + "description": "Bundled plugins for Claude Code including Agent SDK development tools, PR review toolkit, and commit workflows" + }, "plugins": [ { "name": "agent-sdk-dev", diff --git a/.gitignore b/.gitignore index e094608..31eaf27 100644 --- a/.gitignore +++ b/.gitignore @@ -22,7 +22,7 @@ pids .env .env.local .env.*.local - +settings.local.json # IDE .vscode/ .idea/ diff --git a/agent-team-test-artifacts/agent-1/npm-cache/_cacache/content-v2/sha512/ba/43/2d6190a2d08edc0f7aedf3dae75f2db40ff66f9341a3fd25bad3161fcf5ef34ec94bcfe56e857c3f28f6feda7769dff01369d25dc8d12a74a42570d93b9d b/agent-team-test-artifacts/agent-1/npm-cache/_cacache/content-v2/sha512/ba/43/2d6190a2d08edc0f7aedf3dae75f2db40ff66f9341a3fd25bad3161fcf5ef34ec94bcfe56e857c3f28f6feda7769dff01369d25dc8d12a74a42570d93b9d new file mode 100644 index 0000000..4808441 Binary files /dev/null and b/agent-team-test-artifacts/agent-1/npm-cache/_cacache/content-v2/sha512/ba/43/2d6190a2d08edc0f7aedf3dae75f2db40ff66f9341a3fd25bad3161fcf5ef34ec94bcfe56e857c3f28f6feda7769dff01369d25dc8d12a74a42570d93b9d differ diff --git a/agent-team-test-artifacts/agent-1/npm-cache/_cacache/index-v5/8e/df/5472fe1cc0e8f0c6de8ab9638dcb0eb4220317269f225ef94e7896902fd7 b/agent-team-test-artifacts/agent-1/npm-cache/_cacache/index-v5/8e/df/5472fe1cc0e8f0c6de8ab9638dcb0eb4220317269f225ef94e7896902fd7 new file mode 100644 index 0000000..6c95652 --- /dev/null +++ b/agent-team-test-artifacts/agent-1/npm-cache/_cacache/index-v5/8e/df/5472fe1cc0e8f0c6de8ab9638dcb0eb4220317269f225ef94e7896902fd7 @@ -0,0 +1,2 @@ + +c0aca304189825d07d68f12a85ca4c4f5d53e58b {"key":"pacote:tarball:file:E:/ZNGZ/Code_copy/learning_proj/Open-ClaudeCode/package","integrity":"sha512-ukMtYZCi0I7cD3rt89rnXy20D/Zvk0Gj/SW60xYfz17zTslLz+VuhXw/KPb+2ndp3/ATadJdyNEqdKQlcNk7nQ==","time":1779353697479,"size":31196633} \ No newline at end of file diff --git a/agent-team-test-artifacts/agent-1/npm-cache/_update-notifier-last-checked b/agent-team-test-artifacts/agent-1/npm-cache/_update-notifier-last-checked new file mode 100644 index 0000000..e69de29 diff --git a/plugins/hookify/agents/conversation-analyzer.md b/plugins/hookify/agents/conversation-analyzer.md index cb91a41..47c5bfb 100644 --- a/plugins/hookify/agents/conversation-analyzer.md +++ b/plugins/hookify/agents/conversation-analyzer.md @@ -1,6 +1,7 @@ --- name: conversation-analyzer -description: Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Examples: Context: User is running /hookify command without arguments\nuser: "/hookify"\nassistant: "I'll analyze the conversation to find behaviors you want to prevent"\nThe /hookify command without arguments triggers conversation analysis to find unwanted behaviors.Context: User wants to create hooks from recent frustrations\nuser: "Can you look back at this conversation and help me create hooks for the mistakes you made?"\nassistant: "I'll use the conversation-analyzer agent to identify the issues and suggest hooks."\nUser explicitly asks to analyze conversation for mistakes that should be prevented. +description: |- + Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Examples: Context: User is running /hookify command without arguments\nuser: "/hookify"\nassistant: "I'll analyze the conversation to find behaviors you want to prevent"\nThe /hookify command without arguments triggers conversation analysis to find unwanted behaviors.Context: User wants to create hooks from recent frustrations\nuser: "Can you look back at this conversation and help me create hooks for the mistakes you made?"\nassistant: "I'll use the conversation-analyzer agent to identify the issues and suggest hooks."\nUser explicitly asks to analyze conversation for mistakes that should be prevented. model: inherit color: yellow tools: ["Read", "Grep"] diff --git a/plugins/plugin-dev/.claude-plugin/plugin.json b/plugins/plugin-dev/.claude-plugin/plugin.json new file mode 100644 index 0000000..f90c477 --- /dev/null +++ b/plugins/plugin-dev/.claude-plugin/plugin.json @@ -0,0 +1,9 @@ +{ + "name": "plugin-dev", + "description": "Comprehensive toolkit for developing Claude Code plugins. Includes expert skills covering hooks, MCP integration, commands, agents, and best practices.", + "version": "0.1.0", + "author": { + "name": "Daisy Hollman", + "email": "daisy@anthropic.com" + } +} diff --git a/plugins/plugin-dev/agents/agent-creator.md b/plugins/plugin-dev/agents/agent-creator.md index 6095392..28a7cc8 100644 --- a/plugins/plugin-dev/agents/agent-creator.md +++ b/plugins/plugin-dev/agents/agent-creator.md @@ -1,33 +1,34 @@ --- name: agent-creator -description: Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples: - - -Context: User wants to create a code review agent -user: "Create an agent that reviews code for quality issues" -assistant: "I'll use the agent-creator agent to generate the agent configuration." - -User requesting new agent creation, trigger agent-creator to generate it. - - - - -Context: User describes needed functionality -user: "I need an agent that generates unit tests for my code" -assistant: "I'll use the agent-creator agent to create a test generation agent." - -User describes agent need, trigger agent-creator to build it. - - - - -Context: User wants to add agent to plugin -user: "Add an agent to my plugin that validates configurations" -assistant: "I'll use the agent-creator agent to generate a configuration validator agent." - -Plugin development with agent addition, trigger agent-creator. - - +description: |- + Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples: + + + Context: User wants to create a code review agent + user: "Create an agent that reviews code for quality issues" + assistant: "I'll use the agent-creator agent to generate the agent configuration." + + User requesting new agent creation, trigger agent-creator to generate it. + + + + + Context: User describes needed functionality + user: "I need an agent that generates unit tests for my code" + assistant: "I'll use the agent-creator agent to create a test generation agent." + + User describes agent need, trigger agent-creator to build it. + + + + + Context: User wants to add agent to plugin + user: "Add an agent to my plugin that validates configurations" + assistant: "I'll use the agent-creator agent to generate a configuration validator agent." + + Plugin development with agent addition, trigger agent-creator. + + model: sonnet color: magenta diff --git a/plugins/plugin-dev/agents/plugin-validator.md b/plugins/plugin-dev/agents/plugin-validator.md index cf977e4..1fe52a8 100644 --- a/plugins/plugin-dev/agents/plugin-validator.md +++ b/plugins/plugin-dev/agents/plugin-validator.md @@ -1,35 +1,36 @@ --- name: plugin-validator -description: Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples: - - -Context: User finished creating a new plugin -user: "I've created my first plugin with commands and hooks" -assistant: "Great! Let me validate the plugin structure." - -Plugin created, proactively validate to catch issues early. - -assistant: "I'll use the plugin-validator agent to check the plugin." - - - -Context: User explicitly requests validation -user: "Validate my plugin before I publish it" -assistant: "I'll use the plugin-validator agent to perform comprehensive validation." - -Explicit validation request triggers the agent. - - - - -Context: User modified plugin.json -user: "I've updated the plugin manifest" -assistant: "Let me validate the changes." - -Manifest modified, validate to ensure correctness. - -assistant: "I'll use the plugin-validator agent to check the manifest." - +description: |- + Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples: + + + Context: User finished creating a new plugin + user: "I've created my first plugin with commands and hooks" + assistant: "Great! Let me validate the plugin structure." + + Plugin created, proactively validate to catch issues early. + + assistant: "I'll use the plugin-validator agent to check the plugin." + + + + Context: User explicitly requests validation + user: "Validate my plugin before I publish it" + assistant: "I'll use the plugin-validator agent to perform comprehensive validation." + + Explicit validation request triggers the agent. + + + + + Context: User modified plugin.json + user: "I've updated the plugin manifest" + assistant: "Let me validate the changes." + + Manifest modified, validate to ensure correctness. + + assistant: "I'll use the plugin-validator agent to check the manifest." + model: inherit color: yellow diff --git a/plugins/plugin-dev/agents/skill-reviewer.md b/plugins/plugin-dev/agents/skill-reviewer.md index b15adbe..e4c83a5 100644 --- a/plugins/plugin-dev/agents/skill-reviewer.md +++ b/plugins/plugin-dev/agents/skill-reviewer.md @@ -1,34 +1,35 @@ --- name: skill-reviewer -description: Use this agent when the user has created or modified a skill and needs quality review, asks to "review my skill", "check skill quality", "improve skill description", or wants to ensure skill follows best practices. Trigger proactively after skill creation. Examples: - - -Context: User just created a new skill -user: "I've created a PDF processing skill" -assistant: "Great! Let me review the skill quality." - -Skill created, proactively trigger skill-reviewer to ensure it follows best practices. - -assistant: "I'll use the skill-reviewer agent to review the skill." - - - -Context: User requests skill review -user: "Review my skill and tell me how to improve it" -assistant: "I'll use the skill-reviewer agent to analyze the skill quality." - -Explicit skill review request triggers the agent. - - - - -Context: User modified skill description -user: "I updated the skill description, does it look good?" -assistant: "I'll use the skill-reviewer agent to review the changes." - -Skill description modified, review for triggering effectiveness. - - +description: |- + Use this agent when the user has created or modified a skill and needs quality review, asks to "review my skill", "check skill quality", "improve skill description", or wants to ensure skill follows best practices. Trigger proactively after skill creation. Examples: + + + Context: User just created a new skill + user: "I've created a PDF processing skill" + assistant: "Great! Let me review the skill quality." + + Skill created, proactively trigger skill-reviewer to ensure it follows best practices. + + assistant: "I'll use the skill-reviewer agent to review the skill." + + + + Context: User requests skill review + user: "Review my skill and tell me how to improve it" + assistant: "I'll use the skill-reviewer agent to analyze the skill quality." + + Explicit skill review request triggers the agent. + + + + + Context: User modified skill description + user: "I updated the skill description, does it look good?" + assistant: "I'll use the skill-reviewer agent to review the changes." + + Skill description modified, review for triggering effectiveness. + + model: inherit color: cyan diff --git a/plugins/pr-review-toolkit/agents/code-reviewer.md b/plugins/pr-review-toolkit/agents/code-reviewer.md index 462f2e0..7a793f0 100644 --- a/plugins/pr-review-toolkit/agents/code-reviewer.md +++ b/plugins/pr-review-toolkit/agents/code-reviewer.md @@ -1,6 +1,7 @@ --- name: code-reviewer -description: 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. \n\nExamples:\n\nContext: The user has just implemented a new feature with several TypeScript files.\nuser: "I've added the new authentication feature. Can you check if everything looks good?"\nassistant: "I'll use the Task tool to launch the code-reviewer agent to review your recent changes."\n\nSince the user has completed a feature and wants validation, use the code-reviewer agent to ensure the code meets project standards.\n\n\n\nContext: The assistant has just written a new utility function.\nuser: "Please create a function to validate email addresses"\nassistant: "Here's the email validation function:"\n\nassistant: "Now I'll use the Task tool to launch the code-reviewer agent to review this implementation."\n\nProactively use the code-reviewer agent after writing new code to catch issues early.\n\n\n\nContext: The user is about to create a PR.\nuser: "I think I'm ready to create a PR for this feature"\nassistant: "Before creating the PR, I'll use the Task tool to launch the code-reviewer agent to ensure all code meets our standards."\n\nProactively review code before PR creation to avoid review comments and iterations.\n\n +description: |- + 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. \n\nExamples:\n\nContext: The user has just implemented a new feature with several TypeScript files.\nuser: "I've added the new authentication feature. Can you check if everything looks good?"\nassistant: "I'll use the Task tool to launch the code-reviewer agent to review your recent changes."\n\nSince the user has completed a feature and wants validation, use the code-reviewer agent to ensure the code meets project standards.\n\n\n\nContext: The assistant has just written a new utility function.\nuser: "Please create a function to validate email addresses"\nassistant: "Here's the email validation function:"\n\nassistant: "Now I'll use the Task tool to launch the code-reviewer agent to review this implementation."\n\nProactively use the code-reviewer agent after writing new code to catch issues early.\n\n\n\nContext: The user is about to create a PR.\nuser: "I think I'm ready to create a PR for this feature"\nassistant: "Before creating the PR, I'll use the Task tool to launch the code-reviewer agent to ensure all code meets our standards."\n\nProactively review code before PR creation to avoid review comments and iterations.\n\n model: opus color: green --- diff --git a/plugins/pr-review-toolkit/agents/code-simplifier.md b/plugins/pr-review-toolkit/agents/code-simplifier.md index 7d6cfd8..83ee0d0 100644 --- a/plugins/pr-review-toolkit/agents/code-simplifier.md +++ b/plugins/pr-review-toolkit/agents/code-simplifier.md @@ -1,37 +1,38 @@ --- name: code-simplifier -description: Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by following project best practices while retaining all functionality. The agent focuses only on recently modified code unless instructed otherwise.\n\nExamples:\n\n -Context: The assistant has just implemented a new feature that adds user authentication to an API endpoint. -user: "Please add authentication to the /api/users endpoint" -assistant: "I've implemented the authentication for the /api/users endpoint. Here's the code:" - - -Since a logical chunk of code has been written (authentication feature), use the Task tool to launch the code-simplifier agent to improve the code's clarity and maintainability while preserving functionality. - -assistant: "Now let me use the code-simplifier agent to refine this implementation for better clarity and maintainability" - +description: |- + Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by following project best practices while retaining all functionality. The agent focuses only on recently modified code unless instructed otherwise.\n\nExamples:\n\n + Context: The assistant has just implemented a new feature that adds user authentication to an API endpoint. + user: "Please add authentication to the /api/users endpoint" + assistant: "I've implemented the authentication for the /api/users endpoint. Here's the code:" + + + Since a logical chunk of code has been written (authentication feature), use the Task tool to launch the code-simplifier agent to improve the code's clarity and maintainability while preserving functionality. + + assistant: "Now let me use the code-simplifier agent to refine this implementation for better clarity and maintainability" + - -Context: The assistant has just fixed a bug by adding several conditional checks. -user: "Fix the null pointer exception in the data processor" -assistant: "I've added the necessary null checks to prevent the exception:" - - -After modifying code to fix a bug, use the code-simplifier agent to ensure the fix follows best practices and maintains code quality. - -assistant: "Let me refine this bug fix using the code-simplifier agent to ensure it follows our best practices" - + + Context: The assistant has just fixed a bug by adding several conditional checks. + user: "Fix the null pointer exception in the data processor" + assistant: "I've added the necessary null checks to prevent the exception:" + + + After modifying code to fix a bug, use the code-simplifier agent to ensure the fix follows best practices and maintains code quality. + + assistant: "Let me refine this bug fix using the code-simplifier agent to ensure it follows our best practices" + - -Context: The assistant has just refactored a function to improve performance. -user: "Optimize the data sorting algorithm for better performance" -assistant: "I've optimized the sorting algorithm. Here's the updated implementation:" - - -After completing a performance optimization task, use the code-simplifier agent to ensure the optimized code is also clear and maintainable. - -assistant: "Now I'll use the code-simplifier agent to ensure the optimized code is also clear and follows our coding standards" - + + Context: The assistant has just refactored a function to improve performance. + user: "Optimize the data sorting algorithm for better performance" + assistant: "I've optimized the sorting algorithm. Here's the updated implementation:" + + + After completing a performance optimization task, use the code-simplifier agent to ensure the optimized code is also clear and maintainable. + + assistant: "Now I'll use the code-simplifier agent to ensure the optimized code is also clear and follows our coding standards" + model: opus --- diff --git a/plugins/pr-review-toolkit/agents/comment-analyzer.md b/plugins/pr-review-toolkit/agents/comment-analyzer.md index e214620..e39423b 100644 --- a/plugins/pr-review-toolkit/agents/comment-analyzer.md +++ b/plugins/pr-review-toolkit/agents/comment-analyzer.md @@ -1,6 +1,7 @@ --- name: comment-analyzer -description: Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes: (1) After generating large documentation comments or docstrings, (2) Before finalizing a pull request that adds or modifies comments, (3) When reviewing existing comments for potential technical debt or comment rot, (4) When you need to verify that comments accurately reflect the code they describe.\n\n\nContext: The user is working on a pull request that adds several documentation comments to functions.\nuser: "I've added documentation to these functions. Can you check if the comments are accurate?"\nassistant: "I'll use the comment-analyzer agent to thoroughly review all the comments in this pull request for accuracy and completeness."\n\nSince the user has added documentation comments and wants them checked, use the comment-analyzer agent to verify their accuracy against the actual code.\n\n\n\n\nContext: The user just asked to generate comprehensive documentation for a complex function.\nuser: "Add detailed documentation for this authentication handler function"\nassistant: "I've added the documentation. Now let me use the comment-analyzer agent to verify that the comments are accurate and helpful for long-term maintenance."\n\nAfter generating large documentation comments, proactively use the comment-analyzer to ensure quality.\n\n\n\n\nContext: The user is preparing to create a pull request with multiple code changes and comments.\nuser: "I think we're ready to create the PR now"\nassistant: "Before creating the pull request, let me use the comment-analyzer agent to review all the comments we've added or modified to ensure they're accurate and won't create technical debt."\n\nBefore finalizing a PR, use the comment-analyzer to review all comment changes.\n\n +description: |- + Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes: (1) After generating large documentation comments or docstrings, (2) Before finalizing a pull request that adds or modifies comments, (3) When reviewing existing comments for potential technical debt or comment rot, (4) When you need to verify that comments accurately reflect the code they describe.\n\n\nContext: The user is working on a pull request that adds several documentation comments to functions.\nuser: "I've added documentation to these functions. Can you check if the comments are accurate?"\nassistant: "I'll use the comment-analyzer agent to thoroughly review all the comments in this pull request for accuracy and completeness."\n\nSince the user has added documentation comments and wants them checked, use the comment-analyzer agent to verify their accuracy against the actual code.\n\n\n\n\nContext: The user just asked to generate comprehensive documentation for a complex function.\nuser: "Add detailed documentation for this authentication handler function"\nassistant: "I've added the documentation. Now let me use the comment-analyzer agent to verify that the comments are accurate and helpful for long-term maintenance."\n\nAfter generating large documentation comments, proactively use the comment-analyzer to ensure quality.\n\n\n\n\nContext: The user is preparing to create a pull request with multiple code changes and comments.\nuser: "I think we're ready to create the PR now"\nassistant: "Before creating the pull request, let me use the comment-analyzer agent to review all the comments we've added or modified to ensure they're accurate and won't create technical debt."\n\nBefore finalizing a PR, use the comment-analyzer to review all comment changes.\n\n model: inherit color: green --- diff --git a/plugins/pr-review-toolkit/agents/pr-test-analyzer.md b/plugins/pr-review-toolkit/agents/pr-test-analyzer.md index 9b2de05..ef82db0 100644 --- a/plugins/pr-review-toolkit/agents/pr-test-analyzer.md +++ b/plugins/pr-review-toolkit/agents/pr-test-analyzer.md @@ -1,6 +1,7 @@ --- name: pr-test-analyzer -description: Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n\nContext: Daisy has just created a pull request with new functionality.\nuser: "I've created the PR. Can you check if the tests are thorough?"\nassistant: "I'll use the pr-test-analyzer agent to review the test coverage and identify any critical gaps."\n\nSince Daisy is asking about test thoroughness in a PR, use the Task tool to launch the pr-test-analyzer agent.\n\n\n\n\nContext: A pull request has been updated with new code changes.\nuser: "The PR is ready for review - I added the new validation logic we discussed"\nassistant: "Let me analyze the PR to ensure the tests adequately cover the new validation logic and edge cases."\n\nThe PR has new functionality that needs test coverage analysis, so use the pr-test-analyzer agent.\n\n\n\n\nContext: Reviewing PR feedback before marking as ready.\nuser: "Before I mark this PR as ready, can you double-check the test coverage?"\nassistant: "I'll use the pr-test-analyzer agent to thoroughly review the test coverage and identify any critical gaps before you mark it ready."\n\nDaisy wants a final test coverage check before marking PR ready, use the pr-test-analyzer agent.\n\n +description: |- + Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n\nContext: Daisy has just created a pull request with new functionality.\nuser: "I've created the PR. Can you check if the tests are thorough?"\nassistant: "I'll use the pr-test-analyzer agent to review the test coverage and identify any critical gaps."\n\nSince Daisy is asking about test thoroughness in a PR, use the Task tool to launch the pr-test-analyzer agent.\n\n\n\n\nContext: A pull request has been updated with new code changes.\nuser: "The PR is ready for review - I added the new validation logic we discussed"\nassistant: "Let me analyze the PR to ensure the tests adequately cover the new validation logic and edge cases."\n\nThe PR has new functionality that needs test coverage analysis, so use the pr-test-analyzer agent.\n\n\n\n\nContext: Reviewing PR feedback before marking as ready.\nuser: "Before I mark this PR as ready, can you double-check the test coverage?"\nassistant: "I'll use the pr-test-analyzer agent to thoroughly review the test coverage and identify any critical gaps before you mark it ready."\n\nDaisy wants a final test coverage check before marking PR ready, use the pr-test-analyzer agent.\n\n model: inherit color: cyan --- diff --git a/plugins/pr-review-toolkit/agents/silent-failure-hunter.md b/plugins/pr-review-toolkit/agents/silent-failure-hunter.md index b8a8dfa..575109d 100644 --- a/plugins/pr-review-toolkit/agents/silent-failure-hunter.md +++ b/plugins/pr-review-toolkit/agents/silent-failure-hunter.md @@ -1,6 +1,7 @@ --- name: silent-failure-hunter -description: Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could potentially suppress errors. Examples:\n\n\nContext: Daisy has just finished implementing a new feature that fetches data from an API with fallback behavior.\nDaisy: "I've added error handling to the API client. Can you review it?"\nAssistant: "Let me use the silent-failure-hunter agent to thoroughly examine the error handling in your changes."\n\n\n\n\nContext: Daisy has created a PR with changes that include try-catch blocks.\nDaisy: "Please review PR #1234"\nAssistant: "I'll use the silent-failure-hunter agent to check for any silent failures or inadequate error handling in this PR."\n\n\n\n\nContext: Daisy has just refactored error handling code.\nDaisy: "I've updated the error handling in the authentication module"\nAssistant: "Let me proactively use the silent-failure-hunter agent to ensure the error handling changes don't introduce silent failures."\n\n +description: |- + Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could potentially suppress errors. Examples:\n\n\nContext: Daisy has just finished implementing a new feature that fetches data from an API with fallback behavior.\nDaisy: "I've added error handling to the API client. Can you review it?"\nAssistant: "Let me use the silent-failure-hunter agent to thoroughly examine the error handling in your changes."\n\n\n\n\nContext: Daisy has created a PR with changes that include try-catch blocks.\nDaisy: "Please review PR #1234"\nAssistant: "I'll use the silent-failure-hunter agent to check for any silent failures or inadequate error handling in this PR."\n\n\n\n\nContext: Daisy has just refactored error handling code.\nDaisy: "I've updated the error handling in the authentication module"\nAssistant: "Let me proactively use the silent-failure-hunter agent to ensure the error handling changes don't introduce silent failures."\n\n model: inherit color: yellow --- diff --git a/plugins/pr-review-toolkit/agents/type-design-analyzer.md b/plugins/pr-review-toolkit/agents/type-design-analyzer.md index f720f0f..1a32842 100644 --- a/plugins/pr-review-toolkit/agents/type-design-analyzer.md +++ b/plugins/pr-review-toolkit/agents/type-design-analyzer.md @@ -1,6 +1,7 @@ --- name: type-design-analyzer -description: Use this agent when you need expert analysis of type design in your codebase. Specifically use it: (1) when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, (2) during pull request creation to review all types being added, (3) when refactoring existing types to improve their design quality. The agent will provide both qualitative feedback and quantitative ratings on encapsulation, invariant expression, usefulness, and enforcement.\n\n\nContext: Daisy is writing code that introduces a new UserAccount type and wants to ensure it has well-designed invariants.\nuser: "I've just created a new UserAccount type that handles user authentication and permissions"\nassistant: "I'll use the type-design-analyzer agent to review the UserAccount type design"\n\nSince a new type is being introduced, use the type-design-analyzer to ensure it has strong invariants and proper encapsulation.\n\n\n\n\nContext: Daisy is creating a pull request and wants to review all newly added types.\nuser: "I'm about to create a PR with several new data model types"\nassistant: "Let me use the type-design-analyzer agent to review all the types being added in this PR"\n\nDuring PR creation with new types, use the type-design-analyzer to review their design quality.\n\n +description: |- + Use this agent when you need expert analysis of type design in your codebase. Specifically use it: (1) when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, (2) during pull request creation to review all types being added, (3) when refactoring existing types to improve their design quality. The agent will provide both qualitative feedback and quantitative ratings on encapsulation, invariant expression, usefulness, and enforcement.\n\n\nContext: Daisy is writing code that introduces a new UserAccount type and wants to ensure it has well-designed invariants.\nuser: "I've just created a new UserAccount type that handles user authentication and permissions"\nassistant: "I'll use the type-design-analyzer agent to review the UserAccount type design"\n\nSince a new type is being introduced, use the type-design-analyzer to ensure it has strong invariants and proper encapsulation.\n\n\n\n\nContext: Daisy is creating a pull request and wants to review all newly added types.\nuser: "I'm about to create a PR with several new data model types"\nassistant: "Let me use the type-design-analyzer agent to review all the types being added in this PR"\n\nDuring PR creation with new types, use the type-design-analyzer to review their design quality.\n\n model: inherit color: pink --- @@ -58,13 +59,13 @@ Provide your analysis in this structure: ### Ratings - **Encapsulation**: X/10 [Brief justification] - + - **Invariant Expression**: X/10 [Brief justification] - + - **Invariant Usefulness**: X/10 [Brief justification] - + - **Invariant Enforcement**: X/10 [Brief justification]