Menú
Branching strategy, commit discipline, PR hygiene, and semantic versioning
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Build UIs that work for all users including keyboard navigation, screen readers, and WCAG 2.2
Design multi-agent systems with robust tool interfaces, state management, and failure handling
Build ML systems with disciplined training, evaluation, deployment, and safety practices
Design APIs that are stable, ergonomic, and evolvable
Design systems at the right scale with explicit trade-off documentation
Design services that are reliable, observable, secure, and maintainable
| name | git-workflow-and-versioning |
| description | Branching strategy, commit discipline, PR hygiene, and semantic versioning |
| difficulty | junior |
| domains | ["general"] |
Git history is documentation. A clear commit history enables fast debugging, safe reverts, and meaningful changelogs. This skill enforces the habits that make git useful as a tool rather than just a backup system.
Use: <type>/<description> — e.g., feat/user-search, fix/login-redirect, chore/update-deps
Types: feat, fix, docs, chore, refactor, perf, test
Follow Conventional Commits:
<type>(<scope>): <description>
[optional body]
[optional footer]
Examples:
feat(auth): add OAuth2 login with Googlefix(api): handle null user_id in /profile endpointperf(db): add index on users.email columnRules:
Closes #123A PR should be reviewable in under 30 minutes. If it takes longer, it's too big. Split it.
Every PR must have:
MAJOR.MINOR.PATCH
Tag releases: git tag v1.2.3 -m "Release 1.2.3"
gitleaks, detect-secrets)