/configure:status Skill

/configure:status

Display infrastructure standards compliance status without making changes.

When to Use This Skill

| Use this skill when... | Use another approach when... | |------------------------|------------------------------| | Checking overall compliance status | Running full compliance checks with fixes (use /configure:all --fix) | | Generating compliance reports | Need to fix issues found (use /configure:all) | | Quick project health check | Checking specific component (use /configure:X --check-only) | | CI/CD status validation | Running interactive selection (use /configure:select) | | Reviewing current configuration state | Need detailed component analysis |

Context

Project standards: !find . -maxdepth 1 -name \'.project-standards.yaml\'
Project type: !find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^project_type:" {} +
Standards version: !find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^standards_version:" {} +
Last configured: !find . -maxdepth 1 -name '.project-standards.yaml' -exec grep -m1 "^last_configured:" {} +
Pre-commit config: !find . -maxdepth 1 -name \'.pre-commit-config.yaml\'
Workflows: !find . -path '*/.github/workflows/*' -maxdepth 3 -name '*.yml'
Has Dockerfile: !find . -maxdepth 1 -name 'Dockerfile*' -print -quit
Has skaffold: !find . -maxdepth 1 -name \'skaffold.yaml\'
Has helm: !find . -maxdepth 2 -type d -name 'helm' -print -quit
Test configs: !find . -maxdepth 1 $ -name 'vitest.config.*' -o -name 'jest.config.*' -o -name 'pytest.ini' $
Linting config: !find . -maxdepth 1 $ -name 'biome.json' -o -name '.eslintrc*' $
Editor config: !find . -maxdepth 1 -name \'.editorconfig\'
Gitleaks config: !find . -maxdepth 1 -name \'.gitleaks.toml\'
Package files: !find . -maxdepth 1 $ -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' $

Parameters

Parse from $ARGUMENTS:

--verbose: Show detailed compliance information for each component

Execution

Execute this read-only compliance status check:

Step 1: Detect project type

Read .project-standards.yaml if it exists (shows tracked version and last configured date)
Auto-detect project type from file structure
Report discrepancy if detected type differs from tracked type

Step 2: List components and run detection scripts

List the component roster from the manifest (single source of truth — configure-all/components.yaml):

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

For each COMPONENT=<name> ... HAS_SCRIPT=true line, run that component's detection script (read-only) and collect only its STATUS= and ISSUE_COUNT= lines for the roll-up:

bash "${CLAUDE_SKILL_DIR}/../<name>/scripts/<name>.sh" --project-dir "$(pwd)"

For HAS_SCRIPT=false components, assess presence from the file-presence table in REFERENCE.md using the Context probes above. Never re-derive the component list by hand — new detection scripts automatically improve this skill via the manifest.

Step 3: Determine compliance status

For each component, assign a status:

| Status | Meaning | |--------|---------| | PASS | Fully compliant with project standards | | WARN | Present but outdated or incomplete | | FAIL | Missing required configuration | | SKIP | Not applicable for project type |

Step 4: Print compliance report

Infrastructure Standards Status
====================================
Repository: [name]
Project Type: [type] ([detected])
Standards Version: [version] (tracked: [tracked])
Last Configured: [date]

Component Status:
  Pre-commit      PASS   v5.0.0 hooks, conventional commits
  Release-please  PASS   Node workspace plugin
  Dockerfile      WARN   Missing healthcheck
  Skaffold        PASS   3 profiles configured
  CI Workflows    WARN   Missing test workflow
  Helm            SKIP   No helm/ directory
  Tests           PASS   Vitest configured
  Coverage        WARN   72% (below 80% threshold)
  Linting         PASS   Biome configured
  Formatting      PASS   Biome configured
  Dead Code       WARN   Knip found 3 unused exports
  Editor          PASS   .editorconfig present
  Security        PASS   gitleaks + npm audit

Summary: [N] warnings, [N] failures
Run /configure:all to fix issues

Step 5: Show verbose details (if requested)

If --verbose flag is set:

Show specific version numbers for each hook/tool
List individual compliance checks performed
Show detected deviations from .project-standards.yaml
Display file modification timestamps
Show cache-busting configuration details (framework, CDN, hash patterns)

Agentic Optimizations

| Context | Command | |---------|---------| | Quick status check | /configure:status | | Verbose status | /configure:status --verbose | | Check standards version | grep "^standards_version:" .project-standards.yaml 2>/dev/null \| sed 's/.*:[[:space:]]*//' | | Check last configured date | grep "^last_configured:" .project-standards.yaml 2>/dev/null \| sed 's/.*:[[:space:]]*//' | | List all workflow files | find .github/workflows -maxdepth 1 -name '*.yml' -exec basename {} \; |

Flags

| Flag | Description | |------|-------------| | --verbose | Show detailed compliance information |

Notes

This command is read-only - no files are modified
Use for CI/CD compliance checks (exit code reflects status)
Run before /configure:all to preview what will be fixed

Agent Skills: /configure:status

Install this agent skill to your local

Skill Files