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.

72

Quality

90%

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

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 with clear sequencing, validation feedback loops, and disciplined progressive disclosure via real reference files. The only weakness is minor redundancy between the description, 'When to use', and the Routing table.

Suggestions

Remove the redundant reference listing: either drop the Routing table or drop the inline 'Read references/X.md' lines, keeping one consistent navigation path.

Trim the 'When to use' bullet list since the same triggers already appear in the frontmatter description.

DimensionReasoningScore

Conciseness

The body is largely lean and command-driven, but the 'When to use' section re-states description triggers and the Routing table duplicates reference pointers already cited inline in each phase — minor trimming opportunities.

4 / 5

Actionability

Provides copy-paste-ready, executable commands for every operational step (gh issue create, git worktree add, git commit, gh pr create, gh pr checks, npm run build/test), with sensible placeholders for variable parts.

5 / 5

Workflow Clarity

Five phases are clearly sequenced with explicit validation checkpoints (local build+test, user confirmation before issues, CI checks) and a feedback loop ('If CI fails, re-enter the worktree, fix, and push again'), plus a closing self-check checklist — satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

The body is an overview that points to seven real, one-level-deep reference files (all verified present in references/), signaled both inline per phase and in a Routing table, keeping detail out of SKILL.md while remaining easy to navigate.

5 / 5

Total

19

/

20

Passed

Description

88%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, third-person description that clearly states a multi-step pipeline and provides explicit, natural trigger guidance. It is highly specific and complete, with only minor gaps in synonym coverage and sibling-skill disambiguation.

Suggestions

Add a few more natural synonyms (e.g. 'code quality check', 'lint pass', 'tech debt sweep') to broaden trigger-term coverage.

Consider a brief disambiguating phrase in the description to separate it from adjacent skills like pr-review-fix or systematic-debugging.

DimensionReasoningScore

Specificity

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

5 / 5

Completeness

Explicitly answers both 'what' (the full review→issue→worktree→PR pipeline) and 'when' via a clear 'Use this skill when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'audit the codebase', 'comprehensive code review', 'find and fix security/quality/reliability issues', and 'proactive health check' are present, but a few common synonyms (e.g. 'lint', 'tech debt', 'code quality check') are missing.

4 / 5

Distinctiveness Conflict Risk

The end-to-end audit-to-PR pipeline carves a clear niche, but the description does not explicitly disambiguate from closely related sibling skills (e.g. systematic-debugging, pr-review-fix), leaving minor overlap risk.

4 / 5

Total

18

/

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.