Systematically analyze codebase structure, complexity, dependencies, and architectural patterns to understand project organization
SkillScore68Maintained
Automatic
◆Coding packanalysiscode-qualityarchitecture
Last verified 9/2/2026
What it changes
Passed 14 of 21 test cases with the skill, and 11 of 21 without it.
Without skill50%
With skill68%
Checks it passed that the model alone missed
The response lists Phase 1 as Structure Discovery.
The response constrains the grep search using --include="*.cs".
The response includes determining existing domain entities and their relationships.
and 3 more in the full report
4 fixed11 passed either way7 still failing0 broke
Pass-rate lift
+18 pp
Tokens
+46%
Agent turns
0%
Response time
+12%
Model gemini-3.6-flashMeasured 9/2/2026v315 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
How can I scan a .NET backend repository for built-in validation attributes like Required, Range, and StringLength using standard command-line tools without picking up unrelated text files?
What was checked, without and with the skill
Checked
Without skill
With skill
The response includes a grep command searching for .NET DataAnnotations validation attributes.
Passed
Passed
The response constrains the grep search using --include="*.cs".
Missed
Passed
case-07 · gemini-3.6-flash · 9/2/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md266 linessingle file
Codebase Analysis Skill
Overview
This skill provides techniques for extracting business requirements, domain knowledge, and technical specifications from existing codebases.
Analysis Objectives
When analyzing a codebase, seek to understand:
Domain Model: Core entities and their relationships
Business Rules: Validation, calculations, workflows
Integrations: External systems and data flows
User Capabilities: What users can do in the system
Technical Constraints: Architecture patterns and limitations