git-pr-workflows-pr-enhance
Skill2 starsChanged 8 months agoMITView on GitHub
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensu
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- xfstudio/skillsedited, first seen Oct 13, 2026
- ai4brands-design/claude-skillsedited, first seen Mar 22, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- xfstudio/skills★ 998% same
- ai4brands-design/claude-skills★ 298% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-native-cliSkill
- api-documentationSkill
- api-security-best-practicesSkill
- architectureSkill
- bash-proSkill
- clean-codeSkill
- code-review-excellenceSkill
- debugging-strategiesSkill
- documentationSkill
- github-actions-templatesSkill
- ios-developerSkill
- performance-optimizerSkill
- rust-async-patternsSkill
- rust-proSkill
- security-auditSkill
- swiftui-expert-skillSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- testing-patternsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 34
If detailed examples are required, open resources/implementation-playbook.md.
- Distinctive: line 42
Test Coverage: Before/after coverage comparison
≈ “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
Pull Request Enhancement
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.
Use this skill when
- Working on pull request enhancement tasks or workflows
- Needing guidance, best practices, or checklists for pull request enhancement
Do not use this skill when
- The task is unrelated to pull request enhancement
- You need a different domain or tool outside this scope
Context
The user needs to create or improve pull requests with detailed descriptions, proper documentation, test coverage analysis, and review facilitation. Focus on making PRs that are easy to review, well-documented, and include all necessary context.
Requirements
$ARGUMENTS
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Output Format
- PR Summary: Executive summary with key metrics
- Detailed Description: Comprehensive PR description
- Review Checklist: Context-aware review items
- Risk Assessment: Risk analysis with mitigation strategies
- Test Coverage: Before/after coverage comparison
- Visual Aids: Diagrams and visual diffs where applicable
- Size Recommendations: Suggestions for splitting large PRs
- Review Automation: Automated checks and findings
Focus on creating PRs that are a pleasure to review, with all necessary context and documentation for efficient code review process.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
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.