What problem does it solve? Teams adopting AI-agent-friendly repository structures need a way to measure how compliant an existing repo is and detect drift over time, without risking unintended file changes during the audit. ## Core Features & Use Cases - Read-only compliance scan: Runs aidlc-cli.mjs scan against a target path and reports an 18-item table with status, evidence, and reason for each item, plus an overall percentage. - Profile-aware scoring: When .codepresso/state/aidlc-profile.json exists, it passes the profile so items are scored honestly against the team's actual tools and host instead of a generic baseline. - Gap explanation and secrets surfacing: Explains functional scoring nuances (e.g., a pre-push script not wired to a git hook scores partial), flags detected secrets in masked form with rotation advice, and marks items requiring manual setup. - Use Case: After scaffolding a repo with aidlc-init, re-run this skill monthly to check whether CI workflows, code indexes, or hooks have drifted out of compliance. ## Quick Start Ask the AI to run /codepresso:aidlc-doctor on your repository path to see its AI-native compliance score and missing items.
