agentleFS
Sign inStart free
Beskars-CodeBeskars-Code/Skills/skills/babysit-pr/SKILL.md

babysit-pr

Skill0 starsChanged 5 days agoMITView on GitHub

Use when the user asks to babysit, watch, or monitor a PR until its checks or reviews change, or to report when it is ready. Watches and reports only; fixes and other changes need their own permission.

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use leaving-pr-comments, sol-loop and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • scottwaterSkill

    leaving-pr-comments

    Format comments an agent posts on GitHub on the user's behalf. Use whenever leaving a PR comment, review comment, or reply.

    Also in 9 projects that use this

  • scottwaterSkill

    sol-loop

    Review a change with GPT Sol in a loop until both agents agree. Use when the user says sol loop, or when another skill asks for a Sol review.

    Also in 7 projects that use this

  • Nexus-Organization-InfosecSkill

    full-stop

    Shut down the Full Control phone-bridge completely — end Claude's watch loop, stop the bridge server (server.py started via ensure_server.ps1), and mark Claude offline in the app. Use whenever the user invokes /full-stop or says "stop full control", "stop the watch loop", "shut down the bridge/server", or "stop the ps1". Counterpart of [[full-control]], which starts everything.

    Also in 9 projects that use this

  • assisjpSkill

    file-pr

    Prepare and open or update an authorized pull request with a concise problem-first description and verifiable evidence. Use when the user asks to create, file, open, or update a PR. Do not use merely to review a diff or when publication is not authorized.

    Also in 13 projects that use this

  • shhacSkill

    full-send

    Complete an explicitly assigned task autonomously through parallel agents, peer-reviewed decisions, and automatic retries of temporary blockers. Use only when the user explicitly invokes Full Send.

    Also in 8 projects that use this

  • assisjpSkill

    takeover

    Take over an existing branch, pull request, worktree, or agent handoff while preserving the original goal, contributor credit, and concurrent work. Use when the user asks to take over, finish, rescue, or continue someone else's implementation. Do not use to replace a clear request to start new work.

    Also in 4 projects that use this

  • +1 more from scottwater

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every run applies code quality, code structure, and Plain language.

    line 9
  2. Distinctive:

    Before a decision, use Asking the user.

    line 12
  3. Distinctive:

    Keep ownership and evidence in the existing execution context.

    line 13
  4. Distinctive:

    If still waiting, let only the owner watch.

    line 24
  5. Distinctive:

    When nested, return to the existing parent.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Babysit a PR

Every run applies code quality, code structure, and Plain language. Before a decision, use Asking the user. Keep ownership and evidence in the existing execution context.

  1. Identify repository, PR and parent/owner. Read PR lifecycle, tool discovery, and execution evidence.
  2. Establish authority and inspect existing findings before registering a watch under watch lifecycle.
  3. Resolve authorized actionable work through the current orchestrator's remediation.
  4. If still waiting, let only the owner watch. On each wake reconcile state and apply latest-head readiness.
  5. Cleanly unwatch before questions, handoff or completion. Report head, actual checks/reviews, blockers, readiness and cleanup state. Default stop unmerged.

When nested, return to the existing parent; do not create another watcher, review dispatcher, or shipping lifecycle.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free