ao-cyber-systems/monorepo-doctor
plugins/monorepo-standards/skills/monorepo-doctor/SKILL.md
Validate that a monorepo follows the AO Cyber Systems layout convention — root CLAUDE.md declares every area, every area has its own CLAUDE.md, no compiled binaries are tracked in git. Reads the root `CLAUDE.md` Layout table, walks the working tree, and reports drift in a single Markdown summary. Standalone — works on any repo. Triggers on: "audit monorepo layout", "monorepo doctor", "is this monorepo healthy?", "check the layout", "find binaries in the repo".
development
Updated May 12, 2026
$ install --global
skillsauthnpx skillsauth add ao-cyber-systems/devflow-claude monorepo-doctorInstall 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: May 12, 2026, 3:09 AM172.0s4 files scanned
SKILL.md
- name:
- monorepo-doctor
- description:
- |
- Triggers on:
- audit monorepo layout", "monorepo doctor", "is this monorepo healthy?", "check the layout", "find binaries in the repo".
- argument-hint:
- [--json] [--root <path>] [--no-binary-scan]
<objective>
Validate a monorepo against the standard layout:
- Root
CLAUDE.mdexists and declares its areas in a Layout table. - Every declared area exists on disk.
- Every directory on disk that looks like a monorepo area is declared (no orphans).
- Every declared area has its own
CLAUDE.md. - No compiled executables or oversize files (> 5 MB) are tracked in non-asset paths.
This is a standalone command — no .planning/ directory required.
Output: a Markdown report printed to the terminal, plus exit code 0 (clean) or 1 (issues found). </objective>
<context> Arguments: $ARGUMENTS (optional)Supported flags (pass them through verbatim):
--root <path>— audit a repo other than the cwd--json— machine-readable output instead of Markdown--no-binary-scan— skip the (slowest) binary walk
The standard AO Cyber Systems monorepo layout is:
| Path | Purpose |
|------|---------|
| go/ | Go services + cmd entrypoints |
| flutter/ | Flutter mobile/desktop app |
| admin/ | Admin web UI (Next.js / Vite) |
| mobile/ or pos/ or api-dart/ | product-specific extras |
| proto/ | gRPC/protobuf schemas |
Every product monorepo (aodex, aosentry, eden-biz, politihub, aohealth) is being aligned to this layout. This skill is how you check whether a repo currently complies. </context>
<process>1. Locate the CLI.
The doctor logic lives at ${CLAUDE_PLUGIN_ROOT}/skills/monorepo-doctor/lib/cli.js. Resolve the plugin root from the env or fall back to the well-known install path.
2. Run the audit.
node "${CLAUDE_PLUGIN_ROOT}/skills/monorepo-doctor/lib/cli.js" $ARGUMENTS
Capture stdout (the human-readable report) and the exit code. Exit code 0 means the monorepo is compliant; exit code 1 means at least one issue was found.
3. Present the report.
Show the full report to the user verbatim. Do not summarise unless they ask — the report is already terse.
4. Suggest next steps.
If the report shows issues, suggest the user invoke /devflow:new-monorepo (template scaffold) or /devflow:quick to fix each issue category. Do not auto-fix without confirmation.
<when_to_use> Use monorepo-doctor for:
- New monorepo onboarding — confirm layout matches the standard
- Periodic drift checks — catch undeclared dirs or missing area docs
- Pre-PR validation — before merging a large refactor
- Pre-release — block ship if binaries snuck into the tree
Do NOT use for:
- Linting code style (use language-native linters)
- Validating CI workflows (separate skill)
- DevFlow
.planning/state checks (use/devflow:status check) </when_to_use>
<output_format> Markdown report with sections:
- Declared areas summary
- Declared areas missing on disk
- Top-level dirs not declared in CLAUDE.md
- Areas without CLAUDE.md
- Tracked binaries
- Final PASS/FAIL marker
Exit non-zero on failure so the parent skill / shell can chain. </output_format>
Related Skills
ao-cyber-systems/decide
development
VerifiedTrustedCommunity
Resolve a parked decision and resume autonomous execution. Use when you see a pending DECISION-NNN.md in .planning/decisions/pending/, when the user wants to choose an option for a blocked checkpoint:decision, or when you need to tell the executor which option to take. Triggers on: "resolve decision", "decide DECISION-", "pick option for DECISION-", "unblock DECISION-", "answer DECISION-", "choose option for decision", "I want option-a", "go with option-b", "my answer is".
SKILL.mdUpdated Jun 13, 2026
ao-cyber-systems/flow
development
VerifiedTrustedCommunity
Orchestrate a multi-step DevFlow workflow by chaining skills. Use when the user wants to invoke a sequence of skills as one ask (e.g., "build and sync to github", "research, plan, then build", "ship and announce"). Triggers on: "ship X to Y", "build and X", "plan and X", "X then Y", "in one go", "as a chain", "all in sequence", "chain", "ship-and-sync", "research-plan-build"
SKILL.mdUpdated May 26, 2026
ao-cyber-systems/new-monorepo
testing
VerifiedTrustedCommunity
Stamp a new polyglot monorepo using the AO Cyber Systems scaffold — root CLAUDE.md with Layout table, per-area CLAUDE.md, path-filtered CI workflows, comprehensive .gitignore, and the no-binaries pre-commit hook config. Use this for new product monorepos (the 5-monorepo architecture: aodex, aosentry, eden-biz, politihub, aohealth, plus future ones). Triggers on: "new monorepo", "scaffold a monorepo", "set up a monorepo", "create a new product monorepo".
SKILL.mdUpdated May 12, 2026
ao-cyber-systems/eden-web:frontend-design
development
VerifiedTrustedCommunity
Build, review, or visually inspect web pages using Hugo templates, Tailwind CSS, and the project's brand design system. Use when the user wants to create new pages, design components, audit existing UI, review frontend code, or visually test rendered pages. Triggers on: "build the UI", "design this page", "create a page", "review the frontend", "audit the UI", "check UI consistency", "make it look good", "frontend review", "visual review", "check how it looks", "inspect the page"
SKILL.mdUpdated May 12, 2026