babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/babysit-babysitter-issues && cp -r /tmp/babysit-babysitter-issues/.claude/skills/babysit-babysitter-issues ~/.claude/skills/babysit-babysitter-issuesSKILL.md
# Babysit Babysitter Issues Fetch open GitHub issues from https://github.com/a5c-ai/babysitter/issues assigned to `a5c-agent`, then orchestrate work on each issue via `/babysitter:call`. ## Workflow ### Step 1: Fetch Assigned Issues Use the `gh` CLI to list open issues assigned to `a5c-agent`: ```bash gh issue list --repo a5c-ai/babysitter --assignee a5c-agent --state open --json number,title,url,labels --limit 50 ``` If no issues are found, report that there are no open issues assigned to `a5c-agent` and stop. ### Step 2: Present Issues Display the list of open issues to the user with their number, title, labels, and URL. ### Step 3: Orchestrate via Babysitter For each issue, invoke the `babysitter:yolo` skill with a prompt that includes the issue URL and context: ``` /babysitter:yolo work on this GitHub issue: <issue_url> ``` If multiple issues are selected, process them sequentially -- complete one before starting the next. Present a summary after each issue is processed. as part of the process, create a new branch from staging named `issue-<number>` and push commits to that branch. then create a pull request against staging with a meaningful name and a description of the work done (with link to the original issue). if the issue has a "bug" label, prioritize fixing the bug and include details about the bug and how it was fixed in the pull request description. ### Step 4: Summary After all open a5c-assigned issues have been processed, provide a summary of what was done for each issue. ## Notes - Only issues assigned to `a5c-agent` are fetched. Other assignees are ignored. - The `gh` CLI must be authenticated. If authentication fails, prompt the user to run `gh auth login`. - Each issue is handed off to `/babysitter:yolo` which handles the actual implementation work. - the entire workflow should be without any user interaction or breakpoints in the run, allowing for a seamless babysitting experience. do not let the user select which issues to work on -- just process all open a5c-assigned issues sequentially.
Coordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
>-
Discover public GitHub repositories that import defineTask from @a5c-ai/babysitter-sdk and maintain a deduplicated catalog of those repositories in docs/repo-with-babysitter-processes.md. Excludes any repo named "babysitter" (to filter out forks of this monorepo). Invoke when asked to find, discover, catalog, or refresh "repos using babysitter", "babysitter in the wild", or "who else is using babysitter".