publish-pr
Skill272 starsChanged 16 days agoMITView on GitHub
Publish GitHub pull requests for this repository. Use this skill whenever the user asks to create, open, raise, or publish a PR. Follow the repository's pull request template exactly, default to a published/ready-for-review PR unless the user explicitly requests a draft, and write a conventional-commit-style title that describes the user-visible problem solved or outcome achieved. Continue with babysit-pr when monitoring or review-comment handling is requested.
- Commits and pushes
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Davidengstrom01/claude-skillstheir own version, first seen Nov 16, 2026
- LeonardiFranco/skillstheir own version, first seen Nov 8, 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
- 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
- Davidengstrom01/claude-skills★ 0same 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- babysit-prSkill
- publish-prSkill
- release-notes-discordSkill
- release-notesSkill
- babysit-prSkill
- release-notes-discordSkill
- release-notesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 10 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read AGENTS.md, .github/pull_request_template.md, and relevant contribution guidance.
- Distinctive: line 15
Create or use a correctly named feature branch, commit the intended changes with the repository's commit convention, and push the branch …
- Distinctive: line 16
Check whether the current branch already has an open or draft PR.
- Distinctive: line 20
Verify the PR has the requested publication state and required screenshot attachments.
- Distinctive: line 21
When the user also requests monitoring, babysitting, or handling review comments, continue with babysit-pr.
- Distinctive: line 25
Use the conventional prefix and casing style found in recent PR history:
- Distinctive: line 47
Keep the title concise, concrete, and understandable without reading the diff.
- Distinctive: line 54
Do not check a checklist item based on intention or inference.
- Distinctive: line 55
Do not claim iRacing or other live-environment testing unless it was actually performed.
- Very specific: line 61
Keep review screenshots and recordings outside the repository worktree, such as in a temporary directory.
- Distinctive: line 63
Check the CLI that will actually perform the upload:
- Distinctive: line 70
If the installed CLI needs upgrading on Windows and that upgrade is authorized, use:
- Very specific: line 93
Use !Screenshot for an image and !
“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 a Pull Request
Publish the current work as a GitHub pull request, ready for review by default.
Workflow
- Read
AGENTS.md,.github/pull_request_template.md, and relevant contribution guidance. - Inspect the worktree, current branch, diff, commits, and remote. Never commit directly to
main. - Determine the intentional PR scope. Preserve unrelated user changes. Run checks appropriate to the changed files and report any checks that cannot be run.
- Create or use a correctly named feature branch, commit the intended changes with the repository's commit convention, and push the branch when needed.
- Check whether the current branch already has an open or draft PR. Reuse and update it instead of creating a duplicate.
- Derive the PR title from recent PR history and the rules below.
- Copy
.github/pull_request_template.mdverbatim for the PR body. Preserve every heading, HTML comment, checklist entry, and their order. Fill in applicable placeholders and check only items actually completed. Every visual change requires actual screenshot attachments as described below. Only changes with no visual impact may mark screenshots as not applicable. - Update the existing PR or create a new one as published and ready for review unless the user explicitly asks for a draft or required screenshot uploads remain blocked. Treat silence about publication state as a request for a published PR once all requirements are satisfied. If an existing PR is a draft and the user requests publication, mark it ready for review only after required screenshots are attached.
- Verify the PR has the requested publication state and required screenshot attachments. If the user did not request a draft and tooling unexpectedly leaves one, mark it ready for review and verify again only when its screenshot requirements are satisfied.
- When the user also requests monitoring, babysitting, or handling review comments, continue with babysit-pr. Otherwise return the PR's title and URL after publication verification. Publishing alone does not start an ongoing watch or authorize merging.
Title Rules
Use the conventional prefix and casing style found in recent PR history:
<type>: <problem solved or outcome achieved>Choose the type that matches the work, such as feat, fix, perf, refactor, docs, test, build, ci, or chore.
Describe the problem that is now solved or the capability the user now has. Do not merely name the implementation action, internal symbol, file, bridge, or refactor.
Good:
fix: site missing session bridge causing it to not loadAvoid:
fix: initialize browser session bridgeKeep the title concise, concrete, and understandable without reading the diff. Prefer the repository's established wording when history provides a close precedent, but apply the problem/outcome rule even if an older title was implementation-focused.
PR Body Rules
- Copy the current repository template verbatim rather than recreating it from memory. Preserve all headings, HTML comments, checklist entries, and their order.
- Explain the problem, its effect, and how the PR resolves it in the Description.
- Include exact validation performed and distinguish automated, Storybook, manual, and real-environment testing.
- Do not check a checklist item based on intention or inference.
- Do not claim iRacing or other live-environment testing unless it was actually performed.
- Preserve Before and After screenshot headings.
Review Images and Videos
- Every visual change must be shown to the user with a screenshot in the final response and have actual screenshots uploaded as GitHub attachments in the PR body. Include Before / After images for changes to existing UI, and at least an After image for new UI. Prose descriptions, Storybook links, and local image paths are not substitutes.
- Keep review screenshots and recordings outside the repository worktree, such as in a temporary directory. Do not commit them to
docs/assets/pr-reviews/or any other repository path. This does not prevent adding product assets that the user explicitly requested as part of the implementation. - Before uploading, check the selected subcommand's
--helpfor--attach(for example,gh pr comment --help). If the installed CLI lacks it, check the current official release and use an updated CLI before declaring upload unavailable. A checksum-verified portable release outside the worktree can use existing authentication without changing the installed CLI. Do not run the examples below unless the selected command advertises the flag. Check the CLI that will actually perform the upload:
gh --version gh pr edit --helpIf the installed CLI needs upgrading on Windows and that upgrade is authorized, use:
winget upgrade --id GitHub.cli --exact --silent --disable-interactivityWindows may request administrator approval. Leave that prompt for the user; do not automate it or report the upgrade complete before it finishes. Re-run
gh --versionand check the attachment flag afterward. If using a portable release instead, run these checks against that executable's full path.- When supported, upload directly with
gh pr create,gh pr edit, orgh pr commentand--attach. If the flag is absent, try an authenticated GitHub browser upload instead. If uploads remain blocked, keep the visual PR in draft, report the exact blocker, and continue recovery where possible. Do not claim publication is complete until screenshots are attached; do not commit review assets as a workaround. For a comment attachment when
--attachis supported:gh pr comment <PR-NUMBER> --body 'Review screenshot' \ --attach '/path/to/image.png#Screenshot of bug fix'To place media under the template's Before/After headings, write the body to a temporary file with local Markdown references, then pass that file and the same media paths to
gh pr createorgh pr edit:gh pr edit <PR-NUMBER> --body-file /tmp/pr-body.md \ --attach /tmp/screenshot.png --attach /tmp/replay.mp4Use
for an image andin its own paragraph for a video player.ghreplaces the local references with uploaded attachment URLs. Repeat--attachfor additional files.- Read back the PR body and verify that the uploaded attachments render and no local paths or repository-hosted review media links remain. A normal GET of each image URL can also verify delivery; do not treat a failed HEAD request alone as proof the attachment is broken. If an upload partially fails, inspect the saved body before retrying to avoid duplicates.
Publication Guardrail
Published means ready for review, not merely pushed to a remote. Visual PRs also require verified screenshot attachments before they can be marked ready for review. Unless the user explicitly requests a draft or screenshot uploads remain blocked, confirm the PR's draft flag is false before completing the task. When the user explicitly requests a draft or required screenshot uploads remain blocked, create or retain and verify a draft PR instead, and explain any blocker. Never create a duplicate PR when the branch already has one.
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.

