Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From configure-plugin
Shows read-only infrastructure standards compliance status by scanning configs like pre-commit, CI workflows, Dockerfiles, Skaffold, Helm, linting, tests, and editorconfig. For quick health checks and CI/CD validation.
npx claudepluginhub laurigates/claude-plugins --plugin configure-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/configure-plugin:configure-statushaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Display infrastructure standards compliance status without making changes.
Runs comprehensive infrastructure standards compliance checks and auto-configures fixes for frontend, infrastructure, or Python projects. Ideal for audits, new setups, CI/CD validation with --check-only or --fix.
Audits a repository for baseline compliance across 9 categories including code quality, security, CI/CD, testing, and documentation. Emits Markdown report and JSON sidecar.
Assesses codebase for AI agent readiness by detecting stacks, monorepos, git setup, and evaluating style, testing, code quality, secrets, and file sizes.
Share bugs, ideas, or general feedback.
Display infrastructure standards compliance status without making changes.
| 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 |
find . -maxdepth 1 -name \'.project-standards.yaml\'grep -m1 "^project_type:" .project-standards.yamlgrep -m1 "^standards_version:" .project-standards.yamlgrep -m1 "^last_configured:" .project-standards.yamlfind . -maxdepth 1 -name \'.pre-commit-config.yaml\'find .github/workflows -maxdepth 1 -name '*.yml'find . -maxdepth 1 -name 'Dockerfile*' -print -quitfind . -maxdepth 1 -name \'skaffold.yaml\'find . -maxdepth 2 -type d -name 'helm' -print -quitfind . -maxdepth 1 \( -name 'vitest.config.*' -o -name 'jest.config.*' -o -name 'pytest.ini' \)find . -maxdepth 1 \( -name 'biome.json' -o -name '.eslintrc*' \)find . -maxdepth 1 -name \'.editorconfig\'find . -maxdepth 1 -name \'.gitleaks.toml\'find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' \)Parse from $ARGUMENTS:
--verbose: Show detailed compliance information for each componentExecute this read-only compliance status check:
.project-standards.yaml if it exists (shows tracked version and last configured date)Check for presence and validity of each configuration:
| Component | Files Checked |
|---|---|
| Pre-commit | .pre-commit-config.yaml |
| Release-please | release-please-config.json, .release-please-manifest.json, .github/workflows/release-please.yml |
| Dockerfile | Dockerfile, Dockerfile.* |
| Skaffold | skaffold.yaml |
| CI Workflows | .github/workflows/*.yml |
| Helm | helm/*/Chart.yaml |
| Documentation | tsdoc.json, typedoc.json, mkdocs.yml, docs/conf.py, pyproject.toml [tool.ruff.lint.pydocstyle] |
| GitHub Pages | .github/workflows/docs.yml, .github/workflows/*pages*.yml |
| Cache Busting | next.config.*, vite.config.*, vercel.json, _headers |
| Tests | vitest.config.*, jest.config.*, pytest.ini, pyproject.toml [tool.pytest], .cargo/config.toml |
| Coverage | vitest.config.* [coverage], pyproject.toml [tool.coverage], .coveragerc |
| Linting | biome.json, pyproject.toml [tool.ruff], clippy.toml |
| Formatting | .prettierrc*, biome.json, pyproject.toml [tool.ruff.format], rustfmt.toml |
| Dead Code | knip.json, knip.ts, pyproject.toml [tool.vulture] |
| Editor | .editorconfig, .vscode/settings.json, .vscode/extensions.json |
| Security | .github/workflows/*security*, .gitleaks.toml, pyproject.toml [tool.bandit] |
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 |
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
If --verbose flag is set:
.project-standards.yaml| 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 {} \; |
| Flag | Description |
|---|---|
--verbose | Show detailed compliance information |
/configure:all to preview what will be fixed/configure:all - Run all compliance checks/configure:select - Interactively select which components to configure/configure:pre-commit - Pre-commit specific checks/configure:release-please - Release-please specific checks