mikeparcewski/wicked-garden-search-codebase-narrator
skills/search/codebase-narrator/SKILL.md
Narrate codebase structure and architecture for orientation — directory layout, key modules, data flows, technical decisions, and code health. A query + synthesis capability rather than a persistent role; produces a guided reading order and flags gotchas for newcomers. Use when: "give me an architecture walkthrough", "narrate this codebase", "explain how this project is organized", "code navigation", "where should I start reading".
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-search-codebase-narratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 13, 2026, 8:06 AM251.0s2 files scanned
SKILL.md
- # Search domain convention:
- the consolidated wicked-garden-search skill (../SKILL.md)
- name:
- wicked-garden-search-codebase-narrator
- description:
- |
- Use when:
- give me an architecture walkthrough", "narrate this codebase",
- phase_relevance:
- ["*"]
- archetype_relevance:
- ["*"]
Codebase Narrator
Analyzes a codebase and produces a narrative — not a file list, but a story of how the project is organized, why things are where they are, what to read first, and what the non-obvious gotchas are. Works on any language or stack.
Quick Start
Invoke this skill when a human (or a subagent) needs orientation on an unfamiliar codebase. Typical outputs:
- Big-picture summary (what this project does and how it's built)
- Directory map with annotations
- Key modules with responsibilities, dependencies, dependents
- Data flow ASCII diagram
- Technical-decision table
- Code-health signals
- Reading order ("start here, then here, then here")
- Gotchas list (non-obvious patterns, common newcomer mistakes)
First Strategy: Use wicked-* Ecosystem
- Search: Use wicked-garden:search to find symbols, imports, and patterns
- Memory: Use wicked-brain:memory to recall past architecture decisions
- Native tasks: Inspect current work via TaskCreate/TaskUpdate with
metadata={event_type, chain_id, source_agent, phase}
If wicked-* tools are available, prefer them over manual grep/find.
Process
1. Scan Project Structure
# Depth-limited directory tree
find . -maxdepth 3 -type f | head -100
Or use the search index (FTS5 over indexed code):
wicked-brain:search "class |function |def |interface "
Identify:
- Language(s): primary + secondary
- Framework(s): web framework, ORM, test framework
- Build system: how the project builds
- Package manager: dependency management
2. Identify Key Modules
Find the architectural pillars:
- Entry points: main files, server startup, CLI entry
- Core domain: business logic, models, entities
- API layer: routes, controllers, endpoints
- Data layer: database models, migrations, repositories
- Infrastructure: config, deployment, CI/CD
For each module: what does it do? what does it depend on? what depends on it?
3. Trace Data Flows
User Request → API Layer → Business Logic → Data Layer → Response
↓ ↓ ↓ ↓
Validation Auth/Authz Processing Persistence
Map: happy path, error paths, async flows (background jobs, events, queues), external calls (third-party API integrations).
4. Surface Technical Decisions
Visible in the code:
- Architecture style: monolith, microservices, serverless
- Design patterns: repository, factory, observer, etc.
- Configuration approach: env vars, config files, secrets management
- Testing strategy: unit, integration, e2e coverage
5. Assess Code Health
- Complexity hotspots: large files, deep nesting
- Tech debt markers: TODO/FIXME/HACK counts
- Test coverage: test-to-code ratio
- Documentation: README quality, inline comments
- Dependency health: outdated or vulnerable deps
6. Generate Narrative
See refs/output-template.md for the full structure.
Narrative Quality
Good codebase narratives:
- Tell a story — not just a file list, but why things are where they are
- Prioritize — start with the most important modules
- Connect the dots — show how pieces relate
- Flag surprises — call out non-obvious patterns
- Guide exploration — give a reading order, not just a map
Common Pitfalls
- Listing every file without explaining relationships
- Assuming reader knows the framework conventions
- Skipping the "why" behind architectural choices
- Ignoring test structure (tests reveal intent)
- Missing configuration and deployment patterns
See Also
- refs/output-template.md — full output format
- ../SKILL.md
blast-radiusaction — for impact analysis of specific symbols - ../SKILL.md
indexaction — build or refresh the index before diving in
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026