Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR introduces the initial implementation of Classy Claude Commands (CCC) by adding comprehensive documentation and the first two specialized agents for Claude Code development workflows.
- Adds foundational documentation explaining the project structure, command philosophy, and development patterns
- Creates visual workflow documentation with Mermaid flowcharts for key command processes
- Introduces first two agents: pytest-test-writer for comprehensive Python testing and bug-fixer for systematic error resolution
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds detailed Mermaid flowcharts documenting the workflows of three core commands |
| CLAUDE.md | Comprehensive project guide explaining command structure, development patterns, and integration points |
| CHANGELOG.md | Initial changelog documenting the addition of 10 specialized Claude Code commands |
| .claude/agents/pytest-test-writer.md | Agent definition for comprehensive Python test coverage using pytest |
| .claude/agents/bug-fixer.md | Agent definition for systematic bug analysis and resolution workflows |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| @@ -0,0 +1,61 @@ | |||
| --- | |||
| name: pytest-test-writer | |||
| description: Use this agent when you need comprehensive test coverage for Python code using pytest. Examples: <example>Context: User has written a new function and wants thorough test coverage. user: 'I just wrote this authentication function, can you write tests for it?' assistant: 'I'll use the pytest-test-writer agent to create comprehensive tests with edge cases and mocking strategies.' <commentary>The user needs test coverage for new code, so use the pytest-test-writer agent to analyze the function and create a detailed testing plan.</commentary></example> <example>Context: User wants to improve existing test coverage. user: 'Our user service module only has 60% test coverage, we need to get it to 100%' assistant: 'Let me use the pytest-test-writer agent to analyze the gaps and create additional tests.' <commentary>The user needs comprehensive test coverage improvement, so use the pytest-test-writer agent to identify untested code paths and create appropriate tests.</commentary></example> | |||
There was a problem hiding this comment.
[nitpick] This extremely long single-line description field is difficult to read and maintain. Consider breaking it into multiple lines or moving the examples to a separate section for better readability.
| description: Use this agent when you need comprehensive test coverage for Python code using pytest. Examples: <example>Context: User has written a new function and wants thorough test coverage. user: 'I just wrote this authentication function, can you write tests for it?' assistant: 'I'll use the pytest-test-writer agent to create comprehensive tests with edge cases and mocking strategies.' <commentary>The user needs test coverage for new code, so use the pytest-test-writer agent to analyze the function and create a detailed testing plan.</commentary></example> <example>Context: User wants to improve existing test coverage. user: 'Our user service module only has 60% test coverage, we need to get it to 100%' assistant: 'Let me use the pytest-test-writer agent to analyze the gaps and create additional tests.' <commentary>The user needs comprehensive test coverage improvement, so use the pytest-test-writer agent to identify untested code paths and create appropriate tests.</commentary></example> | |
| description: > | |
| Use this agent when you need comprehensive test coverage for Python code using pytest. | |
| examples: | |
| - context: User has written a new function and wants thorough test coverage. | |
| user: "I just wrote this authentication function, can you write tests for it?" | |
| assistant: "I'll use the pytest-test-writer agent to create comprehensive tests with edge cases and mocking strategies." | |
| commentary: "The user needs test coverage for new code, so use the pytest-test-writer agent to analyze the function and create a detailed testing plan." | |
| - context: User wants to improve existing test coverage. | |
| user: "Our user service module only has 60% test coverage, we need to get it to 100%" | |
| assistant: "Let me use the pytest-test-writer agent to analyze the gaps and create additional tests." | |
| commentary: "The user needs comprehensive test coverage improvement, so use the pytest-test-writer agent to identify untested code paths and create appropriate tests." |
| @@ -0,0 +1,70 @@ | |||
| --- | |||
| name: bug-fixer | |||
| description: Use this agent when you encounter bugs, errors, or unexpected behavior in your code that need systematic analysis and resolution. Examples: <example>Context: User encounters a Python traceback error when running their application. user: 'I'm getting a KeyError when trying to access user data in my Flask app' assistant: 'I'll use the bug-fixer agent to systematically analyze this error and develop a solution plan.' <commentary>Since the user is reporting a bug, use the bug-fixer agent to analyze the issue, understand the codebase context, and create a structured fix plan.</commentary></example> <example>Context: User notices their tests are failing after recent changes. user: 'My tests started failing after I refactored the authentication module, but I'm not sure what's causing it' assistant: 'Let me use the bug-fixer agent to analyze the test failures and trace them back to the root cause in your refactored code.' <commentary>The user has a bug manifesting as test failures, so use the bug-fixer agent to systematically diagnose and fix the issue.</commentary></example> | |||
There was a problem hiding this comment.
[nitpick] This extremely long single-line description field is difficult to read and maintain. Consider breaking it into multiple lines or moving the examples to a separate section for better readability.
| description: Use this agent when you encounter bugs, errors, or unexpected behavior in your code that need systematic analysis and resolution. Examples: <example>Context: User encounters a Python traceback error when running their application. user: 'I'm getting a KeyError when trying to access user data in my Flask app' assistant: 'I'll use the bug-fixer agent to systematically analyze this error and develop a solution plan.' <commentary>Since the user is reporting a bug, use the bug-fixer agent to analyze the issue, understand the codebase context, and create a structured fix plan.</commentary></example> <example>Context: User notices their tests are failing after recent changes. user: 'My tests started failing after I refactored the authentication module, but I'm not sure what's causing it' assistant: 'Let me use the bug-fixer agent to analyze the test failures and trace them back to the root cause in your refactored code.' <commentary>The user has a bug manifesting as test failures, so use the bug-fixer agent to systematically diagnose and fix the issue.</commentary></example> | |
| description: | | |
| Use this agent when you encounter bugs, errors, or unexpected behavior in your code that need systematic analysis and resolution. | |
| examples: | |
| - context: User encounters a Python traceback error when running their application. | |
| user: "I'm getting a KeyError when trying to access user data in my Flask app" | |
| assistant: "I'll use the bug-fixer agent to systematically analyze this error and develop a solution plan." | |
| commentary: "Since the user is reporting a bug, use the bug-fixer agent to analyze the issue, understand the codebase context, and create a structured fix plan." | |
| - context: User notices their tests are failing after recent changes. | |
| user: "My tests started failing after I refactored the authentication module, but I'm not sure what's causing it" | |
| assistant: "Let me use the bug-fixer agent to analyze the test failures and trace them back to the root cause in your refactored code." | |
| commentary: "The user has a bug manifesting as test failures, so use the bug-fixer agent to systematically diagnose and fix the issue." |
There was a problem hiding this comment.
Ptdr, tu critiques le taff de ton pote en fait?
No description provided.