configure-all

/configure:all

Run all infrastructure standards compliance checks.

When to Use This Skill

Use this skill when...	Use another approach when...
Performing comprehensive infrastructure audit	Checking single component (use specific /configure:X skill)
Setting up new project with all standards	Project already has all standards configured
CI/CD compliance validation	Need detailed status only (use /configure:status)
Running initial configuration	Interactive component selection needed (use /configure:select)
Batch-fixing all compliance issues with --fix	Manual review of each component preferred

Context

• Project standards: !find . -maxdepth 1 -name \'.project-standards.yaml\'
• Project type indicators: !find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name '*.tf' \)
• Infrastructure dirs: !find . -maxdepth 1 -type d \( -name 'terraform' -o -name 'helm' -o -name 'argocd' \)
• Current standards version: !find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^standards_version:" {} +

Parameters

Parse from command arguments:

• --check-only: Report status without offering fixes (CI/CD mode)
• --fix: Apply all fixes automatically without prompting
• --type <type>: Override auto-detected project type (frontend, infrastructure, python)

Execution

Execute this comprehensive infrastructure standards compliance check:

Step 1: Detect project type

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

Step 2: List components from the manifest

The component roster lives in components.yaml — the single source of truth. Never hand-maintain a component list here; run the lister:

bash "${CLAUDE_SKILL_DIR}/scripts/list-components.sh"

Each COMPONENT=<name> DOMAIN=<domain> HAS_SCRIPT=<bool> TYPES=<types> line is one component skill. If the lister reports STATUS=ERROR, stop and surface the ISSUES: block — the manifest and the skills on disk have drifted.

Step 3: Run all checks

For each listed component whose TYPES includes the detected project type (TYPES=all always applies), invoke it in check-only mode using the SlashCommand tool — e.g. COMPONENT=configure-tests runs:

/configure:tests --check-only

Skip components whose TYPES excludes the detected project type, and report them as SKIP. For finer applicability judgment (e.g. Skaffold only when a k8s/ dir exists), see REFERENCE.md.

Collect results from each check.

Step 4: Generate compliance report

Print a summary table with each component's status (PASS/WARN/FAIL), overall counts, and a list of issues to fix. For report format template, see REFERENCE.md.

Step 5: Apply fixes (if requested)

If --fix flag is set or user confirms:

1. Run each failing configure command with --fix
2. Report what was fixed and what requires manual intervention

Step 6: Update standards tracking

Create or update .project-standards.yaml with the current standards version, project type, timestamp, and component versions. For template, see REFERENCE.md.

Agentic Optimizations

Context	Command
Quick compliance check (all components)	/configure:all --check-only
Auto-fix all issues	/configure:all --fix
Check standards file validity	test -f .project-standards.yaml && cat .project-standards.yaml | head -10
List project type indicators	find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' \) -exec basename {} \;
Count missing components	grep -c "status: missing" compliance-report.txt 2>/dev/null

Flags

Flag	Description
--check-only	Report status without offering fixes
--fix	Apply all fixes automatically
--type <type>	Override project type (frontend, infrastructure, python)

Exit Codes (for CI)

Code	Meaning
0	All checks passed
1	Warnings found (non-blocking)
2	Failures found (blocking)

Agent Teams (Optional)

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

Teammate	Focus	Checks
Linting teammate	Code quality configs	linting, formatting, dead-code, editor
Security teammate	Security configs	security, pre-commit, container
Testing teammate	Test infrastructure	tests, coverage, memory-profiling
CI teammate	Deployment configs	workflows, release-please, dockerfile, skaffold

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

See Also

• /configure:select - Interactively select which components to configure
• /configure:status - Quick read-only status overview
• components.yaml - The authoritative component roster (per-component /configure:X skills are listed there, not here)