hashiiiii-pull-request
Skill10 starsChanged 3 months agoMITView on GitHub
Use this skill to create or edit a GitHub pull request with the repository template or the default structure.
- Commits and pushes
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hallmarkSkill
- hashiiiii-explain-prSkill
- hashiiiii-gitSkill
- hashiiiii-imagesSkill
- hashiiiii-issuesSkill
- hashiiiii-localeSkill
- hashiiiii-write-enSkill
- hashiiiii-write-jaSkill
- hashiiiii-zigSkill
- show-meSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use the repository's pull request template when one exists.
- Distinctive: line 15
If there are multiple templates, use the one selected by the user or repository.
- Distinctive: line 19
If no template exists, use:
- Distinctive: line 38
If work is incomplete, create a draft.
- Very specific: line 40
Create a pull request with gh pr create --title "<type>: <subject>" --body-file <file>.
≈ “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 Conventions
Use the repository's pull request template when one exists. Search in this order:
.github/pull_request_template.md.github/PULL_REQUEST_TEMPLATE.mdpull_request_template.md- A single Markdown file under
.github/PULL_REQUEST_TEMPLATE/
If there are multiple templates, use the one selected by the user or repository. Preserve the selected template's headings, order, and subsections, and fill every heading.
Resolve the pull-requests language through the shared locale rules for the title and body. Preserve repository template headings. Keep default template headings in English.
If no template exists, use:
## Summary
## Motivation
## Changes
## Testing| Section | Content |
| Summary | Describe the change in one or two sentences. |
| Motivation | Explain why and link a related issue with Closes #NNN. |
| Changes | List the important changes. |
| Testing | List commands run and their actual results. |
If work is incomplete, create a draft. Use the same type for the branch, commit, and title. See hashiiiii-git for the type and title format.
Create a pull request with gh pr create --title "<type>: <subject>" --body-file <file>. Add --draft when work is incomplete.
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.

