Best use case
babysitter:issue is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Start a babysitter workflow from a GitHub issue.
Teams using babysitter:issue should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/issue/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How babysitter:issue Compares
| Feature / Agent | babysitter:issue | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Start a babysitter workflow from a GitHub issue.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# babysitter:issue Run issue-driven orchestration. ## Behavior 1. Parse issue input: - Numeric issue id, or full GitHub issue URL. - Optional `--repo owner/name`. 2. Resolve repository: - If `--repo` omitted, infer from current git remote. 3. Fetch issue details: - Use `.codex/github-workflow.js` helper. 4. Generate: - Concise implementation plan. - Proposed steps and risk notes. 5. Optional actions: - `--apply` -> return `mode=apply` and ready-to-run babysitter prompt. - `--pr <number>` -> post plan comment to existing PR. - `--open-pr` -> attempt `gh pr create --fill`. 6. If in apply mode: - Start babysitter run with issue context in prompt. ## Output Contract - Return JSON with: - `issue`: metadata - `plan`: list of actionable steps - `mode`: `plan` or `apply` - `nextAction`: command suggestion
Related Skills
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
issue
Run an issue-centric Babysitter workflow.
issue-tracker
Track and manage project issues with escalation and resolution workflows
issue-tree-generator
Generate and validate issue trees for structured problem solving with MECE validation
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
babysitter:project-install
Set up a project for babysitting. Research the codebase, build project profile, install tools.
babysitter:doctor
Diagnose babysitter run health — journal integrity, state cache, effects, locks, sessions, logs, and disk usage.
babysitter:model
Set or view model routing policy for plan/execute/review phases.
babysitter:plan
Plan a babysitter workflow without executing it. Focus on creating the best process possible.
babysitter:assimilate
Assimilate an external methodology, harness, or specification into babysitter process definitions.
babysitter:help
Help and documentation for babysitter commands, processes, skills, agents, and methodologies.
babysitter:call
Start a babysitter orchestration run. Use this command to start babysitting a complex workflow.