CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-pr

Use when asked to review and fix an open pull request this session did not write — one another tool such as Codex opened, or another session left — and bring it to merge-ready on its own branch. Covers finding and reusing the branch's existing worktree, reading what the branch would run before running it, rebasing it, only on the owner's word, and regenerating bun.lock with evidence instead of merging it, running prep-pr's review lenses on someone else's work, telling a red check main caused from one the branch caused, fixing every finding on the branch, and rewriting the body with write-pr.

Quality

91%

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

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.

The body is an exceptionally actionable, well-validated workflow: exact commands, explicit stop conditions, decision tables, and feedback loops for every risky operation. Its weaknesses are structural rather than substantive — the Traps table duplicates earlier steps, and the long single file could offload the lockfile procedure to a reference file.

Suggestions

Trim the Traps table to traps not already stated as step rules (e.g. drop the dirty-worktree and main-failure rows, which restate Steps 1 and 4) to cut duplicated tokens.

Move the Step 3 bun.lock regeneration procedure — the change/commands table and evidence-script walkthrough — into a references/ file, keeping a short pointer and the stop conditions in SKILL.md.

Condense the worktree-lifecycle rationale in Step 1 (prunable/no-line/one-line cases) into a compact table matching the style of Steps 3 and 4.

DimensionReasoningScore

Conciseness

The body is dense and operational, assumes competence, and explains only non-obvious repo-specific rationale ("a bare `bun install` drops every entry for a platform this machine is not"), but the Traps table restates roughly six rules already given in Steps 0–4 (e.g. the dirty-worktree and main-failure rules), and a few passages could be tightened. That duplication keeps it at the efficient-with-minor-trims anchor rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Guidance is copy-paste ready throughout: exact `gh api … --jq` queries, the `bun add '<pkg>@<version>' --cwd <dir>` table with precise flags, regexes for branch-name and package validation, and the evidence-script invocation pinned to main's copy. Decision tables cover the common cases (fork head, prunable worktree, flake vs branch failure), matching the fully-executable anchor.

5 / 5

Workflow Clarity

Steps 0–7 are explicitly sequenced with pervasive validation checkpoints ("must print nothing", "Stop and report", "Anything else → stop and ask the owner"), feedback loops ("A red check goes back to Step 4", "the lockfile is wrong: start this step again"), and a closing stop-and-hand-back checklist. For a risky skill (force-push, rebase, running unreviewed code) the validation coverage satisfies the top anchor rather than the minor-gaps one.

5 / 5

Progressive Disclosure

No bundle files exist, and the single body is well-sectioned with one-level-deep, clearly signaled pointers (prep-pr, write-pr, wiki/conventions/contributing.md, scripts/wait-pr.sh, scripts/lockfile-evidence.sh). However, ~230 lines of inline material — notably the full bun.lock regeneration procedure and red-check triage tables — could live in a reference file, which is the minor-organization-gaps anchor rather than the appropriately-split one.

4 / 5

Total

18

/

20

Passed

Description

92%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 explicit, dense with concrete capabilities, and cleanly separates its niche (externally-authored PRs) from related pipeline skills. Its only weakness is mild: it omits the "PR" abbreviation and a few natural phrasing variants users might say. It answers both what and when with no padding despite its length.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the entire workflow — "finding and reusing the branch's existing worktree", "reading what the branch would run before running it", "regenerating bun.lock with evidence instead of merging it", "telling a red check main caused from one the branch caused", "rewriting the body with write-pr" — with no coverage gaps, matching the comprehensive anchor rather than the minor-gaps anchor.

5 / 5

Completeness

Both halves are explicit: "Use when asked to review and fix an open pull request this session did not write" gives concrete trigger conditions for when, and "bring it to merge-ready on its own branch" plus the Covers list gives a full what. The when-clause is highly specific, so the anchor-4 caveat ("'when' could be more explicit") does not apply.

5 / 5

Trigger Term Quality

"review and fix an open pull request" is the natural user phrase and "another tool such as Codex opened, or another session left" matches how provenance is described, but the common abbreviation "PR" and variants like "someone else's PR" are absent — good coverage with a few natural terms missing, one notch below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche — taking over pull requests written outside this session — with distinct triggers ("this session did not write", "another tool such as Codex opened") that carve it apart from sibling PR-preparation skills, giving minimal conflict risk. It is not the anchor-4 case because the provenance condition removes the overlap with closely related review skills.

5 / 5

Total

19

/

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: 3 missing

Warning

Total

15

/

16

Passed

Repository

englishstreetventures/osn

Path

.claude/skills/review-pr/SKILL.md

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.