agentleFS
usk6666usk6666/yorishiro-proxy/.claude/skills/pr/SKILL.md

pr

Skill19 starsChanged 23 days agoApache-2.0View on GitHub

Create a PR. Verify build and test pass, then run gh pr create

  • Deletes or force-pushes
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Build verification: Run make build and confirm no errors

    line 12
  2. Very specific:

    Run tests: Run make test and confirm all tests pass

    line 13
  3. Distinctive:

    Review diff: Check changes with git diff main...HEAD

    line 14
  4. Very specific:

    Generate PR title: Create a title in Conventional Commits format (feat(scope): description)

    line 15
  5. Very specific:

    Create PR: Run gh pr create --title "<title>" --body "<body>"

    line 17
  6. Distinctive:

    If build or tests fail, do not create the PR and report the problem instead

    line 34
  7. Distinctive:

    Default base branch is main

    line 35
  8. Very specific:

    Do not use --delete-branch on the upstream PR if the downstream has not been retargeted — you lose the PR thread (closed PRs are still …

    line 58

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

A skill for creating Pull Requests.

Steps

  1. Build verification: Run make build and confirm no errors
  2. Run tests: Run make test and confirm all tests pass
  3. Review diff: Check changes with git diff main...HEAD
  4. Generate PR title: Create a title in Conventional Commits format (feat(scope): description)
  5. Generate PR body: Generate body including a summary of changes and test plan
  6. Create PR: Run gh pr create --title "<title>" --body "<body>"
  7. Display result: Show the PR URL

PR Body Template

## Summary
- <bulleted list of changes>

## Test plan
- [ ] Test items

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Notes

  • If build or tests fail, do not create the PR and report the problem instead
  • Default base branch is main

Stacked PRs

When PR B is stacked on PR A's branch (B.base == A.head_branch) and you merge PR A with gh pr merge --delete-branch, GitHub auto-closes PR B because its base branch no longer exists. Auto-closed PRs cannot be reopened (gh pr reopen returns "Could not open the pull request") nor have their base changed (gh pr edit --base returns "Cannot change the base branch of a closed pull request").

Two safe sequences:

  1. Retarget before merging upstream (preferred when you have time):
    gh pr edit <B>  --base <A's base>     # B will temporarily show A's diff too — fine if A merges first
    gh pr merge <A> --squash --admin --delete-branch
  2. Recreate downstream after merging upstream:
    gh pr merge <A> --squash --admin --delete-branch     # closes B
    # in a worktree on B's branch:
    git rebase --onto origin/<base> <A's-original-head-commit>     # drops A's commits, replays only B's
    git push --force-with-lease
    gh pr create --base <base> --head <B's-branch>

Do not use --delete-branch on the upstream PR if the downstream has not been retargeted — you lose the PR thread (closed PRs are still readable but lose OPEN semantics for review-gate and merge-queue tooling).

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.