Menu
Branch naming, commit messages, PR conventions, and merge strategy for clean, traceable git history.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Rules and strategies for managing agent context window size, avoiding bloat, and preserving signal-to-noise ratio.
Standard patterns for error handling, retry logic, circuit breakers, and graceful degradation.
Detect and remove contradictions across agent policies before execution.
Multi-step tool workflows via code orchestration to reduce latency, context pollution, and token overhead.
Bind project-specific prompts to local schema and workflow artifacts while keeping the harness core generic and globally reusable.
Operational session protocol for task-scoped leases, reconciliation, checkpoints, inspection, queue promotion, and handoff across long-running work.
| name | git-workflow |
| description | Branch naming, commit messages, PR conventions, and merge strategy for clean, traceable git history. |
Enforce clean, traceable git history with consistent branch naming, commit messages, and PR conventions.
Format: <type>/<issue-id>-<short-description>
| Type | Use for |
|---|---|
feat/ | New features |
fix/ | Bug fixes |
refactor/ | Code restructuring without behavior change |
chore/ | Build, CI, tooling, dependencies |
test/ | Test additions or fixes |
docs/ | Documentation only |
hotfix/ | Urgent production fixes |
Examples:
feat/M1-I3-user-authenticationfix/M2-I1-null-pointer-on-empty-listchore/update-eslint-configFormat: <type>(<scope>): <description>
Rules:
Examples:
feat(auth): add JWT refresh token rotation
fix(api): prevent duplicate webhook delivery on retry
refactor(db): extract query builder from repository layer
chore(deps): bump express from 4.18 to 4.21
Multi-line example:
fix(payments): handle race condition in concurrent refunds
Two simultaneous refund requests could both succeed because the
balance check was not atomic. Wrapped in a database transaction
with SELECT FOR UPDATE to prevent double-spending.
Closes #42
Same format as commit: <type>(<scope>): <description>
## What
Brief description of the change.
## Why
Context: what problem this solves or what feature it delivers.
## How
Key implementation decisions (not a line-by-line walkthrough).
## Testing
- [ ] Unit tests added/updated
- [ ] Integration tests (if applicable)
- [ ] Manual verification steps
## Related
- Closes #<issue_number>
- Depends on #<pr_number> (if any)
| Scenario | Strategy |
|---|---|
| Feature branch → main | Squash merge (clean history) |
| Long-lived branch → main | Merge commit (preserve branch history) |
| Hotfix → main | Fast-forward or squash |
| main → feature branch (sync) | Rebase (keep linear history) |
github-sync — label and milestone alignment for issues/PRscompletion-gate — quality gate before mergemy-branch, wip, test2)fix, update, wip, asdf