mirror of
https://github.com/steipete/agent-rules.git
synced 2025-12-16 12:00:09 +01:00
b14f443855
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>
44 lines
1.5 KiB
Plaintext
44 lines
1.5 KiB
Plaintext
# Commit
|
|
|
|
Create well-formatted commits with conventional commit messages and emojis.
|
|
|
|
## Features:
|
|
- Runs pre-commit checks by default (lint, build, generate docs)
|
|
- Automatically stages files if none are staged
|
|
- Uses conventional commit format with descriptive emojis
|
|
- Suggests splitting commits for different concerns
|
|
|
|
## Usage:
|
|
- `/commit` - Standard commit with pre-commit checks
|
|
- `/commit --no-verify` - Skip pre-commit checks
|
|
|
|
## Commit Types:
|
|
- ✨ feat: New features
|
|
- 🐛 fix: Bug fixes
|
|
- 📝 docs: Documentation changes
|
|
- ♻️ refactor: Code restructuring without changing functionality
|
|
- 🎨 style: Code formatting, missing semicolons, etc.
|
|
- ⚡️ perf: Performance improvements
|
|
- ✅ test: Adding or correcting tests
|
|
- 🧑💻 chore: Tooling, configuration, maintenance
|
|
- 🚧 wip: Work in progress
|
|
- 🔥 remove: Removing code or files
|
|
- 🚑 hotfix: Critical fixes
|
|
- 🔒 security: Security improvements
|
|
|
|
## Process:
|
|
1. Check for staged changes (`git status`)
|
|
2. If no staged changes, review and stage appropriate files
|
|
3. Run pre-commit checks (unless --no-verify)
|
|
4. Analyze changes to determine commit type
|
|
5. Generate descriptive commit message
|
|
6. Include scope if applicable: `type(scope): description`
|
|
7. Add body for complex changes explaining why
|
|
8. Execute commit
|
|
|
|
## Best Practices:
|
|
- Keep commits atomic and focused
|
|
- Write in imperative mood ("Add feature" not "Added feature")
|
|
- Explain why, not just what
|
|
- Reference issues/PRs when relevant
|
|
- Split unrelated changes into separate commits |