agentleFS
Mr-QuinMr-Quin/danmaku-anywhere/.claude/skills/babysit-pr/SKILL.md

babysit-pr

Skill551 starsChanged 5 days agoLicence not identifiedView on GitHub

Use to monitor an open PR for AI/bot review comments, evaluate them critically, push fixes for real issues, and resolve threads — capped at a sensible duration so it self-terminates. Invoke as "babysit PR #N" or after opening a PR.

65 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 10 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.
  • cogine-aiSkill

    leaving-pr-comments

    Use whenever leaving comments on GitHub.

    Also in 12 projects that use this

  • tekumaraSkill

    sol-loop

    Use when the user says "sol loop".

    Also in 10 projects that use this

  • tunnckoCoreSkill

    full-stop

    Trigger this if the user says 'full stop', even as a closing "Full stop." that reads like emphasis.

    Also in 13 projects that use this

  • cogine-aiSkill

    modernize

    For getting old prs up to date. Use when asked to rebase a pr or "modernize".

    Also in 10 projects that use this

  • tekumaraSkill

    file-pr

    Raise a concise pull request. Use when the user asks to raise, open, or create a PR.

    Also in 17 projects that use this

  • Solly922Skill

    html-communication

    Create self-contained HTML artifacts for plans, architecture maps, comparisons, reports, timelines, diagrams, and technical explainers when visual structure improves understanding. Use for complex or spatial information; do not use for short, linear answers that are clearer in Markdown.

    Also in 3 projects that use this

  • +1 more from tekumara
  • +1 more from cogine-ai

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 63 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 63 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.

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.