raise-pr
Skill2 starsChanged 2 days agoMITView on GitHub
Lint, commit, push and open a PR with screenshots and an at-a-glance description; merge only when asked. Use when the user asks to raise, open or ship a PR for the current work, optionally naming a base branch and whether to merge.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- atomicinnovation/acceleratortheir own version, first seen Nov 14, 2026
- seankoji-com/.agentstheir own version, first seen Nov 8, 2026
- Pubx-ai/skillstheir own version, first seen Nov 8, 2026
- bwhtech/skillsword for word, first seen Oct 13, 2026
- dr-zog/plumblinetheir own version, first seen Aug 27, 2026
- hiteshbandhu/skills-i-usetheir own version, first seen Jun 26, 2026
Other versions7 projects use a version of this.
Word for word · 1
- bwhtech/skills★ 3100% same
Edited · 0
None found.
Wrote their own version · 6
- Shopify/flash-list★ 7.2ksame name
- atomicinnovation/accelerator★ 35same name
- Pubx-ai/skills★ 6same name
- seankoji-com/.agents★ 2same name
- hiteshbandhu/skills-i-use★ 1same name
- dr-zog/plumbline★ 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.
- control-roomSkill
- dsa-conscious-codingSkill
- excalidraw-architectureSkill
- improve-codebase-architectureSkill
- issue-to-phasesSkill
- pr-screenshotsSkill
- visual-reviewerSkill
- wayfinderSkill
- workSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Branch: If on the base branch, create type/short-slug first.
- Very specific: line 12
Strip comments: Remove every comment and docstring the branch adds (git diff <base>...
- Distinctive: line 15
No exceptions without the user's explicit approval of that specific comment.
- Very specific: line 16
Lint like CI: If .pre-commit-config.yaml exists, run pre-commit run --all-files until a run is clean.
- Very specific: line 20
Screenshots: If the diff changes what renders (.html, .vue, .jinja, templates, CSS, frontend JS), follow the pr-screenshots skill steps …
“Common” is measured: kept by at least 6 in 10 of the 6 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
Raise a pull request for the current work. Take the base branch, whether to merge, and a line on what the change is for from the user's request.
- Branch. If on the base branch, create
type/short-slugfirst. Base = the branch named in the request, else the repo default (gh repo view --json defaultBranchRef). Confirm the base exists onorigin— a local-onlymainis not a valid base. - Strip comments. Remove every comment and docstring the branch adds (
git diff <base>...plus uncommitted changes): Python#comments and docstrings, JS//and/* */, CSS/* */, HTML/Jinja comments. Keep licence headers, shebangs and lint pragmas (# noqa,# type:,// eslint-disable). No exceptions without the user's explicit approval of that specific comment. - Lint like CI. If
.pre-commit-config.yamlexists, runpre-commit run --all-filesuntil a run is clean. CI runs--all-fileswith the hook-pinned ruff, which can disagree with local ruff. Exclude vendored/minified files (public/js/vendor/,*.min.js) from formatters instead of reformatting them. - Commit. Stage explicit paths only. Conventional one-line message:
type(scope): subject. - Screenshots. If the diff changes what renders (
.html,.vue,.jinja, templates, CSS, frontend JS), follow thepr-screenshotsskill steps 1–4: capture, crop + annotate, visual review, commit the images underdocs/implementation/media/. Push and open the PR with this body and nothing else:
1. <the problem, in user terms> 2. <what you can do now> You can visit <route / screen> to see it. <img src="https://github.com/<owner>/<repo>/blob/<branch>/docs/implementation/media/<name>.png?raw=1" width="700">No "Verified:" line, no implementation notes, no "Generated with Claude Code" or session-link footer. Set the body with
gh api -X PATCH repos/<owner>/<repo>/pulls/<n> -f body=..., read it back, andcurl -sL -o /dev/null -w "%{http_code} %{content_type}"every image URL (must be200 image/png).- CI.
gh pr checks <n> --watch. Fix failures and push again; never merge a red PR. - Merge only if the request asks for it.
gh pr merge <n> --mergeonce checks are green. Keep the branch: the screenshot URLs point at it and die when it is deleted.
Report the PR URL, the checks result, and whether it was merged.
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.

