mirror of
https://github.com/alirezarezvani/ClaudeForge.git
synced 2026-07-03 10:23:15 -04:00
Reza Rezvani
078bf9f418
- Add CI/CD workflow change type - Expand checklist with quality gates sections - Add Conventional Commits and branch naming reminders - Better organize code quality, docs, testing, CI/CD sections This file was modified in Phase 2 but accidentally not staged.
2.2 KiB
2.2 KiB
Pull Request
Description
Provide a clear and concise description of your changes.
Type of Change
- Bug fix (non-breaking change fixing an issue)
- New feature (non-breaking change adding functionality)
- Breaking change (fix or feature causing existing functionality to change)
- Documentation update
- Code refactoring
- Performance improvement
- Test addition/improvement
- CI/CD workflow change
Related Issues
Closes #(issue_number)
Changes Made
- Change 1
- Change 2
- Change 3
Testing Performed
Describe the tests you ran to verify your changes:
- Tested installation (./install.sh)
- Tested slash command (/enhance-claude-md)
- Tested guardian agent
- Tested on new project
- Tested on existing project with CLAUDE.md
- Tested modular architecture
Test Environment:
- OS: [e.g., macOS 13.5]
- Claude Code Version: [e.g., 2.1.0]
Screenshots (if applicable)
Add screenshots to help explain your changes.
Checklist
Code Quality
- My code follows the project's style guidelines
- Python syntax is valid (if applicable)
- Bash scripts have valid syntax (if applicable)
- Markdown files are properly formatted
- No hardcoded secrets or sensitive data
- I have commented my code where necessary
Documentation
- I have updated the documentation (if needed)
- I have updated CHANGELOG.md with my changes (for releases)
- README.md is updated if user-facing changes
Testing
- I have tested my changes thoroughly
- Tested installation (./install.sh or install.ps1)
- Tested slash command (/enhance-claude-md) if applicable
- Tested guardian agent if applicable
- Tested on target environment (macOS/Linux/Windows)
CI/CD
- PR title follows Conventional Commits format (e.g.,
feat(installer): add feature) - Branch name follows convention (feature/, fix/, hotfix/, etc.)
- All quality gates passing
- No merge conflicts with target branch
Additional Notes
Any additional information reviewers should know.