code-reviewer
tessl i github:alirezarezvani/claude-skills --skill code-reviewerComprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go. Includes automated code analysis, best practice checking, security scanning, and review checklist generation. Use when reviewing pull requests, providing code feedback, identifying issues, or ensuring code quality standards.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill is a template-like shell with almost no actionable content for code review. It lists generic capabilities and vague feature descriptions without providing concrete guidance on how to actually review code, what to look for, or how to use the referenced scripts effectively. The content reads like marketing copy rather than executable instructions.
Suggestions
Replace generic script descriptions with actual usage examples showing real inputs and expected outputs (e.g., 'python scripts/pr_analyzer.py ./src --check-security' with sample output)
Add concrete code review examples: show a code snippet, identify specific issues, and demonstrate the expected review feedback format
Define a clear review workflow with specific steps: 1) Run static analysis, 2) Check for X issues, 3) Verify Y criteria, with explicit validation checkpoints
Remove all generic filler content ('Expert-level automation', 'Best practices built-in') and replace with specific, actionable guidance for each supported language
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic filler content that adds no value. Phrases like 'Automated tool for pr analyzer tasks' and 'Expert-level automation' are meaningless padding. The skill explains obvious concepts and includes boilerplate that Claude doesn't need. | 1 / 3 |
Actionability | Almost entirely vague and abstract. Script usages show generic placeholders like '[options]' and '[arguments]' without explaining what they actually do. No concrete examples of actual code review feedback, no real command outputs, no executable guidance for performing reviews. | 1 / 3 |
Workflow Clarity | No clear workflow for actually conducting a code review. Steps like 'Review recommendations' and 'Apply fixes' are vague. Missing validation checkpoints, no feedback loops for iterating on review findings, and no concrete sequence for the review process itself. | 1 / 3 |
Progressive Disclosure | References external files appropriately (references/*.md, scripts/), but the main content is bloated with generic information that should either be removed or moved to reference files. The structure exists but content organization is poor. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
92%This is a strong skill description that clearly articulates capabilities across multiple languages with specific actions and includes an explicit 'Use when...' clause. The main weakness is potential overlap with other code-related skills, though the focus on review workflows (PRs, checklists) provides reasonable differentiation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automated code analysis, best practice checking, security scanning, and review checklist generation' along with specific languages supported (TypeScript, JavaScript, Python, Swift, Kotlin, Go). | 3 / 3 |
Completeness | Clearly answers both what (code analysis, best practice checking, security scanning, checklist generation) AND when with explicit 'Use when...' clause covering reviewing PRs, providing feedback, identifying issues, and ensuring quality standards. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'pull requests', 'code feedback', 'code review', 'code quality', 'issues'. Also lists specific language names which are common trigger terms. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies code review context, terms like 'code quality' and 'best practices' could overlap with general coding assistance skills or linting skills. The specific mention of 'pull requests' and 'review checklist generation' helps but doesn't fully distinguish it. | 2 / 3 |
Total | 11 / 12 Passed |
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.