tzachbon/srulik-toolkit / plugins/srulik-toolkit/skills/pr-babysit
pr-babysit
VerifiedBabysit a pull request within the original conversation, using a low-cost subagent for bounded read-only triage while the parent owns monitoring, fixes, and authorized merging. Use when asked to babysit or monitor a PR through CI and review, including new feedback after checks pass.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.2 KB |
| references/comments.md | markdown | 1.2 KB |
| references/github.md | markdown | 1.1 KB |
| references/oh-my-pi.md | markdown | 1.7 KB |
| references/t3-code.md | markdown | 5.2 KB |
references/comments.md
View on GitHub# Comments posted for the user
Apply these rules to every comment an agent posts for the user on a pull request or issue: top-level comments, inline review comments, replies to bots or reviewers, review bodies, and the written reason before resolving or dismissing feedback. Skip them for PR descriptions, commit messages, and text the user asked to post verbatim.
Start the comment with this callout:
```md
> [!NOTE]
> 🤖 **<model> responding on behalf of <user>**
The reply starts here.
```
- Use the public model name the harness reports. If it reports none, use the harness name. Do not guess.
- Use the user's name or provider login.
- Keep the attribution inside the callout and the reply outside it. Add no heading, rule, signature, or second attribution.
Write the reply directly: lead with the conclusion, cite the code, check, or reproduction, and separate verified facts from judgment. No canned thanks or status narration.
Before posting, check the whole comment, including quotes and attachments, for secrets and private details, and preview the Markdown. After posting, confirm the provider returned the comment or review URL. Resolve a thread only after its reply posted.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |