pr-readiness Skill
Verify that a pull request into microsoft/vscode-makefile-tools meets contribution requirements. Use when preparing, reviewing, or finalizing a PR to check for a descriptive title, a meaningful description, a properly formatted CHANGELOG entry, code correctness, regression risks, adherence to existing patterns, and whe Published by microsoft in vscode-makefile-tools.
What is pr-readiness Skill?
Verify that a pull request into microsoft/vscode-makefile-tools meets contribution requirements. Use when preparing, reviewing, or finalizing a PR to check for a descriptive title, a meaningful description, a properly formatted CHANGELOG entry, code correctness, regression risks, adherence to existing patterns, and whe Published by microsoft in vscode-makefile-tools. 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.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using vscode-makefile-tools
Technical details
- Install or run with Copy skill directory
When to use pr-readiness Skill
- Use it for developers using vscode-makefile-tools.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-makefile-tools
- Skill file: .github/skills/pr-readiness/SKILL.md
What it does
Verify that a pull request into microsoft/vscode-makefile-tools meets contribution requirements. Use when preparing, reviewing, or finalizing a PR to check for a descriptive title, a meaningful description, a properly formatted CHANGELOG entry, code correctness, regression risks, adherence to existing patterns, and whe
Skill instructions
PR Readiness PR Requirements Checklist 1. PR Title The title must clearly and concisely describe the change from the user's perspective. It should: - Start with a verb (e.g., "Fix", "Add", "Improve", "Remove", "Update"). - Mention the affected feature or area (e.g., dry-run parsing, IntelliSense, build targets, configurations, tree view). - Be specific enough that a reader understands the change without opening the PR. Good examples: - Fix dry-run parser not recognizing cross-compiler prefixed gcc invocations - Add support for pre-configure script arguments in makefile.configurations - Improve target parsing to handle makefile variable-defined targets Bad examples: - Fix bug (too vague) - Update code (no useful information) - WIP (not ready for review) 2. PR Description The PR body must include: - What changed: A short summary of the user-visible behavior change. - Why: The motivation — link to a GitHub issue if one exists (e.g., Fixes 1234). - How (if non-obvious): A brief explanation
Explore related resources
Frequently asked questions
What is pr-readiness?
pr-readiness is a open-source AI agent skill with Copy skill directory. Verify that a pull request into microsoft/vscode-makefile-tools meets contribution requirements.
Who is pr-readiness best for?
pr-readiness is best for reusing agent instructions, scripts, and references.
How do I install pr-readiness?
Install or run pr-readiness using Copy skill directory. Check pr-readiness for the latest setup command.
Is pr-readiness actively maintained?
pr-readiness may need a closer maintenance check before production use.
Auto-fetched from GitHub.
