pr-workflow
Skill0 starsChanged 3 months agoMITView on GitHub
Create a pull request with auto-generated title, body, and linked issues from commit history (create PR, open pull request, submit PR).
- Commits and pushes
22 other projects use a version of this.
Adopted by
Most recently taken up by
- sbluemin/fleet-harnesstheir own version, first seen Nov 8, 2026
- notque/vexjoy-agenttheir own version, first seen Nov 7, 2026
- yktsnet/dotfiles-publictheir own version, first seen Nov 5, 2026
- OneByJorah/VirtOfficetheir own version, first seen Nov 1, 2026
- ryanschue/automated-product-engineertheir own version, first seen Nov 1, 2026
- OneByJorah/offivotheir own version, first seen Oct 20, 2026
Used with
Projects with it also use workflow and code-review.
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.
VercelSkillworkflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.
Also in 4 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- tursodatabase/turso★ 25ksame name
- esphome/esphome★ 12ksame name
- open-edge-platform/anomalib★ 6.4ksame name
- Chorus-AIDLC/Chorus★ 1.2ksame name
- glommer/pgmicro★ 1.2ksame name
- Tencent-Hunyuan/UniRL★ 1ksame name
- esphome/esphome-docs★ 466same name
- notque/claude-code-toolkit★ 448same name
- notque/vexjoy-agent★ 448same name
- mezotv/notra★ 256same name
12 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 repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- ai-engineerSkill
- api-clientSkill
- changelog-enforcerSkill
- code-cleanup-guardianSkill
- code-reviewerSkill
- contract-testSkill
- db-migrateSkill
- dep-auditSkill
- devops-automatorSkill
- env-configSkill
- error-observabilitySkill
- frontend-designSkill
- git-commit-helperSkill
- github-issues-managerSkill
- git-issue-syncSkill
- git-protocolSkill
- handoffSkill
- incident-responseSkill
- init-projectSkill
- karpathy-guidelinesSkill
- market-researcherSkill
- parallel-agent-git-isolationSkill
- product-strategistSkill
- rapid-builderSkill
- release-managerSkill
- resumeSkill
- scrutinizeSkill
- shadcn-uiSkill
- skill-builderSkill
- sprint-plannerSkill
- state-machine-diagramsSkill
- state-managementSkill
- surveySkill
- system-architectSkill
- tech-docsSkill
- unstuckSkill
- ux-design-systemSkill
- ux-researchSkill
- webapp-testingSkill
- web-dev-fundamentalsSkill
- workflow-optimizerSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
If there are uncommitted changes, warn the user
- Distinctive: line 41
If there are no commits vs main, abort with a message
- Very specific: line 42
Verify the branch is pushed to remote: git push -u origin $(git branch --show-current)
- Distinctive: line 78
Always link to issues found in commit messages
- Distinctive: line 79
Keep summary concise — the diff tells the full story
“Common” is measured: kept by at least 6 in 10 of the 19 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
Pull Request Workflow
Pre-fetched Context
Current Branch
!git branch --show-current 2>/dev/null
Commits on This Branch (vs main)
!git log main..HEAD --oneline 2>/dev/null || git log origin/main..HEAD --oneline 2>/dev/null || echo "Cannot determine commits vs main"
Changed Files
!git diff main..HEAD --name-only 2>/dev/null || echo "Cannot determine changed files"
Diff Stats
!git diff main..HEAD --stat 2>/dev/null || echo "Cannot determine diff stats"
Open Issues Referenced in Commits
!git log main..HEAD --pretty=format:"%s" 2>/dev/null | grep -oE "#[0-9]+" | sort -u || echo "No issue references found"
Uncommitted Changes
!git status --porcelain 2>/dev/null
Your Task
Using the pre-fetched data above:
1. Pre-flight Checks
- If there are uncommitted changes, warn the user
- If there are no commits vs main, abort with a message
- Verify the branch is pushed to remote:
git push -u origin $(git branch --show-current)
2. Generate PR Content
From the commit history, generate:
Title: Under 70 characters, summarizing the change. Use the dominant commit type (feat/fix/refactor).
Body:
## Summary
[2-3 bullet points describing what changed and why, derived from commit messages]
## Changes
[List of significant files changed with brief explanation]
## Issues
[List of Closes #N / Fixes #N from commit messages]
## Testing
- [ ] All tests passing
- [ ] Type checker passes
- [ ] Linter passes
- [ ] Manual testing completed3. Create the PR
gh pr create --title "title" --body "$(cat <<'EOF'
body content
EOF
)"4. Return the PR URL
Rules
- Always link to issues found in commit messages
- Keep summary concise — the diff tells the full story
- Base branch defaults to
mainunless $ARGUMENTS specifies otherwise
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.

