/configure:all

Run all infrastructure standards compliance checks.

Context

Orchestrator command that runs all /configure:* subcommands and provides a comprehensive compliance report.

Workflow

Phase 1: Project Detection

1. Read .project-standards.yaml if exists
2. Auto-detect project type:
   • infrastructure: Has terraform/, helm/, argocd/, or *.tf files
   • frontend: Has package.json with vue/react dependencies
   • python: Has pyproject.toml or requirements.txt
3. Allow override via --type flag
4. Report detected vs tracked type if different

Phase 2: Run All Checks

Execute each configure command in check-only mode:

/configure:makefile --check-only
/configure:pre-commit --check-only
/configure:release-please --check-only
/configure:dockerfile --check-only
/configure:container --check-only
/configure:skaffold --check-only
/configure:workflows --check-only
/configure:sentry --check-only
/configure:docs --check-only
/configure:github-pages --check-only
/configure:cache-busting --check-only
/configure:tests --check-only
/configure:coverage --check-only
/configure:memory-profiling --check-only
/configure:linting --check-only
/configure:formatting --check-only
/configure:dead-code --check-only
/configure:editor --check-only
/configure:security --check-only

Collect results from each check.

Phase 3: Generate Comprehensive Report

╔══════════════════════════════════════════════════════════════╗
║           Infrastructure Standards Compliance            ║
╠══════════════════════════════════════════════════════════════╣
║  Repository:    R4C-Cesium-Viewer                            ║
║  Project Type:  frontend (detected)                          ║
║  Standards:     2025.1                                       ║
║  Last Check:    2025-11-28 10:30:00                          ║
╚══════════════════════════════════════════════════════════════╝

Component Summary:
┌─────────────────┬──────────┬─────────────────────────────────┐
│ Component       │ Status   │ Notes                           │
├─────────────────┼──────────┼─────────────────────────────────┤
│ Makefile        │ ✅ PASS  │ All targets present             │
│ Pre-commit      │ ⚠️ WARN  │ 2 outdated hooks                │
│ Release-please  │ ✅ PASS  │ Fully compliant                 │
│ Dockerfile      │ ❌ FAIL  │ Missing healthcheck             │
│ Container       │ ⚠️ WARN  │ Missing vulnerability scan      │
│ Skaffold        │ ✅ PASS  │ 3 profiles configured           │
│ CI Workflows    │ ⚠️ WARN  │ Missing test workflow           │
│ Sentry          │ ✅ PASS  │ SDK configured                  │
│ Documentation   │ ⚠️ WARN  │ Generator configured, no deploy │
│ GitHub Pages    │ ❌ FAIL  │ No workflow configured          │
│ Cache Busting   │ ✅ PASS  │ Content hashing enabled         │
│ Tests           │ ✅ PASS  │ Vitest configured               │
│ Coverage        │ ⚠️ WARN  │ Below 80% threshold             │
│ Linting         │ ✅ PASS  │ Biome configured                │
│ Formatting      │ ✅ PASS  │ Biome configured                │
│ Dead Code       │ ⚠️ WARN  │ 3 unused exports                │
│ Editor          │ ✅ PASS  │ .editorconfig present           │
│ Security        │ ✅ PASS  │ Dependency audit enabled        │
└─────────────────┴──────────┴─────────────────────────────────┘

Overall Status: 1 FAIL, 2 WARN, 3 PASS

Issues to Fix:
  1. [FAIL] Dockerfile: Add HEALTHCHECK instruction
  2. [WARN] Pre-commit: Update conventional-pre-commit v3.6.0 → v4.3.0
  3. [WARN] Pre-commit: Update gruntwork/helmlint v0.1.23 → v0.1.29
  4. [WARN] Workflows: Add test.yml workflow

Run with --fix to apply automatic fixes.

Phase 4: Apply Fixes (If Requested)

If --fix flag or user confirms:

1. Run each configure command with --fix:

   /configure:pre-commit --fix
   /configure:release-please --fix
   /configure:dockerfile --fix
   /configure:container --fix
   /configure:skaffold --fix
   /configure:workflows --fix
   /configure:sentry --fix
   /configure:docs --fix
   /configure:github-pages --fix
   /configure:cache-busting --fix
   /configure:tests --fix
   /configure:coverage --fix
   /configure:memory-profiling --fix
   /configure:linting --fix
   /configure:formatting --fix
   /configure:dead-code --fix
   /configure:editor --fix
   /configure:security --fix
   

2. Report what was fixed and what requires manual intervention

Phase 5: Update Standards Tracking

Create or update .project-standards.yaml:

# Standards Tracking
# Generated by /configure:all
standards_version: "2025.1"
project_type: "frontend"
last_configured: "2025-11-28T10:30:00Z"

components:
  pre-commit: "2025.1"
  release-please: "2025.1"
  dockerfile: "2025.1"
  container: "2025.1"
  skaffold: "2025.1"
  workflows: "2025.1"
  sentry: "2025.1"
  docs: "2025.1"
  github-pages: "2025.1"
  cache-busting: "2025.1"
  tests: "2025.1"
  coverage: "2025.1"
  memory_profiling: "2025.1"
  linting: "2025.1"
  formatting: "2025.1"
  dead-code: "2025.1"
  editor: "2025.1"
  security: "2025.1"

# Documented deviations from standard
deviations: []

Flags

Exit Codes (for CI)

Examples

# Full compliance check with interactive fixes
/configure:all

# CI mode - check only, no fixes
/configure:all --check-only

# Auto-fix all issues
/configure:all --fix

# Force infrastructure type
/configure:all --type infrastructure

Component Applicability

Not all components apply to all project types:

See Also

• /configure:select – Interactively select which components to configure
• /configure:status – Quick read-only status overview
• /configure:pre-commit – Pre-commit specific checks
• /configure:release-please – Release automation checks
• /configure:dockerfile – Dockerfile configuration checks
• /configure:container – Comprehensive container infrastructure
• /configure:skaffold – Kubernetes development checks
• /configure:workflows – GitHub Actions checks
• /configure:sentry – Sentry error tracking checks
• /configure:docs – Documentation standards and generators
• /configure:github-pages – GitHub Pages deployment
• /configure:cache-busting – Cache-busting strategies
• /configure:tests – Testing framework setup
• /configure:coverage – Code coverage configuration
• /configure:memory-profiling – Memory profiling with pytest-memray
• /configure:linting – Linter configuration
• /configure:formatting – Code formatter setup
• /configure:dead-code – Dead code detection
• /configure:editor – Editor/IDE configuration
• /configure:security – Security scanning

Agent Teams (Optional)

For faster compliance checks on large projects, spawn teammates for parallel configuration checks:

This is optional — the skill works sequentially without agent teams.