Menu
Produce a read-only repository health briefing covering stack, git state, setup, tests, dependencies, blockers, and next steps.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Full-lifecycle orchestration for comprehensive, no-compromise execution — roll-calls the right skills, fans out parallel/worktree agents, then closes the loop (verify, review, simplify, changelog, handoff, retro). Use when you want maximum effort, to go all-in, or to orchestrate a big task end-to-end.
Runs a short retrospective that PROPOSES edits to the user's Claude Code skills — capturing a newly-found gotcha, fixing a description that didn't auto-trigger, retiring a dead skill, or extracting a reusable pattern into a new skill. Improves the TOOLSET, not the session log. Use when the user signals satisfaction at the end of real work ("thanks", "thanks that worked", "that worked great", "nice", "perfect", "exactly what I needed"), or when they explicitly run /session-retro. Always proposes and waits for confirmation — never edits skills silently. In unattended runs (/orchestrate, overnight, or /session-retro --auto), writes proposals to ~/.claude/retro-proposals/ instead of blocking.
Generate a concise session handoff for resuming work later, including current state, decisions, open issues, and next steps.
Deep task decomposition into parallel workstreams with self-contained agent prompts. Use when you want to review the execution plan before committing to it.
Generate a handoff note for clean session transitions — preserves context across /clear or new sessions. Use when ending a session, when context is getting high, or when the user says "hand off", "wrap up the session", or "save state for next time".
Inspect and clean stale branches across multiple repositories using the dotfiles git-hygiene + gh-bootstrap toolchain. Use when the user asks about branch state, stale local branches, or "no ref was fetched" errors.
| name | repo-health |
| description | Produce a read-only repository health briefing covering stack, git state, setup, tests, dependencies, blockers, and next steps. |
Use for quick orientation or a read-only health check of a repository.
README.md, project guidance files, and manifests such as
package.json, pyproject.toml, go.mod, or Cargo.tomlgit status --shortgit log --oneline -10Keep it short:
## Repo Health
**Stack:** ...
**State:** ...
**Commands:** ...
**Verification:** ...
**Dependency Notes:** ...
**Blockers:** ...
**Next Steps:** ...
This is read-only by default. Do not edit files unless the user separately asks for fixes.