CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review-and-quality

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

Quality

79%

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/code-review-and-quality/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.

A highly actionable, well-sequenced review playbook whose main costs are length and redundancy — the five axes are effectively presented twice and several policy-essay sections dilute the core workflow. It also leans on unbundled external skill references, leaving its progressive disclosure structure incomplete.

Suggestions

Cut or merge the 'Review Speed', 'Honesty in Review', 'Handling Disagreements', and 'Common Rationalizations' sections, and deduplicate the five-axis checklist against the detailed axis sections — the body could shrink by a third without losing guidance.

Move the review checklist template, change-sizing deep dive, and dependency-discipline checklist into a references/ file (e.g. references/checklist.md) and link to it from a short overview, so SKILL.md serves as the hub.

Resolve the dangling references: either bundle the referenced 'security-and-hardening' and 'performance-optimization' material or reword the pointers so it is clear they are external skills, and remove the 'Local checklist coverage' stub.

DimensionReasoningScore

Conciseness

The core five-axis guidance and severity-label table are dense and valuable, but the ~380-line body includes several sections that could be trimmed or cut: 'Review Speed', 'Honesty in Review', 'Handling Disagreements', the 'Multi-Model Review Pattern' ASCII diagram, the 'Common Rationalizations' table, and a full review checklist that repeats the five axes already detailed above. This fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened'); it is above anchor 2 because the majority of sections deliver non-obvious, project-specific judgment rather than padding.

3 / 5

Actionability

Guidance is concretely executable throughout: a copy-paste review checklist template, a severity-prefix table with author actions, numeric change-size thresholds, a splitting-strategy table, a ready-to-use DEAD CODE report format, and an example review-agent prompt. Per the rubric's scoring note for instruction-only skills, the absence of code is not penalized when guidance is this actionable; it matches anchor 5's 'specific examples cover the common cases'.

5 / 5

Workflow Clarity

The Review Process is a clear five-step sequence (understand context → review tests first → implementation → categorize findings by severity → verify the verification) plus a final Verification checklist, matching anchor 4's 'clear sequence with most checkpoints present'. It falls short of anchor 5 because there is no explicit feedback loop for the review cycle itself (e.g., how re-review after author changes is triggered or when rounds converge), though the destructive/batch cap does not apply since this is not a destructive operation.

4 / 5

Progressive Disclosure

The body is well-sectioned internally but is a single ~380-line file whose checklist template and deep-dive guidance (change sizing, dependency discipline) could live in separate reference files. The inline pointers 'see `security-and-hardening`' and 'see `performance-optimization`' reference skills that are not bundled (no references/ directory exists), and the 'Local checklist coverage' section acknowledges the missing upstream checklists — references present but not backed by real files. This fits anchor 3 ('some structure but could be better organized; content that should be separate is inline').

3 / 5

Total

15

/

20

Passed

Description

78%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 and explicitly states both capability and multiple concrete trigger conditions in third person. Its main weakness is that the 'what' stays at the level of 'multi-axis code review' without naming the axes or specific review activities, which slightly limits specificity and keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — 'Conducts multi-axis code review' and 'assess code quality across multiple dimensions' — but never enumerates the axes (correctness, security, performance, etc.) or any concrete review activities. This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'); it is above anchor 2 because the action is stated concretely rather than generically, but below anchor 4 because no list of specific actions is given.

3 / 5

Completeness

Both parts are explicitly answered: the 'what' ('Conducts multi-axis code review... assess code quality across multiple dimensions') and a very explicit 'when' with three concrete trigger clauses ('Use before merging any change', 'Use when reviewing code written by yourself, another agent, or a human', 'Use when you need to assess code quality... before it enters the main branch'). This matches anchor 5; it exceeds anchor 4 because the 'when' could not meaningfully be more explicit or specific.

5 / 5

Trigger Term Quality

Natural phrases users would say are well covered: 'code review', 'reviewing code written by yourself, another agent, or a human', 'before merging any change', and 'assess code quality'. This fits anchor 4 ('good keyword coverage; a few natural terms missing') — common variations like 'PR', 'pull request', or 'LGTM' are absent, keeping it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The pre-merge review niche with author-agnostic triggers ('yourself, another agent, or a human') is mostly distinct, fitting anchor 4. It is not anchor 5 because 'code review'/'code quality' has minor overlap risk with closely related skills such as dedicated security-review or PR-review skills.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/code-review-and-quality/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.