Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Run a project's quality gates, get user review, then commit — the end-of-task counterpart to new-task. Tech-stack agnostic — discovers the project's own test, typecheck, lint, static-analysis, and format commands rather than hardcoding them. Use when a coding task is implemented and ready to commit, when the user says "finish this", "wrap up", "ready to commit", "ship it", or before any commit that concludes a task.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-10 | ✗→✓ | ▲ Improved | 137% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -14% | 0% |
| case-13 | ✗→✓ | ▲ Improved | 22% | 0% |
| case-17 | ✗→✓ | ▲ Improved | -18% | 0% |
| case-20 | ✗→✓ | ▲ Improved | 23% | 0% |
End-of-task lifecycle: gates → review → commit. Counterpart to new-task (which starts the branch). Commit/PR naming is owned by git-conventions.
This skill owns the gate sequence and policy, never the commands — those are stack-specific and get discovered from the project.
Run in this order; stop on first red and enter the fix-loop:
Then: show the user the diff + gate results → ask for review → commit only on explicit approval.
Do not assume tools. Detect the project's own commands, in priority order:
composer.json scripts (e.g. test, lint, analyse).package.json scripts.Makefile / justfile targets.bin/ or scripts/ entrypoints..github/workflows/*, .gitlab-ci.yml) — mirror what CI runs.Map each gate to the discovered command; skip a gate with no command (state which were skipped). Example resolutions (illustrative, not hardcoded): Laravel → pest/phpunit, phpstan/larastan, pint/rector. JS/TS → vitest/jest, tsc --noEmit, eslint, prettier.
> Laravel-specific gate commands live in laravel-rules; this skill > resolves "run the static-analysis command" → that project's tool.
Gate red → read failure → fix → re-run that gate. Cap at ~3 iterations per gate; if still red, stop and escalate to the user with the exact error. Never disable/skip a check to make it pass. Never --no-verify.
git-conventions (type vocab, subject grammar, footers).commit concludes the task; treat it as a confirmation gate.
--no-verify), never weaken a check to pass.git-conventions.Other measured skills in the registry, with their headline benchmark lift.