overlapping-prs
Skill2 starsChanged 10 days agoNo licenceView on GitHub
Plan how a set of pull requests that overlap — same files, same schema migration chain, same shared code — are cut, ordered and merged so that they stop colliding with each other: shared foundation first, a merge order fixed up front with a stack that follows it, and schema migrations kept as the last commit of each PR and regenerated at merge time instead of renumbered. Use whenever several pieces of work touch the same area, whatever groups them (a feature, a batch of bug fixes, a refactor, review follow-ups), before splitting them into PRs; or when open PRs keep falling into conflict after each merge, when every merge forces a migration renumbering on the others, or when two PRs created the same helper twice.
- Commits and pushes
In this repository14 other files it gives its agents.
- dailysumSkill
- demo-prSkill
- demo-recSkill
- jira-readSkill
- notify-pr-slackSkill
- pr-watchSkill
- review-diffSkill
- review-prSkill
- review-retroSkill
- sprint-checkSkill
- ticket-to-prSkill
- visual-planSkill
- wtm-setupSkill
- wtmSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.