Enterprise Review

Detects configuration drift, structural drift, and practice drift across all venture repos. Produces a consistency report stored in VCMS.

Must run from crane-console. This skill is not synced to venture repos.

Arguments

code

enterprise-review [--venture codes]

•--venture - Comma-separated venture codes to audit (e.g., --venture ke,dfg). If omitted, audits all ventures with repos.

Parse the arguments provided by the user:

•If it contains --venture, extract the comma-separated codes into TARGET_VENTURES.
•If empty, set TARGET_VENTURES to all ventures from config/ventures.json that have a repo (codes with a corresponding ~/dev/{code}-console directory).

Execution

Step 1: Verify Context

•Confirm cwd is within crane-console (check for config/ventures.json in repo root).
•If not in crane-console, stop: "This command must run from crane-console. It audits cross-venture consistency."
•Parse TARGET_VENTURES. For each code, verify ~/dev/{code}-console exists and is a git repo. Skip missing repos with a warning.

Display:

code

Enterprise Codebase Audit
Ventures: {list of venture codes being audited}

Step 2: Bash Data Collection

Run a bash command that collects structural snapshots from all target venture repos. For each repo at ~/dev/{code}-console:

bash

for CODE in {TARGET_VENTURES}; do
  REPO="$HOME/dev/${CODE}-console"
  [ -d "$REPO/.git" ] || continue

  echo "=== $CODE ==="

  # Key dependency versions from package.json
  echo "-- dependencies --"
  PKGJSON=$(find "$REPO" -maxdepth 3 -name "package.json" -not -path "*/node_modules/*" | head -1)
  if [ -n "$PKGJSON" ]; then
    for dep in typescript hono wrangler eslint prettier vitest; do
      VER=$(jq -r ".dependencies[\"$dep\"] // .devDependencies[\"$dep\"] // \"not found\"" "$PKGJSON" 2>/dev/null)
      echo "$dep=$VER"
    done
  fi

  # TypeScript config
  echo "-- tsconfig --"
  TSCONFIG=$(find "$REPO" -maxdepth 2 -name "tsconfig.json" -not -path "*/node_modules/*" | head -1)
  if [ -n "$TSCONFIG" ]; then
    jq '{strict: .compilerOptions.strict, target: .compilerOptions.target, module: .compilerOptions.module}' "$TSCONFIG" 2>/dev/null
  fi

  # ESLint, Prettier, CI, Commands, Golden Path
  echo "-- eslint --"
  ls "$REPO"/.eslintrc* "$REPO"/eslint.config.* 2>/dev/null || echo "none"
  echo "-- prettier --"
  ls "$REPO"/.prettierrc* "$REPO"/prettier.config.* 2>/dev/null || echo "none"
  echo "-- ci --"
  ls "$REPO"/.github/workflows/*.yml 2>/dev/null || echo "none"
  echo "-- commands --"
  ls "$REPO"/.claude/commands/*.md 2>/dev/null | xargs -I{} basename {} | sort
  echo "-- golden-path --"
  bash ~/dev/crane-console/scripts/golden-path-audit.sh "$REPO" 2>/dev/null | tail -5

  echo ""
done

Store output as RAW_DATA. This should complete in under 30 seconds.

Step 3: Analysis Pass

Parse RAW_DATA and build the drift report. Build these sections:

3a. Version Alignment Table

Compare key dependency versions across all ventures:

code

| Dependency | {vc} | {ke} | {dfg} | {sc} | {dc} | Drift? |
|------------|------|------|-------|------|------|--------|
| typescript | 5.x  | 5.x  | 5.x   | 5.x  | -    | No     |
| eslint     | 9.x  | 8.x  | 9.x   | -    | -    | YES    |

Flag any version where ventures differ by 1+ major version.

3b. Commands Sync Status

List which enterprise commands are present/missing per venture. Note: some commands are enterprise-only (like enterprise-review.md) and should not be synced.

3c. Golden Path Compliance

Pass/fail per venture with tier context:

code

| Venture | Tier | Failures | Warnings | Status |
|---------|------|----------|----------|--------|
| ke      | 1    | 0        | 2        | PASS   |

3d. Drift Hotspots

Cross-cutting issues that affect multiple ventures or represent enterprise-wide concerns:

•Configuration drift (e.g., "dfg is 2 ESLint majors behind ke")
•Missing enterprise standards (e.g., "3/5 repos missing security.yml workflow")
•Practice drift (e.g., "only 2/5 repos have pre-commit hooks configured")

Step 4: Store and Report

4a. VCMS Report

Store concise report (under 500 words) in VCMS using crane_note:

•Action: create
•Tags: ["code-review", "enterprise"]
•Venture: (omit - this is cross-venture)
•Title: Enterprise Review - {YYYY-MM-DD}

4b. Compare with Previous Review

Search for the most recent enterprise review:

code

crane_notes(tag: "code-review", q: "Enterprise Review")

If found, compare: which drift items were flagged before and are now resolved, which are new, which are persistent. Note trend in the report.

4c. Display to User

Present the full report inline:

code

## Enterprise Codebase Audit - {YYYY-MM-DD}

### Version Alignment
{table}

### Commands Sync Status
{table}

### Golden Path Compliance
{table}

### Drift Hotspots
{numbered list}

### Trend
{comparison with previous review}

### Recommendation
{1-3 actionable next steps}

Step 5: Done

After displaying the report, suggest next steps:

•If commands are out of sync: "Run sync-commands.sh to distribute missing commands."
•If version drift detected: "Consider creating issues to align dependency versions."
•If golden path failures: "Run the code-review skill in the failing repos for detailed findings."

Do NOT automatically take any action. Wait for the Captain.

Record completion in the Cadence Engine:

code

crane_schedule(action: "complete", name: "enterprise-review", result: "success", summary: "{N} ventures audited, {findings}", completed_by: "crane-mcp")

Drift Categories

Configuration Drift

•TypeScript version and tsconfig settings (strict mode, target, module)
•ESLint version and config format (flat config vs legacy)
•Prettier version and settings
•Wrangler and Hono versions

Structural Drift

•API file structure conventions
•Claude commands synced vs missing
•CI workflow files present and consistent
•CLAUDE.md format and completeness

Practice Drift

•Pre-commit hooks configured (husky/lint-staged)
•Branch protection enabled
•Security workflow present
•Secret scanning configured (.gitleaks.toml)
•Test framework configured

Notes

•Not synced. This skill stays in crane-console only. It reads from venture repos but doesn't modify them.
•VCMS tags: code-review + enterprise. The code-review tag groups all review artifacts; the enterprise tag distinguishes cross-venture reports from per-venture scorecards.
•Speed: The bash collection step should complete in under 30 seconds. The analysis is a single pass with no sub-agents.
•Prerequisite: Venture repos must be cloned locally at ~/dev/{code}-console. Missing repos are skipped with a warning.