CtrlK
BlogDocsLog inGet started
Tessl Logo

java-code-review

Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests. By default review files modified in git; when the user explicitly names files, classes, packages, or a diff, review that scope instead. Generate a detailed review.md report with actionable comments and fixes.

71

Quality

86%

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

92%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, actionable review workflow with explicit validation and a concrete output spec. The main opportunity is light trimming of the report template block.

Suggestions

Tighten the report template block by folding the inline comments into shorter placeholders to reduce token weight.

Consider a one-line inline example of a finding entry to anchor the template without adding length.

DimensionReasoningScore

Conciseness

Lean, assumes Claude's competence (no explanation of what Java or bugs are), and every section earns its place; only minor spots in the report template block could be tightened.

4 / 5

Actionability

Concrete git commands ('git status --short', 'git diff'), an exact report structure with required sections, and defined severity levels make the instruction-only guidance fully executable.

5 / 5

Workflow Clarity

A clear sequence (scope -> review -> validate -> write report -> final response) with explicit validation checkpoints and an overwrite/new-filename feedback loop before writing.

5 / 5

Progressive Disclosure

No bundle files exist; the single self-contained SKILL.md is well-organized with clear section headers and needs no external references, satisfying the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

80%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 specific, well-scoped description that names concrete review actions and a clear output artifact. It would benefit from an explicit 'Use when...' trigger clause and a few more natural synonyms.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to review Java code, a Java diff, or for bugs/duplicate code in Java files.'

Include a few natural synonyms users say ('code review', 'lint', 'refactor') to broaden trigger coverage.

Make the invocation 'when' distinct from the scoping 'when' so the trigger condition is unambiguous.

DimensionReasoningScore

Specificity

Lists multiple concrete review actions — 'bugs, duplicate code, correctness risks, maintainability improvements, and missing tests' — plus 'Generate a detailed review.md report', giving comprehensive coverage rather than a single generic verb.

5 / 5

Completeness

The 'what' is explicit and concrete; a 'when' is present only via scoping language ('when the user explicitly names files...') rather than an explicit 'Use when...' trigger phrase, so it could be more explicit.

4 / 5

Trigger Term Quality

Natural terms like 'Java code', 'bugs', 'duplicate code', 'diff', 'git', and 'classes, packages' are present, but common synonyms a user might say (e.g., 'code review', 'lint', 'refactor') are missing.

4 / 5

Distinctiveness Conflict Risk

The Java-specific niche and review-focused triggers make it mostly distinct, but there is minor overlap risk with a general code-review skill.

4 / 5

Total

17

/

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
sivaprasadreddy/sivalabs-agent-skills
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.