qodo-codebase-wisdom

Understand how code works, how a change was done before, and which repos are coupled — to answer a question, plan a code change, debug a regression, or scope a fix, using the qodo CLI's managed tools. Use when a task needs to understand a codebase, its history, or how its repos relate — especially for a repo you don't have checked out or work spanning repos — "how does X work", "where is X defined", "who changed X", "explain this service", "plan the change for X", "what would changing X affect", "which repos depend on X", "why did X regress / when did it break", "has this been fixed before", "how did we solve X".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%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.

The body is a highly actionable, well-sequenced operational policy with concrete commands, explicit error-recovery loops, and a well-integrated single reference file. Its main weakness is token efficiency: dense, hard-to-parse passages and some repetition (provenance flags, update-notice policy) could be tightened or offloaded to the existing references file.

Suggestions

Consolidate the provenance-flag guidance (currently shown in Quick start and restated in Configuration) into a single place, keeping only the stamped example command.

Move the peripheral skill-update notice policy and the manual-update procedure detail into the existing references/skill-updates.md, leaving a one-line pointer in the body.

Rewrite the sandbox auth diagnostic and preflight reuse rules as short checklists to cut dense multi-clause sentences like 'Reuse a successful check in the same executable/workspace/deployment and execution context'.

Dimension	Reasoning	Score
Conciseness	The ~190-line body avoids teaching known concepts, but several dense procedural passages could be tightened (e.g., 'Reuse a successful check in the same executable/workspace/deployment and execution context; request each required host approval') and provenance-flag guidance is repeated across Quick start and Configuration. This fits anchor 3 ('mostly efficient but could be tightened') better than anchor 4, where verbosity would be only minor.	3 / 5
Actionability	Fully executable commands with exact flags ('qodo read codebase grep --repo owner/repo --pattern "chargeCard" --json'), three worked examples with expected output, and a catalog-verification command ('qodo read tools <group> [<tool>] --json') that resolves the illustrative-tool-name caveat — copy-paste ready and covering the common cases.	5 / 5
Workflow Clarity	Sections are ordered as an execution flow (compatibility gate → preflight → route to a tool group → narrow then fetch → deliver) with explicit validation checkpoints (unadorned --version probe with a minimum-version gate, one-retry rules) and feedback loops ('Empty or truncated: true → narrow once and retry', 'MT-TOOL-LOOP error means stop and change approach').	5 / 5
Progressive Disclosure	One clearly signaled, one-level-deep reference ([manual-update procedure](references/skill-updates.md), verified to exist) appropriately holds the peripheral update procedure. Not anchor 5: the body is a self-contained policy document rather than an overview pointing to detailed materials, and peripheral policy (update-notice handling, the sandbox auth diagnostic) arguably belongs in references alongside it.	4 / 5
	Total	17 / 20 Passed

Description

91%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: it states concrete capabilities, scopes them to the qodo CLI's managed read tools, and provides an explicit 'Use when' clause with an extensive set of natural trigger phrases. Its only weaknesses are mildly abstract core actions and broad code-understanding triggers that could compete with general code-exploration skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete capability statements ('understand how code works', 'how a change was done before', 'which repos are coupled — to answer a question, plan a code change, debug a regression, or scope a fix'), but the core actions remain more abstract than anchor-5's fully enumerated operations, leaving minor gaps in coverage.	4 / 5
Completeness	Explicitly answers both what ('Understand how code works... using the qodo CLI's managed tools') and when ('Use when a task needs to understand a codebase, its history, or how its repos relate') with concrete trigger phrases, matching the anchor-5 example pattern exactly.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage with ten quoted user phrasings ('how does X work', 'where is X defined', 'who changed X', 'why did X regress / when did it break', 'has this been fixed before', 'how did we solve X') covering synonyms across question, planning, debugging, and scoping intents.	5 / 5
Distinctiveness Conflict Risk	Cross-repo coupling triggers ('which repos depend on X', 'work spanning repos') and the qodo CLI naming carve a distinct niche, but broad triggers like 'how does X work' and 'explain this service' create minor overlap risk with generic local code-exploration skills.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: qodo-ai/qodo-skills
Path: skills/qodo-codebase-wisdom/SKILL.md
Commit: 7f619ec

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.