codemaps-extractworkflow★1,091
modu-ai/moai-adk ↗What it does
Extract per-package architectural synthesis from Go codebase
Best for
Architectural review insight (coupling risk, latent contracts, layering) layered on top of deterministic go list/go doc baseline for medium-to-large codebases.
Inputs
- · list of Go package paths (via args.packages)
Outputs
- · markdown report per package with 4 sections: dependency_summary, public_surface_summary, architectural_synthesis (layer, role, fan_in_implication, domain_boundary), claims_beyond_baseline
Preconditions
- · Go codebase with readable package sources
- · packages list injected via args
Failure modes
- · parallel agent cost only justified at high package count; scales poorly for small repos
- · non-deterministic if agents add timestamps to output
- · claims beyond baseline may be speculative or incomplete
Trust signals
- · determinism note: package list injected, no wall-clock/random in body
- · honest fallback: agents return 'NONE — reducible to baseline' if no genuine inference
- · read-only enforcement via agentType Explore