Menú
Clean atomic commits, honest messages, and a safe branch/PR workflow
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.
Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags
Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done
Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable
Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed
Author or connect a Model Context Protocol server so an agent gains new tools
Build automated pipelines that gate merges and ship reliably
Basado en la clasificación ocupacional SOC
| name | using-git |
| description | Clean atomic commits, honest messages, and a safe branch/PR workflow |
| version | 1 |
| trust | built-in |
Treat git history as a record someone will read later. Commit and push only when the user asks; if you're on the default branch, branch first.
Committing
git status, git diff --staged). Stage
only related changes — one logical change per commit. Don't git add -A blindly.Branches & PRs 4. Don't commit straight to the default branch — create a focused branch. 5. Open a PR with a clear title and a body covering: what changed, why, how it was tested. Confirm with the user before pushing or opening it (it's outward-facing).
Safety 6. Never force-push a shared branch, hard-reset away uncommitted work, or rewrite published history without explicit confirmation. Prefer revert over reset for anything already pushed.