agentleFS
Sign inStart free
ku5icku5ic/claude-kit/skills/pr/SKILL.md

pr

Skill2 starsChanged 8 days agoMITView on GitHub

Draft what lands in a PR thread (your PR's title and body, a review of someone else's PR, replies to the review on yours), then post an approved draft

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the kind's reference file and follow it as the procedure.

    line 28
  2. Very specific:

    Every kind follows rules/output.md section 4 (External communication).

    line 30
  3. Very specific:

    Only publish posts. The drafting kinds write a file and post nothing.

    line 31
  4. Very specific:

    Every draft starts with this header.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Dispatch

The first word of the arguments is the kind; everything after it is the kind's arguments.

KindUse whenProcedure
descriptiondrafting your PR's title and bodyreference/description.md
reviewyou reviewed someone else's PRreference/review.md
replyanswering the review on your PRreference/reply.md
publishposting an approved draft to GitHubreference/publish.md
  1. Missing or unknown kind: ask via AskUserQuestion with the four kinds above as options.
  2. Read the kind's reference file and follow it as the procedure.
  3. In the reference, the ARGUMENTS token (written with a leading dollar sign) means everything after the kind word in the Arguments line below, and a backticked command prefixed with an exclamation mark means run that command via Bash and use its output.
  4. Every kind follows rules/output.md section 4 (External communication). On tone and shape it wins over the reference file; the sections a reference file defines, such as the PR template handling, stay.
  5. Only publish posts. The drafting kinds write a file and post nothing.

Draft header

Every draft starts with this header; publish parses it.

# PR <n or branch> <kind> draft (not posted)

Kind: <description|review|reply>
PR: <owner>/<repo>#<n>
Head: <full head SHA the draft was written against>

A description for a branch with no PR yet writes Branch: <name> in place of the PR: line.

Arguments: $ARGUMENTS

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