create-pr-main
Skill9 starsChanged 3 months agoMITView on GitHub
Create a pull request targeting main
- Reads credentials
In this repository43 other files it gives its agents.
- accessibility-auditSkill
- add-documentationSkill
- add-error-handlingSkill
- address-github-pr-commentsSkill
- agent-risk-reviewSkill
- agent-work-receiptSkill
- automation-roi-auditSkill
- blind-spot-passSkill
- code-reviewSkill
- commit-changes-mainSkill
- commit-same-branchSkill
- commitSkill
- debug-issueSkill
- decision-auditSkill
- define-agent-goalSkill
- design-agent-loopSkill
- fix-compile-errorsSkill
- fix-git-issuesSkill
- gauntlet-loopSkill
- generate-api-docsSkill
- generate-pr-descriptionSkill
- git-sync-workspaceSkill
- instruction-ablationSkill
- light-review-existing-diffsSkill
- lint-fixSkill
- lint-suiteSkill
- merge-open-prsSkill
- optimize-performanceSkill
- pathfinderSkill
- prompt-eval-debugSkill
- refactor-codeSkill
- requirement-to-implementationSkill
- run-all-tests-and-fixSkill
- scoped-auditSkill
- security-auditSkill
- seo-auditSkill
- setup-new-featureSkill
- structure-promptSkill
- tddSkill
- thermo-nuclear-code-quality-reviewSkill
- update-memory-bankSkill
- update-readmeSkill
- write-unit-testsSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is 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.
1
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 8
Create a well-structured pull request for the main branch of a GitHub repository with proper description, labels, and reviewers.
- Distinctive: line 13
Ensure all changes are committed to the correct branch using the conventional commit message convention
- Distinctive: line 15
Verify branch is up to date with main or master
- Very specific: line 18
Must use the PR template to write the PR description.
- Distinctive: line 22
Add screenshots if UI changes
- Distinctive: line 25
Only use the GitHub UI to create the PR.
- Distinctive: line 26
Create PR with descriptive title
- Distinctive: line 31
Do not open empty PRs; confirm the branch has real changes to review first.
- Distinctive: line 32
Use the PR template and the Conventional Commits convention for the title.
- Distinctive: line 33
Never print, stage, or commit secrets or credential files (.env, .env.*, keys).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Overview
Create a well-structured pull request for the main branch of a GitHub repository with proper description, labels, and reviewers.
Steps
- Prepare branch
- Ensure all changes are committed to the correct branch using the conventional commit message convention
- Push branch to remote
- Verify branch is up to date with main or master
- Write PR description
- Must use the PR template to write the PR description. Refer to ./pull_request_template.md for the PR template.
- Summarize changes clearly
- Include context and motivation
- List any breaking changes
- Add screenshots if UI changes
- Set up PR
- Only use the GitHub UI to create the PR. Do not use the CLI.
- Create PR with descriptive title
Guardrails
- Push only when the user asks; do not push unrequested changes before opening the PR.
- Do not open empty PRs; confirm the branch has real changes to review first.
- Use the PR template and the Conventional Commits convention for the title.
- Never print, stage, or commit secrets or credential files (.env, .env.*, keys); exclude them and warn instead.
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.