Check a pull request’s title and description against its commits and code changes. Identify missing major changes or outdated claims, propose accurate wording, and apply agreed updates while following the repository’s existing template.
Evaluate a PR's title and description against its actual implementation, then iteratively suggest and apply updates. Use when the user asks to check, fix, or update a PR title or description.
Run score Not tested
See how to installThis skill checks a pull request’s title and description against commit messages and the actual changes. A pull request, or PR, is a proposal to have changes reviewed. It identifies meaningful mismatches, such as an incorrect scope, missing major changes, or outdated explanations, and proposes revisions. You review the changes one at a time, refine the wording together, and agree on what to apply.
Use it when implementation work has left a PR description out of date, or when you want to check the accuracy of a summary before review. It leaves accurate descriptions alone and does not treat minor wording differences as reasons to edit. It follows the existing PR template and writing style, updating checkboxes and removing unfilled guidance text where appropriate.
It uses the GitHub CLI, gh. If you omit the PR number or URL, it looks for the current branch’s PR. Updates happen after your agreement. It preserves the canary release section.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
gh pr view.gh pr view <pr> --json title,bodygh pr view <pr> --json commits (commit messages)gh pr diff <pr> (full diff against base)gh pr edit <pr> --title ... --body ....No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Find a trial Storybook package for a specific branch, or trigger its publication when needed. Check release progress and obtain the package reference or commands for creating or upgrading a project with that build.
Look up a project's existing UI components in Storybook, including their props, or configuration inputs, and usage examples. Use the findings to answer questions and identify components to reuse before building duplicates.
Review, improve, rewrite, or draft Storybook documentation in /docs. Assess each page’s purpose, audience, structure, and examples, then make suitable edits or provide a content plan, with formatting checks after changes.
Check out a GitHub pull request, fix linting and TypeScript errors, and commit and push the changes. The workflow supports forked pull requests and repeats type checks to verify fixes while keeping changes focused on these errors.
Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.
Work through unresolved GitHub pull request reviews one at a time. The skill explains each comment, proposes a fix, asks how to proceed, and handles chosen edits, replies, commits, and thread resolution.