Install any skill in seconds. Free to start, no credit card required.
Get Started Free →posit-dev/pr-create
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes.
Passed 15 of 19 test cases with the skill, and 9 of 19 without it.
and 4 more in the full report
7 fixed8 passed either way3 still failing1 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
During Step 5 preview of PR details, under what specific user selection option should the detailed 6-step plan outline be presented to the user?
| Checked | Without skill | With skill |
|---|---|---|
| Shows the plan outline only when the user selects option 2 ('Looks good, tell me what you'll do next'). | Missed | Passed |
The instructions your model reads when the skill loads.
Get changes into a PR, monitor CI, fix any failures, and notify the user when the PR is ready for review.
The user may already have commits ready on a feature branch, or may have uncommitted changes, or both. Adapt the workflow to the current state.
CRITICAL: Use your harness's task list system (e.g., TaskCreate, TaskUpdate, and TaskList tools) for progress tracking and session recovery. Use these tools throughout execution.
[Main Task] "Create PR: [branch-name]"
└── [CI Task] "CI Run #1" (status: failed, reason: lint)
└── [Fix Task] "Fix: lint"
└── [CI Task] "CI Run #2" (status: failed, reason: test failures)
└── [Fix Task] "Fix: test failures"
└── [CI Task] "CI Run #3" (status: passed)
At the start, always call TaskList to check for existing PR tasks. If a "Create PR" task exists with status in_progress, resume using the Session Recovery section below.
Check for a --reviewer argument in the user's message. If present, store the value for use in Step 5. It may be a GitHub handle (@username) or a name (Jane Doe).
Create the main PR task:
TaskCreate:
- subject: "Create PR: [branch-name or 'pending']"
- description: "Create pull request from current changes."
- activeForm: "Checking git status"
TaskUpdate:
- taskId: [pr task ID]
- status: "in_progress"
test cases passed, vs 9 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.