pr-to-ready
Make an open pull request ready to merge by checking live feedback, fixing required items, running checks, and reporting the result. Never merge.
- Installs
- 80
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owainlewis/blueprint --skill pr-to-ready- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads pr-to-ready automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
PR To Ready
- Identify the PR from
$ARGUMENTS, the current branch, or open repo PRs. - Inspect the live PR: diff, commits, checks, reviews, unresolved threads, comments, mergeability, and local git status.
- Classify feedback: actionable, disputed, resolved, outdated, informational, needs-human.
- Fix actionable items, keeping changes small. Push back on disputed items with a comment on the thread explaining why, and do not change the code. Stop for product, security, code-owner, or risk decisions.
- Run the smallest checks that prove the fix, wider checks when shared or user-facing behavior changed.
- Re-check the PR after pushing. Reply on each addressed thread with what changed. Update the linked ticket with proof when accessible.
- Report Ready, Not ready, or Blocked, with changes, checks run, pushed-back items, and remaining items.
- If asked "merge?", answer directly. Never merge.
Rules
- Never merge.
- Push back only with a concrete reason: correctness, scope, or a documented convention. Preference disagreements from a human reviewer go to needs-human, not a rebuttal.
- Do not expand the task for nice-to-have feedback.
- Do not mark ready while required checks fail or actionable feedback remains.
- Trust the live PR state, not stale summaries.
- Do not hide skipped tests, placeholders, partial fixes, or assumptions.
FAQ
What does the pr-to-ready skill do?
Make an open pull request ready to merge by checking live feedback, fixing required items, running checks, and reporting the result. Never merge.
How do I install pr-to-ready?
Run npx skills add https://github.com/owainlewis/blueprint --skill pr-to-ready in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pr-to-ready/ (personal) or .claude/skills/pr-to-ready/ (project).
Which AI agents can use pr-to-ready?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is pr-to-ready safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains pr-to-ready?
It is published by owainlewis in owainlewis/blueprint. It has 80 recorded installs.
More from owainlewis/blueprint
review
owainlewis/blueprint
Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.
plan
owainlewis/blueprint
Turns a reviewed spec or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.
task-to-pr
owainlewis/blueprint
Open the skill to read its SKILL.md instructions.
spec
owainlewis/blueprint
Open the skill to read its SKILL.md instructions.
refactor
owainlewis/blueprint
Improve the shape of existing code without changing behavior.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.