Configure All

Name: Configure All
Author: laurigates

laurigates/claude-plugins

51 installs
49 repo stars
Updated August 4, 2026
laurigates/claude-plugins

Helps with ai & agent building tasks.

About

configure-all is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

configure-all
AI & Agent Building
AI-coding skill

Configure All by the numbers

51 all-time installs (skills.sh)
Ranked #7,219 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

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

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/laurigates/claude-plugins/configure-all.svg)](https://skillselion.com/skills/laurigates/claude-plugins/configure-all)

Installs	51
repo stars	★ 49
Last updated	August 4, 2026
Repository	laurigates/claude-plugins ↗

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

/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: !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

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 \
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.

/configure:all Reference

Report Template

╔══════════════════════════════════════════════════════════════╗
║           Infrastructure Standards Compliance            ║
╠══════════════════════════════════════════════════════════════╣
║  Repository:    <repo-name>                                    ║
║  Project Type:  <type> (detected)                              ║
║  Standards:     2025.1                                         ║
║  Last Check:    <timestamp>                                    ║
╚══════════════════════════════════════════════════════════════╝

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: X FAIL, Y WARN, Z PASS

Issues to Fix:
  1. [FAIL] Component: Description
  2. [WARN] Component: Description

Run with --fix to apply automatic fixes.

Component Applicability by Project Type

Component	Frontend	Infrastructure	Python	Rust
Pre-commit	✅	✅	✅	✅
Release-please	✅	Optional	✅	✅
Dockerfile	✅	⏭️ SKIP	✅	✅
Container	✅	⏭️ SKIP	✅	✅
Skaffold	If k8s/	⏭️ SKIP	If k8s/	If k8s/
CI Workflows	✅	✅	✅	✅
Sentry	✅	Optional	✅	Optional
Documentation	✅	Optional	✅	✅
GitHub Pages	✅	Optional	✅	✅
Cache Busting	✅	⏭️ SKIP	Optional	⏭️ SKIP
Tests	✅	Optional	✅	✅
Coverage	✅	Optional	✅	✅
Memory Profiling	⏭️ SKIP	⏭️ SKIP	✅	⏭️ SKIP
Linting	✅	Optional	✅	✅
Formatting	✅	Optional	✅	✅
Dead Code	✅	Optional	✅	✅
Editor	✅	✅	✅	✅
Security	✅	✅	✅	✅

Standards Tracking Template

# Standards Tracking
# Generated by /configure:all
standards_version: "2025.1"
project_type: "<detected>"
last_configured: "<timestamp>"

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: []

Fix Commands

When --fix is requested, run each failing command with --fix:

/configure:makefile --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