GitHub workflow patterns for Orchestrator AI. Branch naming, PR process, code review, CI/CD. CRITICAL: Use conventional branch names (feature/, fix/, chore/). PRs require quality gates to pass.
CRITICAL: Follow GitHub workflow patterns: conventional branch names, PR process, quality gates, code review.
Use this skill when:
feature/user-authentication
feature/add-api-endpoint
fix/login-bug
fix/memory-leak
chore/update-dependencies
chore/refactor-service
docs/update-readme
test/add-unit-tests
❌ my-feature
❌ bugfix
❌ update
❌ new-stuff
❌ feature_branch (use hyphens, not underscores)
| Type | Prefix | Example | Purpose |
|---|---|---|---|
| Feature | feature/ |
feature/user-auth |
New features |
| Bug Fix | fix/ |
fix/login-error |
Bug fixes |
| Chore | chore/ |
chore/update-deps |
Maintenance tasks |
| Documentation | docs/ |
docs/api-guide |
Documentation updates |
| Test | test/ |
test/unit-tests |
Test additions |
| Refactor | refactor/ |
refactor/service-layer |
Code refactoring |
# Create feature branch
git checkout -b feature/user-authentication
# Or fix branch
git checkout -b fix/login-bug
# Edit files
vim apps/api/src/auth/auth.service.ts
# Stage changes
git add .
# Commit with conventional commit message
git commit -m "feat(auth): add user authentication"
# Push branch to remote
git push origin feature/user-authentication
PR must pass:
npm run format)npm run lint)npm test)npm run build)Once approved and quality gates pass:
## Description
Brief description of changes
## Type of Change
- [ ] Feature
- [ ] Bug Fix
- [ ] Chore
- [ ] Documentation
- [ ] Refactor
## Changes Made
- Change 1
- Change 2
- Change 3
## Testing
How to test these changes:
1. Step 1
2. Step 2
3. Step 3
## Screenshots (if applicable)
[Add screenshots for UI changes]
## Checklist
- [ ] Code follows project conventions
- [ ] Self-review completed
- [ ] Comments added for complex code
- [ ] Documentation updated
- [ ] No new warnings generated
- [ ] Tests added/updated
- [ ] All tests pass locally
# .github/workflows/ci.yml
name: CI
on:
push:
branches: [main, develop]
pull_request:
branches: [main, develop]
jobs:
quality:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: '18'
- run: npm ci
- run: npm run format -- --check
- run: npm run lint
- run: npm test
- run: npm run build
# Good review comment
```typescript
// Consider using environment variable instead of hardcoded value
const apiUrl = process.env.API_URL || 'http://localhost:7100';
# Another good review comment
```typescript
// Should we add error handling here?
const result = await service.call();
## Common Workflow Patterns
### Pattern 1: Feature Development
```bash
# 1. Create feature branch
git checkout -b feature/new-feature
# 2. Make changes and commit
git add .
git commit -m "feat(module): add new feature"
# 3. Push and open PR
git push origin feature/new-feature
# Open PR on GitHub
# 4. Address review comments
git add .
git commit -m "fix(module): address review comments"
git push
# 5. Merge after approval
# 1. Create fix branch from main
git checkout main
git pull
git checkout -b fix/critical-bug
# 2. Fix and commit
git add .
git commit -m "fix(module): fix critical bug"
# 3. Push and open PR
git push origin fix/critical-bug
# Open PR, request urgent review
# 4. Merge immediately after approval
Recommended branch protection for main:
When working with GitHub:
feature/, fix/, etc.)