pr
Skill245 starsChanged 9 months agoMITView on GitHub
Commit, push, and open a pull request on GitHub
- Reads credentials
- Commits and pushes
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 14 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
5
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, push the branch, and open a pull request on GitHub.
- Distinctive: line 14
Run git status to see changed files
- Distinctive: line 15
Run git diff --staged and git diff to see all changes
- Distinctive: line 16
Run git log --oneline -5 to see recent commits
- Distinctive: line 20
Never stage sensitive files (.env, credentials, etc.)
- Very specific: line 21
Follow conventional commit format: type(scope): description
- Distinctive: line 22
Keep commit messages concise (under 72 characters)
- Very specific: line 25
If on main, create a new branch: git checkout -b <branch-name>
- Distinctive: line 27
If already on a feature branch, use it
- Very specific: line 33
Add --label flags to gh pr create based on the PR type and scope.
- Very specific: line 51
Run gh label list to check available labels if unsure.
- Very specific: line 58
Use gh pr create to open the PR
- Distinctive: line 59
Write a clear title (under 70 characters)
- Distinctive: line 60
Write a description that follows the structure below based on PR type
- Distinctive: line 61
Start with a Type checklist — check the one that applies:
- Distinctive: line 96
Run git status to confirm clean state
- Distinctive: line 100
Do NOT push to main directly — always use a feature branch
- Distinctive: line 101
Do NOT force push unless explicitly requested
- Distinctive: line 102
Ask user before proceeding with each step
≈ “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
Pull Request Skill
Commit changes, push the branch, and open a pull request on GitHub.
Instructions
- Check Current State
- Run
git statusto see changed files - Run
git diff --stagedandgit diffto see all changes - Run
git log --oneline -5to see recent commits
- Run
- Stage and Commit
- Stage specific files by name (avoid
git add -Aorgit add .) - Never stage sensitive files (.env, credentials, etc.)
- Follow conventional commit format:
type(scope): description - Keep commit messages concise (under 72 characters)
- Stage specific files by name (avoid
- Create or Use Branch
- If on
main, create a new branch:git checkout -b <branch-name> - Branch name format:
type/short-description(e.g.,feat/code-comparison,fix/marker-cleanup) - If already on a feature branch, use it
- If on
- Push to Remote
- Push with upstream tracking:
git push -u origin <branch-name>
- Push with upstream tracking:
Assign Labels Add
--labelflags togh pr createbased on the PR type and scope.Type labels — pick based on the commit type:
Commit type Label fixbugfeatenhancementdocsdocumentationtest(no type label) refactor(no type label) chore(no type label) Component labels — if the scope matches a component label in the repo, add it:
Scope Label compassCompassinteractionInteractionRun
gh label listto check available labels if unsure. Multiple labels can be combined:gh pr create --label "bug" --label "Compass" ...Open Pull Request
- Use
gh pr createto open the PR - Write a clear title (under 70 characters)
- Write a description that follows the structure below based on PR type
- Start with a Type checklist — check the one that applies:
gh pr create --title "type(scope): description" --label "label" --body "$(cat <<'EOF' ## Type - [ ] Feature - [ ] Bug fix - [ ] Refactor - [ ] Test - [ ] Docs - [ ] Chore ## Summary - bullet points describing what changed and why ## Bug Details (only for bug fixes) **What was the bug?** Describe the incorrect behavior. **Why did it happen?** Explain the root cause. **How was it fixed?** Describe the solution. ## Test Coverage If tests were added or updated, link to the file on the branch (permalink): - [`src/registry/map/__tests__/component.test.tsx`](https://github.com/alamenai/terrae/blob/<branch-name>/src/registry/map/__tests__/component.test.tsx) EOF )"- Use
- Verify and Report
- Show the PR URL to the user
- Run
git statusto confirm clean state
Important Rules
- Do NOT push to
maindirectly — always use a feature branch - Do NOT force push unless explicitly requested
- Ask user before proceeding with each step
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.

