agentleFS
opsmillopsmill/infrahub/.agents/skills/what-is-this-pr/SKILL.md

what-is-this-pr

Skill551 starsChanged 8 days agoApache-2.0View on GitHub

Explains simply the purpose of a pull request. TRIGGER when: the user shares a pull request URL or number and asks what it is for, what it does or why it exists. DO NOT TRIGGER when: the user wants bugs found → reviewing-pull-requests.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read both the description (gh pr view) and the code (gh pr diff).

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

What is this pull request

Explain simply the purpose of the pull request $ARGUMENTS:

  1. Current state
  2. The problem
  3. The proposed solution

Explain it from the side of the person who uses the feature, not the implementation: leave out hook names, query shapes, file paths and test lists. Keep it short.

Read both the description (gh pr view) and the code (gh pr diff); do not check out the branch. Descriptions often say more or less than the code does, so explain what the code does, and point out where the description disagrees with it.

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.