Install any skill in seconds. Free to start, no credit card required.
Get Started Free →platformplatform/create-pull-request
Create a GitHub pull request.
Passed 13 of 18 test cases with the skill, and 10 of 18 without it.
and 2 more in the full report
5 fixed11 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I modified a C# controller in src/PlatformPlatform.Api/Endpoints/Users.cs. I want to build before running tests. Should I run build --backend to save time, or just build?
| Checked | Without skill | With skill |
|---|---|---|
| Selects build without flags. | Missed | Passed |
The instructions your model reads when the skill loads.
Run in parallel (quick reads, not background):
git status - working tree stategit branch --show-current - local branchgit --no-pager log --format=%s --reverse $(git merge-base HEAD main)..HEAD - commits on the branchgit --no-pager diff main - full diffgit rev-parse @{u} 2>/dev/null - upstream presence (already pushed?)gh pr view --json number,url,state 2>/dev/null (only if upstream exists) - check if the branch already has an open pull requestEverything in this step starts in the background (run_in_background: true) so the workflow proceeds without waiting. Results are reconciled in STEP 10.
Skip anything already green this session. Only run what's genuinely uncertain.
When validation IS needed:
Run build first:
build (no flags - covers backend AND frontend; backend changes can break the frontend build via API contracts)build --frontendbuild --cliAfter build, in parallel (with --no-build where applicable):
aspire-restart - service / Aspire wiring changedformat --<target>, lint --<target> - for each target whose code changedtest --no-build - backend changee2e - frontend or shared E2E-covered code changed; use --smoke for low-impact changes (judgment)Use judgment to decide which target a file belongs to (e.g. project / manifest / lock files affect their owning build, even when the extension isn't obvious). Each item runs only if needed and not already green.
Three checks - all read-only at this stage; renames happen in STEP 8.
test cases passed, vs 10 / 18 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.