pr
Skill181 starsChanged 7 months agoMITView on GitHub
Create a pull request using the wingman PR template. Injects git state, commit history, and diff stats automatically.
- Commits and pushes
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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
- Very specific: line 15
Read .github/PULL_REQUEST_TEMPLATE.md and fill every section.
- Distinctive: line 16
Do not free-form the PR body.
- Very specific: line 26
Use gh pr create with --body "$(cat <<'EOF' ...
- Distinctive: line 28
If the diff exceeds 500 lines, do not create the PR.
- Distinctive: line 42
Read the PR template
- Distinctive: line 43
Create the PR with every template section filled
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Context (auto-detected from HEAD)
- Current branch: !
git branch --show-current - Remote status: !
git status -sb | head -1
PR Template
Read .github/PULL_REQUEST_TEMPLATE.md and fill every section. The template is mandatory.
Do not free-form the PR body.
Rules
- PR title:
type(scope): description(conventional commit format, under 70 chars) - Target branch: first positional arg from
$ARGUMENTSif provided, otherwisemain - Source branch: if
--branch <name>is in$ARGUMENTS, use that branch for diff/log commands instead of HEAD. This is needed when the PR branch lives in a different worktree or the main repo checkout. - Push with
-uif needed - Use
gh pr createwith--body "$(cat <<'EOF' ... EOF)"for correct formatting - Hard limit: 500 changed LOC (excluding generated files and lock files). If the diff exceeds 500 lines, do not create the PR. Instead, propose a stacked-PR plan: split changes into logical, independently reviewable PRs where each PR is under 500 LOC. Each stacked PR targets the previous one's branch (not main) until the final one merges the stack into main.
- Warn at 200 changed lines — suggest splitting proactively
Task
- Determine the source branch: use
--branchvalue if provided, otherwise current HEAD - Gather context by running:
git log --oneline origin/main..<source-branch>(commits for this PR)git diff --stat origin/main..<source-branch>(diff stats)git diff --name-only origin/main..<source-branch>(changed files)
- Push the branch if needed
- Read the PR template
- Create the PR with every template section filled
- Return the PR URL
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.

