skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
laurigates/claude-plugins51 installs

configure-all

Run all infrastructure standards checks and configure compliance across a project. Use when performing a comprehensive infrastructure audit, setting up a new project against all standards, batch-fixing compliance issues with --fix, or validating CI/CD compliance. Natural triggers: "check all standards", "audit project compliance", "configure everything", "run all configure checks".

How do I install this agent skill?

npx skills add https://github.com/laurigates/claude-plugins --skill configure-all
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill automates infrastructure compliance audits by detecting project types using local file metadata and running associated configuration checks via sub-skills. No malicious activity or safety violations were identified.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerwarn

    1/2 files flagged

What does this agent skill do?

/configure:all

Run all infrastructure standards compliance checks.

When to Use This Skill

Use this skill when...Use another approach when...
Performing comprehensive infrastructure auditChecking single component (use specific /configure:X skill)
Setting up new project with all standardsProject already has all standards configured
CI/CD compliance validationNeed detailed status only (use /configure:status)
Running initial configurationInteractive component selection needed (use /configure:select)
Batch-fixing all compliance issues with --fixManual 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: !grep -m1 "^standards_version:" .project-standards.yaml

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: Run all checks

Execute each configure command in check-only mode using the SlashCommand tool:

/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

Skip components that do not apply to the detected project type. For component applicability by project type, see REFERENCE.md.

Collect results from each check.

Step 3: 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 4: 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 5: 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

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

Flags

FlagDescription
--check-onlyReport status without offering fixes
--fixApply all fixes automatically
--type <type>Override project type (frontend, infrastructure, python)

Exit Codes (for CI)

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

Agent Teams (Optional)

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

TeammateFocusChecks
Linting teammateCode quality configslinting, formatting, dead-code, editor
Security teammateSecurity configssecurity, pre-commit, container
Testing teammateTest infrastructuretests, coverage, memory-profiling
CI teammateDeployment configsworkflows, 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
  • /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

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/laurigates/claude-plugins/configure-all">View configure-all on skillZs</a>