CtrlK
BlogDocsLog inGet started
Tessl Logo

review-local-branch

Deep code review of the branch you are standing on, before it becomes a PR. Scope is merge-base..working-tree, so it covers commits, staged and unstaged changes together. Runs the same review lanes as review-pr — implementation, verification, approach, security — against the local checkout through the sandbox CLI, and saves a draft to ~/.nx-branch-reviews/<branch>.md. Use when asked to review "this branch", "my changes", or work that is not yet on GitHub.

68

Quality

85%

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

81%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 well-structured, validation-heavy review pipeline with executable bash and explicit feedback loops throughout. Its main weaknesses are minor verbosity and reliance on the sibling review-pr skill for several critical blocks rather than bundling them.

Suggestions

Inline or bundle the Step 5 verification block and Step 7 trim list (currently delegated to review-pr) so the skill is self-contained and the security-critical shell has a single source of truth within this skill's bundle.

Tighten the Trust-model and Step-3 prose sections by converting explanatory paragraphs into bulletted guardrail rules to reclaim tokens without losing the load-bearing cautions.

Add the missing verification/proof-of-work line format inline (or in a bundled reference) so agents do not have to cross-read review-pr to satisfy Step 5's REQUIRED report opening.

DimensionReasoningScore

Conciseness

Dense and purposeful prose that assumes Claude's competence and only explains non-obvious gotchas (write-then-verify-then-move, two-dot-with-working-tree, `|| true` requirement); a few prose sections could be trimmed, keeping it just below the lean 5 anchor.

4 / 5

Actionability

Copy-paste-ready bash for scope, charter, dispatch, and cleanup plus a concrete Agent template, but Step 5's verification block and Step 7's trim are delegated to review-pr rather than inlined, leaving minor gaps versus the fully-executable 5 anchor.

4 / 5

Workflow Clarity

A clearly sequenced 7-step pipeline with explicit validation checkpoints (BASE/empty-diff guards, write-then-verify-then-move, refuse-default-branch, agent verification with retry rule, integer gate) and feedback loops for this batch/review operation.

5 / 5

Progressive Disclosure

Well-organized with clear step headers and one-level-deep delegation to the sibling review-pr skill instead of duplication, but no bundle files exist and several critical blocks live in another skill rather than being bundled, leaving a minor organization gap below the 5 anchor.

4 / 5

Total

17

/

20

Passed

Description

88%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 precise, third-person description that concretely states capabilities and gives explicit natural-language trigger conditions. Its only soft spot is trigger-term breadth and a slight overlap with the sibling review-pr skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Deep code review of the branch', covers 'commits, staged and unstaged changes', runs four named lanes (implementation, verification, approach, security), and 'saves a draft to ~/.nx-branch-reviews/<branch>.md' — comprehensive coverage matching the 5 anchor.

5 / 5

Completeness

Explicitly answers both what (deep review with named lanes over a defined scope, saving a draft) and when ('Use when asked to review "this branch", "my changes", or work that is not yet on GitHub') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers users would actually say ('this branch', 'my changes', 'work that is not yet on GitHub'), but lacks the synonym/extension breadth the 5 anchor expects; sits noticeably above the 3 anchor yet just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche (pre-PR, local, not on GitHub) with distinct triggers, but minor overlap risk with the closely related review-pr sibling skill keeps it just below the 5 anchor.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
nrwl/nx
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.