pr-finalize Skill
Finalizes any PR for merge by verifying title/description match implementation AND performing code review for best practices. Use when asked to "finalize PR", "check PR description", "review commit message", before merging any PR, or when PR implementation changed during review. Do NOT use for extracting lessons or inv Published by microsoft in garnet.
Decision snapshot
Is this a fit?
Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is pr-finalize Skill?
Finalizes any PR for merge by verifying title/description match implementation AND performing code review for best practices. Use when asked to "finalize PR", "check PR description", "review commit message", before merging any PR, or when PR implementation changed during review. Do NOT use for extracting lessons or inv Published by microsoft in garnet. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Declared skill metadata
- Source file: .github/skills/pr-finalize/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use pr-finalize Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/garnet
- Skill file: .github/skills/pr-finalize/SKILL.md
What it does
Finalizes any PR for merge by verifying title/description match implementation AND performing code review for best practices. Use when asked to "finalize PR", "check PR description", "review commit message", before merging any PR, or when PR implementation changed during review. Do NOT use for extracting lessons or inv
Skill instructions
PR Finalize Ensures PR title and description accurately reflect the implementation, and performs a code review for Garnet best practices before merge. Standalone skill — Can be used on any PR. Two-Phase Workflow 1. Title & Description Review — Verify PR metadata matches implementation 2. Code Review — Review code for Garnet-specific best practices and potential issues --- 🚨 CRITICAL RULES 1. NEVER Approve or Request Changes AI agents must NEVER use --approve or --request-changes flags. | Action | Allowed? | Why | |--------|----------|-----| | gh pr review --approve | ❌ NEVER | Approval is a human decision | | gh pr review --request-changes | ❌ NEVER | Blocking PRs is a human decision | 2. NEVER Post Comments Directly This skill is ANALYSIS ONLY. Never post comments using gh commands. | Action | Allowed? | Why | |--------|----------|-----| | gh pr review --comment | ❌ NEVER | Present findings to the user instead | | gh pr comment | ❌ NEVER | Present findings to the user instead | | Ana
Verified compatibility and discovery
Frequently asked questions
What is pr-finalize?
pr-finalize is a open-source AI agent skill with Copy skill directory. Finalizes any PR for merge by verifying title/description match implementation AND performing code review for best practices.
Who is pr-finalize best for?
pr-finalize is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install pr-finalize?
Install or run pr-finalize using Copy skill directory. Check pr-finalize for the latest setup command.
Is pr-finalize actively maintained?
pr-finalize may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
