architecture-review
Reviews a technical proposal before any code is written: an architecture, spec, RFC, ADR, or design issue. Finds choices that…
@owainlewisInstall SkillDevelopment
Skill
/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.
Claude Code
$ npx -y skills add owainlewis/blueprint --skill task-to-pr --agent claude-code
Codex
$ npx skills add owainlewis/blueprint --skill task-to-pr -a codex -y
Cursor
$ npx skills add owainlewis/blueprint --skill task-to-pr -a cursor -y
Gemini CLI
$ npx skills add owainlewis/blueprint --skill task-to-pr -a gemini-cli -y
GitHub Copilot
$ npx skills add owainlewis/blueprint --skill task-to-pr -a github-copilot -y
OpenCode
$ npx skills add owainlewis/blueprint --skill task-to-pr -a opencode -y
Windsurf
$ npx skills add owainlewis/blueprint --skill task-to-pr -a windsurf -y
SKILL.md
task-to-pr.SKILL.mdname: task-to-pr
description: "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."
user-invocable: true
argument-hint: "<specs, tasks, issues, PRs, or milestone>"
disable-model-invocation: true
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
Leave the PR open. Merge only when the user asks (for example "/task-to-pr and merge it") or `/codex-issue-coordinator` was invoked by name, and only when:
- CI passes on the latest commit.
- The latest review verdict is `Approve` and no finding is open.
- Every approval the repository requires is given.
- The PR is up to date with its base.
Never bypass branch protection. After merging, update the ticket and delete any worktree you created. Merging never includes deploying or releasing.
Return
Each PR link with its check results, review verdict, CI state, and anything blocked.
Read more
name: task-to-pr description: "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." user-invocable: true argument-hint: "<specs, tasks, issues, PRs, or milestone>" disable-model-invocation: true
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
Leave the PR open. Merge only when the user asks (for example "/task-to-pr and merge it") or `/codex-issue-coordinator` was invoked by name, and only when:
- CI passes on the latest commit.
- The latest review verdict is `Approve` and no finding is open.
- Every approval the repository requires is given.
- The PR is up to date with its base.
Never bypass branch protection. After merging, update the ticket and delete any worktree you created. Merging never includes deploying or releasing.
Return
Each PR link with its check results, review verdict, CI state, and anything blocked.
Ships withblueprint
Senior engineering habits for coding agents. Small skills for Claude Code and Codex that turn an idea into a reviewed, tested pull request.
43111 skills
Stars on GitHub
Momentum
- stars in total
- 431
Other skills on blueprint.
@owainlewisInstall Skillarchitecture
Writes root ARCHITECTURE.md from a fixed template: the intended system, a data flow diagram, the data model, and the rules every…
@owainlewisInstall Skillcodex-issue-coordinato…
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated…
@owainlewisInstall Skillhtml-doc
Generates a polished, static HTML reading view from an existing Markdown PRD or technical design. Use when a user asks to render,…
@owainlewisInstall Skillimprove
Makes existing code easier to understand without changing behavior. Use to simplify structure, remove duplication or dead code,…
@owainlewisInstall Skillplan
Splits a spec into small tasks, each a working slice an agent can finish in one pull request. Use when a spec is too big for one…
@owainlewisInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about task-to-pr.
- Which coding agents can use task-to-pr?
- task-to-pr installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.