1
0
mirror of https://github.com/steipete/agent-rules.git synced 2025-12-16 12:00:09 +01:00
Files
Peter Steinberger b14f443855 Add 15 new development workflow rules from claude-code
Added comprehensive rules adapted from vincenthopf/claude-code:

Development Workflows:
- commit.mdc, commit-fast.mdc: Git commit workflows
- add-to-changelog.mdc: Structured changelog updates
- pr-review.mdc: Multi-role PR review checklist

Code Quality:
- check.mdc: Multi-language code quality checks
- clean.mdc: Auto-fix formatting and linting
- code-analysis.mdc: Advanced analysis options

Problem Solving:
- analyze-issue.mdc: GitHub issue analysis
- bug-fix.mdc: Complete bug-fixing workflow
- implement-task.mdc: Methodical implementation
- five.mdc: Five Whys root cause analysis

Documentation:
- create-docs.mdc: Comprehensive doc generation
- mermaid.mdc: Diagram generation

Project Setup:
- context-prime.mdc: Load project context
- create-command.mdc: Create custom commands

Credit: @vincenthopf (https://github.com/vincenthopf/claude-code)

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-06-12 14:19:32 +02:00

31 lines
941 B
Plaintext

# Bug Fix
Streamline bug fixing workflow from issue creation to pull request.
## Process:
### Before Starting:
1. **GitHub**: Create an issue with a short descriptive title
2. **Git**: Create and checkout a feature branch (`git checkout -b fix/<issue-description>`)
### Fix the Bug:
1. Reproduce the issue
2. Write failing test that demonstrates the bug
3. Implement the fix
4. Verify test passes
5. Run full test suite
6. Review code changes
### On Completion:
1. **Git**: Commit with descriptive message referencing the issue
- Format: `fix: <description> (#<issue-number>)`
2. **Git**: Push the branch to remote repository
3. **GitHub**: Create PR and link the issue
- Use "Fixes #<issue-number>" in PR description
- Add relevant labels and reviewers
## Best Practices:
- Keep changes focused on the specific bug
- Include regression tests
- Update documentation if behavior changes
- Consider edge cases and related issues