infra-audit

To map project infrastructure, scan orchestration files, env variables, and ORM configs to discover external systems and connection methods. This identifies missing layers like cache or queues by tracing code evidence, producing a structured manifest for infrastructure planning.

An infrastructure manifest is a structured document detailing system type, product, config path, connection method, and access patterns. It includes an ASCII connection graph and evidence-linked opportunities for remediation, written to .planning/infra-manifest.md without exposing secret values.

Trace connection strings and client initialization sites by scanning source files and common client libraries. This attributes external systems to specific services and builds an ASCII connection graph, revealing access patterns and infrastructure dependencies without relying on documentation.

Yes, you can detect missing infrastructure layers by analyzing access patterns and scanning for common client libraries. It flags missing layers such as cache, queue, search, or object storage only when supported by concrete code evidence found during the scan.

No, the infrastructure audit scans env files to identify external systems and connection methods but explicitly excludes secret values. It produces a manifest with config paths and access patterns while ensuring sensitive data is never included in the output.

Scan docker-compose and ORM configs during project onboarding or when planning infrastructure changes. This discovers orchestration setups, external systems, and client initialization sites, helping teams understand existing infrastructure and identify missing layers without relying on memory.