agentleFS
diriendirien/yet-another-agent-harness/.claude/skills/pr/SKILL.md

pr

Skill19 starsChanged 8 months agoMITView on GitHub

Create pull requests with structured description

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user runs /pr or asks to create a pull request.

    line 9
  2. Distinctive:

    Run git log --oneline main..HEAD to understand all commits

    line 13
  3. Distinctive:

    Run git diff main...HEAD to see the full diff

    line 14
  4. Very specific:

    Check if the branch is pushed: git rev-parse --abbrev-ref --symbolic-full-name @{u}

    line 15
  5. Distinctive:

    If not pushed, push with git push -u origin HEAD

    line 16
  6. Very specific:

    Create the PR using gh pr create with:

    line 17
  7. Distinctive:

    Keep the title concise — details go in the body

    line 30

≈ “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

/pr — Pull Request Creation

When to use

When the user runs /pr or asks to create a pull request.

Steps

  1. Run git log --oneline main..HEAD to understand all commits
  2. Run git diff main...HEAD to see the full diff
  3. Check if the branch is pushed: git rev-parse --abbrev-ref --symbolic-full-name @{u}
  4. If not pushed, push with git push -u origin HEAD
  5. Create the PR using gh pr create with:
    • Title: short, under 70 chars
    • Body using the template:

      Summary

      <1-3 bullet points>

      Test plan

      • Tests pass
      • Manual verification

Rules

  • NEVER force push
  • Analyze ALL commits, not just the latest
  • Keep the title concise — details go in the body
  • Return the PR URL to the user when done

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.