CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-sweep

Sweep open (or listed) PRs with up to 100 parallel agents: security-scan outside contributors, rebase onto main when behind (push --force-with-lease), approve pending first-time-contributor CI when relevant, optionally rebase in-house PRs, and report who should review. Supports full, changed-only, behind-only, and conflict-only scopes for cheap daily runs. Use when the user runs /pr-sweep (or /pr-inbound-sweep), or asks to "sweep PRs", "sweep inbound PRs", "security-check outside PRs", "rebase outsider PRs", "rebase our PRs", "approve waiting CI on PRs", "daily PR sweep", or "prep external PRs for review".

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is pr-sweep in TanStack/ai

SKILL.md
Quality
Evals
Security

Quality

Content

88%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-sequenced operational skill with real commands, explicit safety gates, and verification loops for destructive/batch operations. Its weaknesses are mild: some rule repetition across sections and a monolithic ~390-line body where the embedded prompt templates and snapshot schema could live in reference files.

Suggestions

Consolidate the apply-consent rule ('--apply is consent, do not wait for a second yes') into a single authoritative location (e.g., Safety rule 9) and reference it from Modes and §5 instead of restating it.

Move the per-PR agent prompt template and the apply-mode child prompt into files under references/ (e.g., references/agent-prompt.md) and point to them, trimming SKILL.md toward an overview.

Consider moving the full snapshot.json example into a reference file and keeping only the path and key fields (headSha, sweptAt, security, mergeStateStatus) inline.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — real commands and JSON schemas with almost no explanation of known concepts — but the apply-consent rule is stated three times (Modes, Safety rule 9, §5 intro) and push-verification steps are repeated in Safety rule 11, §5b, and the apply child prompt, which could be consolidated.

4 / 5

Actionability

Fully executable throughout: copy-paste-ready gh/git commands, complete JSON return schemas for subagents, and fully embedded per-PR and apply-mode child prompt templates, covering the common cases (forks, 403s, conflicts).

5 / 5

Workflow Clarity

The procedure is clearly sequenced (resolve repo → list → fan-out → report → apply → final report) with explicit validation checkpoints for risky batch mutations: security gate before any mutation, BEFORE/AFTER head-SHA push verification, rebase abort rules, snapshot diffing, and explicit failure handling (push-403, blocked-conflicts).

5 / 5

Progressive Disclosure

Good structure with a clear, one-level-deep reference ('Security heuristics: [references/security-checklist.md]', which exists and is also pointed to from the agent instructions), but at ~390 lines the body inlines material — the snapshot JSON example, per-PR agent prompt template, and apply child prompt — that could be split into reference files to keep SKILL.md a leaner overview.

4 / 5

Total

18

/

20

Passed

Description

100%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.

The description is specific, complete, and trigger-rich: concrete capabilities are stated in third person, the 'Use when' clause enumerates natural user phrasings plus slash commands, and the PR-sweep niche is clearly distinguishable. It matches the rubric's good overall examples in structure and quality.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'security-scan outside contributors, rebase onto main when behind (push --force-with-lease), approve pending first-time-contributor CI when relevant, optionally rebase in-house PRs, and report who should review' — plus concrete scope variants ('full, changed-only, behind-only, and conflict-only'), giving comprehensive coverage with no vague filler.

5 / 5

Completeness

It explicitly answers both 'what' (sweep/security-scan/rebase/approve/report) and 'when' with an explicit 'Use when the user runs /pr-sweep… or asks to…' clause followed by concrete trigger phrases, exactly matching the top anchor's example structure.

5 / 5

Trigger Term Quality

It covers natural trigger phrases users would actually say ('sweep PRs', 'sweep inbound PRs', 'rebase outsider PRs', 'approve waiting CI on PRs', 'daily PR sweep', 'prep external PRs for review') plus slash-command invocations (/pr-sweep, /pr-inbound-sweep), matching the anchor's comprehensiveness including synonyms.

5 / 5

Distinctiveness Conflict Risk

'Sweep PRs' with force-with-lease rebase, CI-workflow approval, and outside-contributor security scanning is a clear niche with distinct triggers; the named phrases (e.g., 'approve waiting CI on PRs', 'daily PR sweep') are unlikely to fire for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
TanStack/ai
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.