kit-create-pr
Skill6 starsChanged 27 days agoMITView on GitHub
Commit changes and create a pull request with proper formatting. Use when ready to publish work for review.
- Commits and pushes
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- kit-audit-metricsSkill
- kit-audit-skillsSkill
- kit-capture-lessonSkill
- kit-challenge-designSkill
- kit-check-blastSkill
- kit-debate-decision-treeSkill
- kit-debug-prodSkill
- kit-decisionsSkill
- kit-evolveSkill
- kit-explainSkill
- kit-learn-repoSkill
- kit-minimizeSkill
- kit-optimize-contextSkill
- kit-planSkill
- kit-proveSkill
- kit-reviewSkill
- kit-strip-diffSkill
- kit-triage-commentsSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
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
- could be automatic: a setting could enforce it
- Distinctive: line 9
Commit changes and create a pull request with proper formatting.
- Distinctive: line 15
Read the current branch:
- Very specific: line 19
If the branch or the user supplies a tracker id (Jira, Linear, GitHub issue, and similar), prefix commit and PR titles with it, for example …
- Distinctive: line 31
Do not: run git add -A (or stage everything) unless they explicitly approve that full set.
- Distinctive: line 32
Default: stage only the paths they named, or ask which paths to include.
- Distinctive: line 53
Ask: "What did users experience that was wrong?"
- Distinctive: line 90
Use descriptive lowercase names with hyphens
- Very specific: line 95
Strip: if the diff is fatter than the outcome, kit-strip-diff before review.
- Very specific: line 96
Review: prefer kit-review author on the branch diff before publish.
- Distinctive: line 98
Diff: no secrets, no probe/TEMP validation junk, no unrelated drive-bys.
- Distinctive: line 99
History: do not force-push to the default branch.
- Distinctive: line 133
After completion, provide user with (DO NOT wrap in code block - URLs must be clickable):
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Create PR
Commit changes and create a pull request with proper formatting.
Flow
1. Optional tracker id
Read the current branch:
git rev-parse --abbrev-ref HEADIf the branch or the user supplies a tracker id (Jira, Linear, GitHub issue, and similar), prefix commit and PR titles with it, for example [ABC-123]. If there is none, omit the prefix. Do not invent an id.
2. Commit Changes
A. Check git status:
git statusB. Stage changes:
- Show
git status/ the file list to the user. - Do not run
git add -A(or stage everything) unless they explicitly approve that full set. - Default: stage only the paths they named, or ask which paths to include.
git add path/to/file [...]C. Commit:
git commit -m "Fix: <problem users experience>"
# or, if a tracker id exists:
git commit -m "[ABC-123] Fix: <problem users experience>"Commit message format:
- Bug fix:
Fix: <problem users experience> - Feature:
Feature: <what users can now do> - Improvement:
Improve: <what's better for users> - Refactor:
Refactor: <description> - With tracker:
[ABC-123] Fix: <problem users experience>
Important:
- Describe the PROBLEM, not your solution
- Ask: "What did users experience that was wrong?"
3. Create Pull Request
A. Push the branch:
git push -u origin HEADB. Create PR using gh CLI:
gh pr create \
--title "Fix: <problem users experience>" \
--body "## Problem
<What users experienced - why this matters to them>
## Solution
<Brief explanation of how it's fixed>"Best Practices
Commit Message
- Format:
Type: Description(optional[TRACKER-ID]prefix) - Types: Fix, Feature, Improve, Refactor
- Description: Describe the problem being fixed, not the code change
- Length: One line, < 72 chars if possible
- Tense: Imperative mood (Fix, Add, Update - not Fixed, Added, Updated)
- Bad: "Add null check to user handler" (what you did)
- Good: "Users see crash when opening empty profile" (what users experienced)
PR Description
- Problem: What the user experienced (lead with this, make it clear why it matters)
- Solution: Brief explanation of how it's fixed (keep technical details minimal)
- Skip "Root Cause" and "Changes" sections - focus on user impact
Branch Naming
- Use descriptive lowercase names with hyphens
- Examples:
fix-login-redirect,feature-chat-export,improve-loading-speed
Hygiene (before publish)
- Strip: if the diff is fatter than the outcome,
kit-strip-diffbefore review. - Review: prefer
kit-review authoron the branch diff before publish. - Branch: descriptive lowercase with hyphens (
fix-…,feature-…). Prefer syncing with default branch before open if the branch is stale (git fetch+ rebase/merge per repo norm). - Diff: no secrets, no probe/TEMP validation junk, no unrelated drive-bys.
- History: do not force-push to the default branch. Force-push to your feature branch only if the user explicitly asks.
- Remote: push with
-uon first publish; confirmgh pr view/ URL after create.
Troubleshooting
Finding Current Branch PR
gh pr view --json number,url,titleExample Complete Flow
1. Branch: fix-new-chat-reload (no tracker id)
2. Commit:
git commit -m "Fix: New Chat button returns to previous chat after reload"
3. Push:
git push -u origin fix-new-chat-reload
4. Create PR:
gh pr create \
--title "Fix: New Chat button returns to previous chat after reload" \
--body "## Problem
Users click New Chat expecting a fresh conversation, but after page reload they see the previous chat instead.
## Solution
Clear chat state properly when starting a new conversation."
→ Result: PR #1780Output Format
After completion, provide user with (DO NOT wrap in code block - URLs must be clickable):
✅ Commit: <Type>: <Description>
✅ PR: #NUMBER - <Title>
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.

