CtrlK
BlogDocsLog inGet started
Tessl Logo

codebase-audit

Perform a full codebase review, categorize findings by severity, file GitHub issues, then fix each issue in an isolated git worktree and submit PRs. Use this skill when the user asks to audit the codebase, do a comprehensive code review, find and fix security/quality/reliability issues, or run a proactive health check across the entire repository.

74

Quality

92%

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 workflow skill with clear sequencing, validation/feedback loops, and clean progressive disclosure to real reference files. Minor conciseness gains are available by trimming the self-check list and deduplicating commit conventions.

Suggestions

Deduplicate commit convention guidance: it appears in Phase 4 step (e) and again in the standalone 'Commit conventions' section — keep it in one place and reference it.

Consider trimming the 'Minimum self-check' list to the highest-value checks, or move it into references/verification.md to keep the overview leaner.

Replace the dependency-scan prose in Phase 1 with a one-line pointer to references/dependency-audit.md, matching the routing pattern used elsewhere.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with no concept explanations Claude already knows, but the self-check list and the separate 'Commit conventions' section (which repeats Phase 4 content) introduce minor redundancy.

4 / 5

Actionability

Provides concrete, executable commands throughout — 'gh issue create --title ...', 'git worktree add ...', 'npm run build && npm run test', 'gh pr create ...', 'gh pr checks' — with concrete scope examples covering the common cases.

5 / 5

Workflow Clarity

Five phases are clearly sequenced with explicit validation checkpoints ('Verify locally: npm run build && npm run test', 'wait for confirmation before proceeding') and a feedback loop in Phase 5 (re-enter worktree if CI fails), appropriate for batch/destructive operations.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview pointing to seven one-level-deep reference files, all of which exist in ./references/, signaled both inline ('Read references/X.md') and via a routing table for easy navigation.

5 / 5

Total

19

/

20

Passed

Description

92%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, concrete description that covers both capabilities and explicit usage triggers for a multi-phase audit pipeline. Slight room to add more synonym-level trigger terms, but overall highly actionable and distinct.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Perform a full codebase review, categorize findings by severity, file GitHub issues, then fix each issue in an isolated git worktree and submit PRs' — giving comprehensive coverage of the pipeline.

5 / 5

Completeness

Clearly states what the skill does (review → classify → file issues → worktree fix → PRs) and explicitly when to use it via 'Use this skill when the user asks to audit the codebase...' with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like 'audit the codebase', 'comprehensive code review', 'find and fix security/quality/reliability issues', and 'proactive health check' are strong, but a few common variations/synonyms a user might say are absent.

4 / 5

Distinctiveness Conflict Risk

The end-to-end audit→issue→worktree→PR niche is distinctive with minimal conflict risk; the body also explicitly routes away from overlapping skills (systematic-debugging, pr-review-fix, mcp-attribution-worktree).

5 / 5

Total

19

/

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.

Validation15 / 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
TencentCloudBase/CloudBase-AI-Toolkit
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.