Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →florianbruniaux/pr
Analyze changes, detect scope issues, and create a well-structured PR
Passed 18 of 20 test cases with the skill, and 13 of 20 without it.
and 2 more in the full report
5 fixed13 passed either way2 still failing0 broke2 errored
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.
When structuring the sections of a pull request body template, developers often start immediately with detailed technical description or bullet lists. What specific top section must lead the description and what is its length constraint?
| Checked | Without skill | With skill |
|---|---|---|
| Places a TLDR summary section at the top of the body template. | Passed | Passed |
| Constrains the TLDR section to a maximum length of 2 lines. | Missed | Passed |
The instructions your model reads when the skill loads.
Analyze changes, detect scope issues, and create a well-structured PR following project conventions.
gh pr create with proper formattingCalculate PR complexity to detect if split is needed:
| Criterion | Weight | Description |
|---|---|---|
| Code files | x2 | *.ts, *.tsx (excluding tests) |
| Test files | x0.5 | *.test.ts, *.spec.ts |
| Config files | x1 | *.json, *.yml, *.md |
| Directories | x3 | Distinct src/* directories |
| Commits | x1 | Number of commits |
Thresholds: 0-15 ✅ Normal | 16-25 ⚠️ Large | 26+ 🔴 Split recommended
| Pattern | Verdict |
|---|---|
| Single scope | ✅ OK |
| Related scopes (sessions + calendar) | ✅ OK |
| Unrelated scopes (payments + auth) | 🔴 Split |
| feat + fix same scope | ✅ OK |
| feat + fix different scopes | 🔴 Split |
test cases passed, vs 13 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.