publish-pr
Skill0 starsChanged 41 days agoMITView on GitHub
Create and publish a GitHub pull request as a draft, with a ticket-key title and a New/Old Behavior description. Use whenever creating, opening, publishing or pushing a PR, even if the user just says 'make a PR'.
- Commits and pushes
6 other projects use a version of this.
Adopted by
Most recently taken up by
- LeonardiFranco/skillstheir own version, first seen Nov 8, 2026
- tariknz/irdashiestheir own version, first seen Oct 17, 2026
- grove/promise-to-prooftheir own version, first seen Oct 12, 2026
- darknightdesigner/skillstheir own version, first seen Oct 2, 2026
- OpenPerfAgent/who-ate-my-flopstheir own version, first seen Sep 30, 2026
- ethanaubuchon/dossier-tradecrafttheir own version, first seen Sep 26, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- tariknz/irdashies★ 270same name
- OpenPerfAgent/who-ate-my-flops★ 35same name
- darknightdesigner/skills★ 4same name
- grove/promise-to-proof★ 4same name
- ethanaubuchon/dossier-tradecraft★ 3same name
- LeonardiFranco/skills★ 1same name
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 repository8 other files it gives its agents.
- grill-meSkill
- multiphase-pr-review-asyncSkill
- multiphase-pr-reviewSkill
- pr-splitSkill
- ship-reviewSkill
- take-feedbackSkill
- thermo-nuclear-code-quality-reviewSkill
- ticketedSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 10 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
10
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
- Distinctive: line 8
Use this skill for every pull request you create.
- Very specific: line 12
Every PR title starts with a ticket key such as NOVA-9999.
- Distinctive: line 16
If neither has one, ask the user.
- Very specific: line 22
Read the diff against the base branch (git diff <base>...HEAD) and the commit messages.
- Distinctive: line 34
Keep the summary short and focused on the effect.
- Distinctive: line 38
Use exactly this template, with these two sections and nothing else:
- Distinctive: line 50
Write a few sentences or short bullets for each section, in plain language a reviewer can follow without opening the code.
- Distinctive: line 51
Don't list changed files, classes or methods, and don't explain why each file changed.
- Distinctive: line 52
Don't add other sections like Summary, Changes, Testing or Checklist.
- Distinctive: line 53
If a change has no behavior change (a pure refactor, for example), say so plainly in New Behavior, e.g.
- Distinctive: line 69
Always create the PR as a draft so the author can check it before reviewers are notified:
- Distinctive: line 78
When it's done, give the user the PR link and the title in one short line.
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
Publish PR
Use this skill for every pull request you create. Reviewers read the PR to understand what changes for the system and its users, so the title and description are about behavior, not about code.
1. Find the ticket key
Every PR title starts with a ticket key such as NOVA-9999. Look for it in this order:
- The current branch name (
git branch --show-current), e.g.feature/NOVA-1234-fix-logingivesNOVA-1234. - The commit messages on the branch (
git log <base>..HEAD --format=%s%n%b). - If neither has one, ask the user. Don't invent a key.
A ticket key looks like [A-Z][A-Z0-9]+-\d+. Write it in upper case.
2. Understand the change
Read the diff against the base branch (git diff <base>...HEAD) and the commit messages. Work out:
- What the system does after this change is merged.
- What it does today: what is wrong, missing or not working.
Think about behavior someone would notice: API responses, messages sent or handled, data written, UI, errors, performance. Leave file names, classes and refactoring steps out. That information is already in the diff.
3. Write the title
Format: <TICKET-KEY>: <short summary>
- Example:
NOVA-9999: Retry failed message deliveries to SignedIn - Keep the summary short and focused on the effect. Use imperative mood and no trailing period.
4. Write the description
Use exactly this template, with these two sections and nothing else:
## New Behavior
<The effect of the change: the new state after the code has been merged.>
## Old Behavior
<The current behavior: what is wrong or not working today.>Guidelines:
- Write a few sentences or short bullets for each section, in plain language a reviewer can follow without opening the code.
- Don't list changed files, classes or methods, and don't explain why each file changed.
- Don't add other sections like Summary, Changes, Testing or Checklist.
- If a change has no behavior change (a pure refactor, for example), say so plainly in New Behavior, e.g. "No functional change; X is now handled by Y, which makes Z easier." In Old Behavior, describe the current state.
Example
Title: NOVA-4821: Skip inactive employees when syncing to Nova
## New Behavior
The nightly sync only sends active employees to Nova. Inactive employees are skipped and logged at info level, so the sync finishes without errors.
## Old Behavior
The sync sent every employee, including inactive ones. Nova rejects inactive employees, so each sync run ended with a batch of failed messages in the error queue.5. Create the PR as a draft
Always create the PR as a draft so the author can check it before reviewers are notified:
git push -u origin HEAD
gh pr create --draft --title "<title>" --body-file <file>Write the body to a temporary file and pass it with --body-file so the markdown survives shell quoting. If a PR already exists for the branch, update its title and body with gh pr edit instead of creating a new one, and leave its draft/ready state as it is.
When it's done, give the user the PR link and the title in one short line.
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.

