Menú
Make sure your code is ready to commit, then stage changes into clean, atomic commit. Use before committing.
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.
Break a feature spec into intentional waves and bite-sized tasks grouped by dependency. Use after a spec is written to prepare for easy-to-track implementation.
Review a code change (diff or PR) for ship-readiness before merge. Use when reviewing your own or someone else's changes prior to committing/merging/etc.
Full review of a plan or spec to be sure there are no surprises, gaps, or mistakes. Use to harden a spec before implementation.
Create a well-thought-out plan covering problem statement, goals, technical approach, and verification criteria. Use while planning / before implementing any non-trivial feature.
Audit a test suite to find tests that give false confidence — tests that encode bugs, duplicate coverage, or are so heavily mocked they can't catch real regressions. Use to improve robustness, audit coverage, or harden a risky area.
Basado en la clasificación ocupacional SOC
| name | gjalla-prepare-and-commit |
| description | Make sure your code is ready to commit, then stage changes into clean, atomic commit. Use before committing. |
Turn a working change into a committable change that reviewers and future readers can trust.
git add -p).gjalla attest --example will show you the format, make sure to view the full output (do not run the command and pipe it 2>/dev/null for example)