CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gitnexus-pr-swarm-review

Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/gitnexus-pr-swarm-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 admirably lean orchestration adapter with an explicit lane sequence and a hard validation gate, and it wastes no tokens. Its main weakness is that the canonical spec it depends on — pr-swarm-review/orchestration.md and the personas directory — is not present in the provided bundle, leaving the bulk of the executable detail unreachable from this file.

Suggestions

Ship the referenced canonical spec inside the skill bundle (e.g. under references/ or as pr-swarm-review/orchestration.md) so 'read it now and follow it' resolves to a real file, or inline the minimal lane definitions needed to run a review if the spec must stay external.

Include the persona filenames or lane names inline (even just a one-line list of lanes 1–7) so a reader can verify the swarm structure without the external file.

Add a fallback instruction for when orchestration.md or the gitnexus-* project agents are missing, so the skill fails gracefully instead of dead-ending.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and imperative with zero padding: 'Run in Swarm mode. Dispatch each lane as its own subagent via the Agent tool.' It assumes Claude's competence throughout — no explanation of what a PR review is, what a subagent is, or why orchestration matters. It matches the anchor 'lean and efficient; assumes Claude's competence; every token earns its place'; even the blockquote distinguishing the CI skill carries real, non-redundant information.

5 / 5

Actionability

There is genuinely concrete guidance — the invocation '/gitnexus-pr-swarm-review <PR URL or PR number>', 'the seven subagents are the project agents named gitnexus-*', 'Run lanes 1–2 first, lanes 3–6 in parallel after, and lane 7 last' — but the operative content (the full review contract: lanes, classifications, finding format, hidden-Unicode checks) lives in 'pr-swarm-review/orchestration.md', which is not present in this skill's bundle (no references/, scripts/, or assets/ directories exist, and no pr-swarm-review/ directory is shipped). So the key execution details are unreachable from what is provided, matching the anchor 'some concrete guidance but incomplete; missing key details'. It is not score 4 because the missing spec is the majority of the executable guidance, not a minor gap.

3 / 5

Workflow Clarity

The sequence is explicit — 'Run lanes 1–2 first, lanes 3–6 in parallel after, and lane 7 last on the draft' — and it includes a real validation checkpoint with a feedback loop: 'Lane 7 is a hard gate. Do not emit the final review while the synthesis critic's "Required corrections before posting" section is non-empty — revise and re-run it.' This matches anchor 4 ('clear sequence with most checkpoints present; minor validation gaps'). It is not score 5 because the per-lane steps themselves are delegated to the absent orchestration.md, so the checkpoints within lanes 1–6 are not visible here; it is above anchor 3 because an explicit gate-and-retry loop is stated rather than merely implied.

4 / 5

Progressive Disclosure

The split is conceptually right — an adapter that pins Claude Code specifics while pointing to a canonical spec ('pr-swarm-review/orchestration.md — read it now and follow it', personas under 'pr-swarm-review/personas/') — and the references are clearly signaled and one level deep. However, no bundle files are provided: the referenced orchestration.md and personas/ directory do not exist in this skill's directory, so navigation dead-ends and the disclosure structure cannot actually be followed. That lands between anchor 3 ('some structure but could be better organized; references present but...') and anchor 4; the clearly signaled but unresolved references keep it from scoring 4.

3 / 5

Total

15

/

20

Passed

Description

53%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 concise, specific about the domain, and clearly distinct thanks to the GitNexus qualifier, but it answers only 'what' and leaves 'when' entirely unanswered. Adding an explicit trigger clause with natural user phrasings (PR review, production readiness, merge readiness) would lift it substantially.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when asked to review a GitNexus pull request, assess production readiness, or gate a merge on review sign-off.'

Include natural trigger synonyms users would actually say — 'PR', 'pull request', 'code review', 'production readiness' — rather than only the compound phrase 'production-readiness pull request review'.

Name the concrete output (e.g., 'produces a production-readiness review report with lane findings and a synthesis') so the 'what' is comprehensive, not a single action.

DimensionReasoningScore

Specificity

The description names a concrete domain and exactly one concrete action — "Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm" — which matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive'. It is not score 2 because the action and domain are specific rather than generic ('Processes PDF files'), and not score 4 because no additional specific actions or output details (e.g., what the review produces) are listed.

3 / 5

Completeness

The 'what' is clear — run a production-readiness PR review via a coordinated reviewer swarm — but there is no 'when' clause at all (no "Use when..." or equivalent trigger guidance), which caps completeness at 3 per the judging guidelines. It is not score 4 because 'when' is entirely absent rather than merely imprecise, and not score 2 because the 'what' is specific and well-stated.

3 / 5

Trigger Term Quality

Relevant keywords exist — "pull request review", "production-readiness", "GitNexus" — but common natural variations are missing: users would say "PR", "review this PR", "code review", or "is this ready to merge". It is above anchor 2 (which requires only generic keywords) but below anchor 4, which expects good coverage of the natural terms users actually say.

3 / 5

Distinctiveness Conflict Risk

The GitNexus-specific niche with the distinctive term "production-readiness pull request review" makes it mostly distinct with minimal conflict against generic PDF/document skills. It is not score 5 because the body itself acknowledges a closely related sibling ('the CI gitnexus-review skill'), so there is minor overlap risk with that closely related skill; it is well above anchor 3 because the triggers are project-specific rather than broadly generic.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

abhigyanpatwari/GitNexus

Path

.claude/skills/gitnexus-pr-swarm-review/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.