CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-splitter

Use when breaking a large, complex, messy, or hard-to-review pull request into multiple smaller PRs; planning stacked PRs; extracting independent changes from a branch; splitting mixed refactor and behavior changes; managing drift after review feedback; rebasing follow-up PRs as earlier PRs change; or preserving original branch intent while shipping incrementally.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill body that gives concrete git commands and templates for a destructive workflow. The main gaps are a slightly implicit error-recovery feedback loop and all content being inline with no bundle references.

Suggestions

Make the validation feedback loop explicit in step 6, e.g. 'If build/tests fail, fix in the split branch and re-run before proceeding — do not advance until verification passes.'

Tighten the Changesets section by merging each point's restatement into a single directive to reduce redundancy.

Consider extracting the scratchpad and PR-description templates into a references file so SKILL.md stays a lean overview pointing one level deep.

DimensionReasoningScore

Conciseness

Dense and instructional, assuming Claude's knowledge of git and PRs without padding; minor redundancy in the Changesets section (e.g. restating 'scope the message to that PR's changes only' with an explanatory sentence) keeps it just below the lean anchor-5.

4 / 5

Actionability

Provides copy-paste-ready commands throughout — 'git branch backup/original-large-pr', 'git checkout backup/original-large-pr -- path/to/file', 'git restore -p --source backup/original-large-pr -- path/to/file', 'git range-diff', 'pnpm changeset -s -m "..."' — plus complete PR-description and scratchpad templates covering the common cases.

5 / 5

Workflow Clarity

An 8-step sequenced workflow with explicit verification (step 6: build/typecheck/lint/tests) and range-diff checks (step 8), plus a scratchpad checklist; however the validate→fix→retry feedback loop is implied rather than spelled out, and for a destructive history-rewriting skill that minor gap keeps it below anchor 5.

4 / 5

Progressive Disclosure

No bundle files exist, so all content lives inline in SKILL.md, but it is well-organized into clearly headed sections (Required workflow, PR description pattern, Scratchpad template, Changesets, Common failure modes, Default output) with no nested references; good structure with minor organization gaps rather than the clear one-level-deep reference split of anchor 5.

4 / 5

Total

17

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, trigger-rich description that names a distinct niche and many concrete actions with natural synonyms. Its only weakness is that the 'what' is folded into the 'when' clauses rather than stated as a separate capability sentence.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'breaking a large... PR into multiple smaller PRs', 'planning stacked PRs', 'extracting independent changes', 'splitting mixed refactor and behavior changes', 'managing drift', 'rebasing follow-up PRs', 'preserving original branch intent' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicit 'Use when...' trigger guidance answers 'when' thoroughly, and the 'what' is conveyed through the action verbs in each clause, but the 'what' is not stated as a standalone clause separate from the triggers, so it falls just below the anchor-5 example that separates both.

4 / 5

Trigger Term Quality

Uses natural terms a user would say — 'pull request', 'PR', 'stacked PRs', 'refactor', 'review feedback', 'rebase', 'follow-up PRs' — including the PR/pull request synonym pair, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (PR splitting / stacked PR management) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mastra-ai/mastra
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.