CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review

Use when reviewing a PR/MR by URL or the local working-tree diff — runs multi-perspective parallel agents (bug scanner, CLAUDE.md compliance, test coverage, plan alignment, git history, sibling MR/epic coherence) with confidence scoring and optional draft inline comments on the MR. Triggers for `/devflow:review` or any "review this PR/MR" request.

Quality

82%

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 review in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

Quality

Content

66%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 a well-sequenced, highly actionable review workflow with strong validation checkpoints and fallback handling. Its two real weaknesses are duplicated rule statements that pad the token budget and a progressive-disclosure structure whose referenced sibling files (AGENTS.md, TEMPLATES.md, requirements.json) do not exist in the bundle, leaving Phases 2–5 unable to execute as shipped.

Suggestions

Ship the referenced sibling files (AGENTS.md, TEMPLATES.md, requirements.json) alongside SKILL.md — or inline their essential content — because in the current bundle every deferred reference is missing, so Phase 2 agent definitions, the Phase 3 scoring rubric, and the Phase 4/5 templates cannot be loaded.

Deduplicate the repeated rules: pagination, never-re-flag, the Source-of-Truth hierarchy, and never-local-diff each appear both inline in their phase and again in 'Important rules' — state each once and cross-reference it to save tokens.

Include the exact gh api PENDING-review and glab api draft-note calls inline (or verify TEMPLATES.md is present), since Phase 5's executable guidance currently resolves to a file that is not in the bundle.

DimensionReasoningScore

Conciseness

The body is dense and operational with almost no explanation of concepts Claude already knows, but four rules are each stated twice — pagination ('Always paginate' restates Phase 1e), the never-re-flag rule (explained in Phase 1e, Phase 3, and Important rules), the Source-of-Truth hierarchy (Phase 1d and Important rules), and the never-local-diff rule (Phase 1b and Important rules). That repetition plus asides like 'This is the single biggest source of review-noise reduction' fits 'mostly efficient but could be tightened' rather than the minor-trimming anchor at 4.

3 / 5

Actionability

Concrete copy-paste-ready commands throughout (gh pr diff/view, glab api --paginate with exact endpoints, git diff HEAD, specific MCP tool names like getJiraIssueRemoteIssueLinks), but fully executable coverage is undercut because the exact Phase 5 PENDING-review API calls and the finding rubric are delegated to TEMPLATES.md, which is not present in the bundle. This is 'mostly executable guidance with minor gaps' rather than fully copy-paste-ready.

4 / 5

Workflow Clarity

The pipeline is explicitly sequenced (Preflight → Input → Phase 0 mode detection → Phases 1–6) with a mode-detection decision table, preflight STOP/AskUserQuestion fallback rules including non-interactive defaults, per-agent context packets, a mandatory cross-check status taxonomy with fix-verification, and PENDING-state confirmation before any MR comments are posted. These are clear validation steps, feedback loops, and error-recovery paths, matching the top anchor.

5 / 5

Progressive Disclosure

The design intent is good — agent definitions, scoring rubric, output template, and API calls are deferred one level deep and clearly signaled ('Read AGENTS.md (sibling to this SKILL.md)', 'Read TEMPLATES.md (sibling)') — but the bundle contains only SKILL.md: no references/, scripts/, or assets/ directories, and AGENTS.md, TEMPLATES.md, requirements.json, and the cited docs/plans design doc are all absent. Every deferred reference is dangling, so the navigation collapses at runtime; this falls below the 'references present but not clearly signaled' anchor at 3.

2 / 5

Total

14

/

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 strong description that clearly answers both what the skill does and when to use it, with concrete capabilities and explicit trigger guidance. Its only weaknesses are a few missing natural trigger variations and some overlap risk with generic code-review skills.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'bug scanner, CLAUDE.md compliance, test coverage, plan alignment, git history, sibling MR/epic coherence', 'confidence scoring', 'optional draft inline comments on the MR' — comprehensively covering the skill's capabilities, matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Both 'what' (multi-perspective parallel agents with the six named review perspectives, confidence scoring, optional draft inline comments) and 'when' ('Use when reviewing a PR/MR by URL or the local working-tree diff', 'Triggers for /devflow:review or any "review this PR/MR" request') are explicitly stated with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural terms like 'reviewing a PR/MR by URL', 'local working-tree diff', and the quoted phrase 'review this PR/MR' cover the main phrasings, but common variations such as 'code review', 'review my changes', or the spelled-out 'pull request'/'merge request' are missing. It sits between good coverage (4) and comprehensive synonym coverage (5), noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

The multi-agent perspective set, epic/sibling-MR coherence, and confidence scoring give it a distinct niche, but the generic trigger phrase 'review this PR/MR' overlaps closely related general code-review skills, keeping it at 'mostly distinct; minor overlap risk' rather than the minimal-conflict anchor at 5.

4 / 5

Total

18

/

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

AndreJorgeLopes/devflow

Path

devflow-plugin/flows/review/skills/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.