CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-code-review

Conduct high-quality, persona-driven code reviews. Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback.

Quality

71%

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 ./.agents/skills/common/common-code-review/SKILL.md

The canonical home for this skill is common-code-review in HoangNguyen0403/agent-skills-standard

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 dense, disciplined instruction skill with a concrete output contract and strong progressive disclosure from the entry file. Its main weaknesses are triple-duplicated rules across the body and reference files, an implicit phase sequence that requires assembly from principle bullets, and orphaned/broken-link bundle files.

Suggestions

Merge the overlapping 'Red Flags', 'Rationalization Prevention', and 'Anti-Patterns' sections into a single anti-patterns section — all three repeat the same no-praise / evidence-required / behavior-over-style rules.

Replace the body's duplicated deterministic-gate and finding-template text with a single pointer to references/output-format.md (the same contract currently appears verbatim in three places).

Add an explicit numbered phase sequence in the body (blind review → deterministic gate → freeze findings + SHA-256 → author claims → reconcile) instead of encoding the order inside prose principle bullets.

Link lenses.md, report.md, and request-template.md from SKILL.md or orchestration.md, and fix or remove the broken cross-skill links in lenses.md and report.md.

DimensionReasoningScore

Conciseness

The body is terse but redundant: "Red Flags", "Rationalization Prevention", and "Anti-Patterns" each repeat the same three ideas (no praise, claims need evidence, behavior over style) — e.g., praise is banned in "Findings first; no strengths or praise section", "Stop if you are praising before reviewing", and the output-format rule. The deterministic-gate and finding-template text is also duplicated almost verbatim across the body, adversarial-review.md, and output-format.md, which could be consolidated to pointers.

3 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill: exact severity tags, required finding fields ("Evidence:", "Why:", "Fix:", "Prevent-by: lint | type | test | eval | runtime | guidance | none"), named defect classes ("No N+1 queries, memory leaks", "injection, secrets, auth leaks"), and a specific three-part test-evidence gate. It falls short of 5 only because no worked finding example appears inline (it is deferred to output-format.md).

4 / 5

Workflow Clarity

The multi-phase process (blind first, deterministic gate, freeze findings and SHA-256, reconcile after author claims) is present and its checkpoints are explicit, but the sequence is embedded in dense principle bullets rather than an ordered workflow — the reader must assemble the phase order from prose, and error-recovery steps live only in the referenced adversarial-review.md. This matches the 'steps present but sequence/checkpoints implicit' anchor more than the clear-sequence 4 anchor.

3 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled, one-level-deep links to real files (adversarial-review.md, orchestration.md, checklist.md, output-format.md) plus purpose guidance for when to load each. The gap keeping it below 5: lenses.md, report.md, and request-template.md are orphaned (never linked from SKILL.md or any reference), and lenses.md and report.md contain links to non-existent cross-skill paths (../../common-security-audit/references/signals.md, ../../common-skill-creator/references/rubric.md).

4 / 5

Total

14

/

20

Passed

Description

70%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 solid description with a correct third-person voice, an explicit 'Use when' trigger clause, and natural trigger terms. Its main weakness is a generic 'what' that relies on qualifiers rather than naming the concrete review outputs (severity-tagged findings with evidence, fixes, and prevention guidance).

DimensionReasoningScore

Specificity

"Conduct high-quality, persona-driven code reviews" names the domain and the review action, and "critiquing code quality, or analyzing changes" adds near-synonymous variants rather than distinct concrete capabilities. It stops short of the several specific, differentiated actions of the 4-5 anchors (e.g., what the review produces: severity-tagged findings, evidence, fixes).

3 / 5

Completeness

Both parts are present: what ("Conduct high-quality, persona-driven code reviews") and an explicit when ("Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback"). The 'what' leans on padded qualifiers ('high-quality', 'persona-driven') instead of concrete capabilities, keeping it below the fully explicit 5 anchor.

4 / 5

Trigger Term Quality

"reviewing PRs, critiquing code quality, analyzing changes" covers natural phrases users would actually say. Common variations like "code review", "review my diff/changes", or "feedback" are missing, so it falls just short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The persona-driven, team-feedback framing carves a recognizable niche with PR-specific triggers, so it is mostly distinct from generic analysis skills. It retains minor overlap risk with closely related code-review skills since "analyzing code" is broad.

4 / 5

Total

15

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/common/common-code-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.