Retrospect External Babysitter Run
For a repository in the babysitter-users catalog, locate its babysitter processes and...
Install
npx skills add a5c-ai/babysitter --skill retrospect-external-babysitter-run -g -a claude-code -y- Repository
- a5c-ai/babysitter1.9k
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,086 tokens
- Runs scripts
- No, instructions only
What it does
For a repository in the babysitter-users catalog, locate its babysitter processes and any committed runs (.a5c/runs/<runId>/) and perform a retrospective on a chosen run -- what went well, what failed, process suggestions, quality of effect design, breakpoint patterns -- mirroring the /babysitter:retrospect workflow but applied to an external repo. Invoke when asked to "retrospect on repo X's run", "analyze how someone else used babysitter", or "review an external babysitter run".
Retrospect External Babysitter Run
Analyse a babysitter run that lives in an external public repository, using the same lens as the in-repo /babysitter:retrospect command. Produce a written retrospective with concrete suggestions for the process author (or, if the insight generalizes, for the babysitter project itself).
When to use
- User names an external repo and asks for a retrospective.
- User asks "find a babysitter run to retrospect on" (combine with the
catalog-babysitter-usersskill to pick one). - User asks "how are other people using babysitter processes? What do they get wrong?".
Prerequisites
ghCLI authenticated.docs/repo-with-babysitter-processes.mdexists (if not, run thecatalog-babysitter-usersskill first).- A workspace directory where external repos can be shallow-cloned (default:
/tmp/babysitter-retrospect/or.a5c/tmp/external-runs/).
Phase 1 -- Target selection
- Read
docs/repo-with-babysitter-processes.mdand list Active repos with stars + description. If the user already named a repo, skip to step 3. - Ask the user which repo to retrospect on (use AskUserQuestion in interactive mode; if non-interactive, pick the highest-starred Active repo that wasn't retrospected in the last 30 days -- track via
docs/retrospectives/<owner>-<name>/log.md). - Confirm the target with the user before cloning.
Phase 2 -- Discover processes and runs
Shallow clone the target:
mkdir -p .a5c/tmp/external-runs
cd .a5c/tmp/external-runs
gh repo clone <owner>/<name> -- --depth 50 --single-branch
cd <name>
Locate:
