github-issue-pr-workflow
Skill1 starsChanged 6 months agoMITView on GitHub
Use when generating GitHub issue plans, PR plans, branch names, commit scopes, review checklists, merge guidance, or issue-first workflow guidance.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms.txtllms.txt
- ai-app-security-reviewSkill
- codeaudit-orchestratorSkill
- codeauditSkill
- docs-claims-evidence-reviewSkill
- enterprise-code-qualitySkill
- nextjs-security-reviewSkill
- official-docs-groundingSkill
- python-backend-qualitySkill
- python-mcp-server-qualitySkill
- refactor-with-testsSkill
- skill-supply-chain-auditorSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Create or propose an issue first.
- Distinctive: line 13
Use a clean scoped branch.
- Distinctive: line 14
Keep commits focused and descriptive.
- Distinctive: line 35
No auto-push, branch deletion, remote mutation, or auto-merge without explicit user approval.
≈ “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
GitHub Issue PR Workflow
Required Flow
- Create or propose an issue first.
- Use a clean scoped branch.
- Keep commits focused and descriptive.
- Link the PR to the issue.
- List tests run.
- Describe security impact and docs impact.
- Merge only after clean review and verification.
Branch Names
fix/issue-12-api-rate-limitrefactor/issue-18-split-security-utilsdocs/issue-21-evidence-map
PR Body Sections
- Linked issue
- Summary
- Tests run
- Security impact
- Docs impact
- Screenshots when UI changed
No auto-push, branch deletion, remote mutation, or auto-merge without explicit user approval.
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.

