agentleFS
ddnexusddnexus/pagy/.claude/skills/merge-pr/SKILL.md

merge-pr

Skill5k starsChanged 9 days agoMITView on GitHub

Merge one or more pagy pull requests the way the maintainer wants (base branch, squash subject with the 💎 prefix, empty body, local branches updated). Use when asked to merge, land or handle a PR.

  • Deletes or force-pushes
  • Commits and pushes

18 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about ddnexus/pagy

The biggest 5 of 55 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 55

Talked about on GitHub, Hacker News and Bluesky (55 times).

On GitHub · 50

45 more on GitHub

On Hacker News · 3

Used with

Projects with it also use implement-issue, create-pr and 2 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.
  • GoogleSkill

    implement-issue

    Implement a Site Kit GitHub issue end-to-end from its implementation brief. Use when the user asks to implement, build, or work on a GitHub issue / feature by number (e.g. "implement issue #12345", "build the feature in issue 12345", "follow the implementation brief for #12345") in the google/site-kit-wp repo.

    Also in 3 projects that use this

  • SentrySkill

    create-pr

    Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

    Also in 7 projects that use this

  • sahinSkill

    create-issue

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

  • Other versions18 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 18

    1. ShareX/ShareX★ 41ksame name
    2. cube-js/cube★ 21ksame name
    3. mihai-dinculescu/tapo★ 877same name
    4. bazel-contrib/rules_python★ 695same name
    5. kkokosa/dotLLM★ 528same name
    6. r3bl-org/r3bl-open-core★ 486same name
    7. tbhb/vale-ai-tells★ 118same name
    8. TermiX-official/cryptoclaw★ 100same name
    9. kdy1/kdy1-scripts★ 34same name
    10. neul-labs/openclawMU★ 33same name

    8 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Always squash-merge. The subject is the PR title followed by (#N), which is what GitHub proposes.

    line 40
  2. Very specific:

    After a merge on master, dev must follow: fast-forward local dev on the new master and push it.

    line 65

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Merging a pull request

This is the procedure for merging a PR in pagy. Run it only when asked to merge: checking a PR never implies merging it. When several PRs are open, process them from the oldest to the newest.

Where a PR lands

A PR from a GitHub bot (dependabot, workflow bumps) stays on master and is merged there.

A PR from a user lands on dev, never on master: change its base first.

gh pr edit N --base dev

master may receive directly only what keeps the code identical to the published gem: docs fixes, workflows, scripts, tests and other chores. Any change under gem/ goes on dev.

Before merging

The PR must be rebased on the tip of its base branch and its checks must be green. For a bot PR that is behind, comment @dependabot rebase. For a user PR that is behind, rebase locally and push to the fork; --force-with-lease to a bare URL fails, so add the fork as a remote first or use plain --force.

git fetch origin pull/N/head:pr-N
git rebase dev pr-N
git remote add <user> https://github.com/<user>/pagy.git && git fetch <user>
git push --force-with-lease <user> pr-N:<branch>

The squash commit

Always squash-merge. The subject is the PR title followed by (#N), which is what GitHub proposes. When the PR touches any file under gem/, prepend 💎 to the subject: the release script builds the CHANGELOG from the 💎 commits and warns about unmarked gem commits. Add (Fix #issue) when the PR closes an issue. The body is always empty.

gh pr merge N --squash --subject "💎 <PR title> (#N)" --body ""

Since the body is empty, GitHub does not close the issue linked in the PR body: check it and close it by hand.

gh issue close N --comment "Fixed by #PR, merged on dev; it will be in the next release."

After merging

Fast-forward the local branch that received the merge and delete the temporary branch.

git pull --ff-only origin dev        # or master for a bot PR
git branch -D pr-N

After a merge on master, dev must follow: fast-forward local dev on the new master and push it. If dev has its own commits, rebase them on master and push with --force-with-lease. origin/dev is never left behind master.

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.