agentleFS
Sign inStart free
owainlewisowainlewis/blueprint/skills/task-to-pr/SKILL.md

task-to-pr

Skill423 starsChanged 3 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Rajveerx11/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository12 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a step names test, review, spec, or plan, read that file and follow it.

    line 13
  2. Distinctive:

    Read the ticket, the repository instructions, and the code it touches.

    line 17
  3. Distinctive:

    Follow test until every check passes.

    line 20
  4. Distinctive:

    Commit with a Conventional Commit message, push, and open the PR.

    line 21
  5. Distinctive:

    Follow review. Wait for CI and any review bot on the latest commit.

    line 22
  6. Very specific:

    Start a task that depends on another once that task has an open PR with an Approve review.

    line 28
  7. Very specific:

    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, …

    line 32
  8. Distinctive:

    Every approval the repository requires is given.

    line 36
  9. Distinctive:

    Never bypass branch protection.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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, review, spec, or plan, 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free