Desenvolvimento

Trigger on "lock phasing", "stage gates", "consult gates", "phase outcomes", "primary question per phase", "entry exit criteria", "gate table". Defines staged outcomes with one primary question per phase plus entry/exit. NOT acceptance metrics (use consult-acceptance), NOT personal save cascade (timeln-plan is parallel -- use its output as optional input only).

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use this skill at the end of a content creation session to review deliverables, collect feedback, detect recurring correction patterns, and create a git commit. Invoke when the user says "wrap up", "end session", "session wrap", "wrap session", "commit session work", or "close out this session".

Prepare commits for the current feature branch, push, and create or update a PR to main.

Depura erros e rastreia falhas em agentes de IA e suas ferramentas. Identifica erros de contexto, loops infinitos, chamadas de ferramenta malformadas, problemas de análise de resposta e conflitos entre subagentes.

List your GitHub-owned local clones under PROJECTS_ROOT that have pending work (uncommitted changes, unpushed commits, or inbound remote commits), with branch, counts, age of oldest pending work, and a per-repo summary. Each run fetches every repo's origin in parallel so the counts reflect the current remote. TRIGGER when: user asks "/github-status", wants a cross-project overview of their repos,

実装・commit 後、`acceptance-check` 通過後・PR 作成前に別の AI (Codex CLI または Claude CLI headless) に diff を渡してセカンドオピニオンのコードレビューを得る。backend は環境変数 `CROSS_REVIEW_BACKEND` で `codex` / `claude-self` から選択でき、未指定時は利用可能な CLI を自動検出する。

Use this skill whenever working on a bug fix — from triage through implementation through verification. Triggers on: "fix this bug", "there's an error", "something is broken", "debug this", "this isn't working", "root cause", "why is this failing", "production issue", "investigate this", "hotfix needed", "patch this". This skill applies systematic root cause analysis before touching code, ensures

Use when the user wants to prevent broken code from being pushed, block git push when tests fail, run tests before push, set up push protection, or add a safety net against pushing untested code. Covers any request to gate pushes on test results — whether they mention "hook", "pre-push", or just describe wanting to stop bad code from reaching the remote. Also handles auto-fix/auto-repair of test f

Revisar o branch atual em busca de bugs, adequação à intenção e cobertura de testes; executar ou escrever testes; fazer commits focados; abrir ou atualizar um PR.

[PM Twin] Define, track, and review product KPIs — success metrics, funnels, health indicators.

Use when Claude Code needs to get oriented in a SpecDD project before later work, while making no edits.