Agent skill
deep-analyze
Deep codebase analysis that extracts learnings from documentation. Creates context entries and learnings from docs/ with pattern matching.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/deep-analyze-paxtone-io-openkodo
SKILL.md
Deep Analyze
Extract full content and learnings from your documentation.
What It Does
Runs kodo analyze --deep --auto which:
- Standard Analysis - All normal analyzers (tech-stack, architecture, etc.)
- Content Extraction - Parses all
.mdfiles indocs/ - Learning Extraction - Finds patterns:
- Rules: "always/never/must" statements
- Decisions: "we chose X because..."
- Tech Stack: "uses X for..."
- Workflows: step sequences
- Domain: entity definitions
- Conventions: naming patterns
Output
.kodo/context-tree/- Context entries with YAML frontmatter.kodo/learnings/- Learnings grouped by category:rules.mddecisions.mdtech-stack.mdworkflows.mddomain.mdconventions.md
Confidence Levels
- HIGH - Your design docs (
docs/plans/) - MEDIUM - Inherited/pre-existing documentation
Usage
Just invoke this skill - it runs automatically:
# This skill runs:
kodo analyze --deep --auto
When to Use
- Starting a new project with existing docs
- After writing design documents
- When onboarding to capture institutional knowledge
- Before major refactoring to preserve context
Single File Extraction
For extracting from a single file:
kodo extract docs/plans/your-design.md
# or
kodo x docs/plans/your-design.md
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?