mirror of
https://github.com/alirezarezvani/ClaudeForge.git
synced 2026-07-03 10:23:15 -04:00
6d954fefee
Phase 4: Claude Code Slash Commands Created 4 GitHub Integration Commands: 1. /github-init - CI/CD system initialization - Runs bootstrap workflow - Creates dev branch - Configures branch protection - Sets default branch to dev - Complete setup verification 2. /commit-smart - Smart commits with quality gates - Pre-commit validation (Python, Bash, secrets) - Conventional Commits format generation - Interactive commit message builder - Quality checks before committing 3. /create-pr - Pull request creation - Branch validation - Target branch detection (dev/main) - PR title generation (Conventional Commits) - PR template population - Workflow trigger explanation 4. /release - GitHub release creation - Version validation (semantic versioning) - CHANGELOG.md integration - Automated release notes - Post-release actions guide All commands provide: - Step-by-step guidance - Copy-paste ready commands - Validation checks - Error handling - Links to documentation Integration with workflows: - Commands trigger bootstrap, pr-into-dev, dev-to-main, release workflows - Enforces quality gates and conventions - Aligns with branching strategy Next: Test workflows with sample feature PR
2.5 KiB
2.5 KiB
title, description
| title | description |
|---|---|
| /github-init | Initialize ClaudeForge CI/CD system |
GitHub CI/CD Initialization
You are helping the user initialize the ClaudeForge CI/CD system.
Workflow
-
Check Current State
- Verify
.github/workflows/directory exists - Check if bootstrap workflow has been run (look for labels/milestones)
- Check if dev branch exists
- Check branch protection status
- Verify
-
Run Bootstrap Workflow
- If not yet run, guide user to run bootstrap workflow:
- Go to Actions → Bootstrap Repository → Run workflow
- Enable all options (create labels, milestones, validate settings)
- Explain what will be created (23 labels, 3 milestones)
- If not yet run, guide user to run bootstrap workflow:
-
Create Dev Branch (if not exists)
git checkout -b dev git push -u origin dev -
Configure Branch Protection
Guide user step-by-step:
For main branch:
- Go to Settings → Branches → Add rule
- Pattern:
main - Enable:
- Require PR before merging
- Require status checks:
quality-gates,production-build,validate-release-pr - Require linear history
- Block force pushes
- Restrict deletions
For dev branch:
- Pattern:
dev - Enable:
- Require PR before merging
- Require status checks:
quality-gates,validate-pr - Require linear history
- Block force pushes
- Restrict deletions
-
Set Default Branch
- Settings → General → Default branch → Change to
dev - This ensures new PRs target dev by default
- Settings → General → Default branch → Change to
-
Verification
- Show current branch protection rules
- Verify workflows are present
- Confirm setup is complete
-
Next Steps
- Point to docs/GITHUB_WORKFLOWS.md for workflow reference
- Point to docs/BRANCHING_STRATEGY.md for branch flow
- Suggest creating first feature branch to test
Commands to provide
# Check current setup
gh repo view --json name,defaultBranchRef,hasIssuesEnabled
# List workflows
ls -la .github/workflows/
# Check labels
gh label list
# Check milestones
gh api repos/:owner/:repo/milestones
# Check branch protection
gh api repos/:owner/:repo/branches/main/protection 2>/dev/null || echo "Not protected"
gh api repos/:owner/:repo/branches/dev/protection 2>/dev/null || echo "Not protected"
Success Criteria
✅ Bootstrap workflow run successfully ✅ Dev branch created and pushed ✅ Branch protection configured for main and dev ✅ Default branch set to dev ✅ User understands next steps
Provide clear, step-by-step guidance with actual commands the user can copy-paste.