Task to PR
Delivers a spec, issue, or decided task as a pull request that passes its checks, CI, and an independent review. Leaves the PR open unless merging was explicitly authorized.
Install
npx skills add owainlewis/blueprint --skill task-to-prgit clone --depth 1 https://github.com/owainlewis/blueprint.git /tmp/blueprint
mkdir -p ~/.claude/skills
cp -r /tmp/blueprint/skills/task-to-pr ~/.claude/skills/task-to-prPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Task to PR Deliver each task as one focused pull request that passes CI and an independent review. The spec, issue, or task is the ticket; do not write another one. When a step names [test](../test/SKILL.md), [review](../review/SKILL.md), [spec](../spec/SKILL.md), or [plan](../plan/SKILL.md), read that file and follow it. ## Steps 1. Read the ticket, the repository instructions, and the code it touches. If a decision that changes behavior is missing, ask the user or return to spec. Split large work with plan. 2. Branch from the latest default branch, or continue the existing branch and PR. 3. Build the change with tests. Update `REQUIREMENTS.md`, `ARCHITECTURE.md`, or the spec if the change makes them wrong. 4. Follow test until every check passes. 5. Commit with a Conventional Commit message, push, and open the PR. Use the repository's PR template, or What, Why, What changed, Verification, and Risk if it has none. 6. Follow review. Wait for CI and any review bot on the latest commit. 7. Fix each real finding and failure, and reply on each review thread with the fix or the reason for no change. Go back to step 4. After three rounds on the same problem, stop and report it. 8. Link the PR and its proof in the ticket. ## Dependent tasks Start a task that depends on another once that task has an open PR with an `Approve` review. Branch from it, and update your branch when it changes or merges. ## Merge
Details
- Skill name
task-to-pr- Repository
- owainlewis/blueprint
- Path
skills/task-to-pr/SKILL.md- License
- MIT
- Repo updated
- 10 November 2026
FAQ
What does the Task to PR skill do?
Delivers a spec, issue, or decided task as a pull request that passes its checks, CI, and an independent review. Leaves the PR open unless merging was explicitly authorized.
How do I install the Task to PR skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add owainlewis/blueprint --skill task-to-pr. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Task to PR popular?
It lives in owainlewis/blueprint, which has 434 GitHub stars and 73 forks.
Related skills
Architecture
434owainlewis/blueprint
Writes root ARCHITECTURE.md from a fixed template: the intended system, a data flow diagram, the data model, and the rules every feature must follow. Use for a new system or a change to its boundaries, data, or deployment.
Architecture Review
434owainlewis/blueprint
Reviews a technical proposal before any code is written: an architecture, spec, RFC, ADR, or design issue. Finds choices that would make it wrong, unsafe, or impossible to prove, and the open questions that block building it.
Codex Issue Coordinator
434owainlewis/blueprint
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
Git Helper
291joshuadavidthomas/opencode-agent-skills
Provides git workflow assistance, branch management, and commit message optimization
Review
434owainlewis/blueprint
Runs an independent, read-only review of a code change in two parts: does it match the spec, and does it work. Tries bad input, checks security, and checks that the tests would catch a regression. Use for a diff, branch, commit, or PR.
Bisect Anything
517dotslashsimran/simcraft
Find the exact commit (or dependency version, config value, or input) that caused a regression by turning it into an automatic pass/fail check and running git bisect run in a separate worktree, then shrink the bad commit to the hunk that matters and explain it. Handles failing tests, changed output, slowdowns, crashes, visual changes, server behaviour, flaky checks, unbuildable commits and merge-heavy history. Use when the user says "what broke this", "find the commit that", "when did this start", "it used to work", "regression", "git bisect", "which version broke it", or "which change made it
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.