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

configure-status

Infrastructure compliance status (read-only). Use when checking overall compliance, generating a report, or reviewing project health without making changes.

How do I install this agent skill?

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

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is a read-only reporting tool that evaluates a project's compliance with infrastructure standards by scanning local configuration files. It uses safe shell commands like find and grep to gather metadata and does not perform any network operations or file modifications.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerwarn

    1/1 file flagged

What does this agent skill do?

/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 statusRunning full compliance checks with fixes (use /configure:all --fix)
Generating compliance reportsNeed to fix issues found (use /configure:all)
Quick project health checkChecking specific component (use /configure:X --check-only)
CI/CD status validationRunning interactive selection (use /configure:select)
Reviewing current configuration stateNeed 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

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

Step 2: Scan configuration files

Check for presence and validity of each configuration:

ComponentFiles Checked
Pre-commit.pre-commit-config.yaml
Release-pleaserelease-please-config.json, .release-please-manifest.json, .github/workflows/release-please.yml
DockerfileDockerfile, Dockerfile.*
Skaffoldskaffold.yaml
CI Workflows.github/workflows/*.yml
Helmhelm/*/Chart.yaml
Documentationtsdoc.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 Bustingnext.config.*, vite.config.*, vercel.json, _headers
Testsvitest.config.*, jest.config.*, pytest.ini, pyproject.toml [tool.pytest], .cargo/config.toml
Coveragevitest.config.* [coverage], pyproject.toml [tool.coverage], .coveragerc
Lintingbiome.json, pyproject.toml [tool.ruff], clippy.toml
Formatting.prettierrc*, biome.json, pyproject.toml [tool.ruff.format], rustfmt.toml
Dead Codeknip.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]

Step 3: Determine compliance status

For each component, assign a status:

StatusMeaning
PASSFully compliant with project standards
WARNPresent but outdated or incomplete
FAILMissing required configuration
SKIPNot 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

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

Flags

FlagDescription
--verboseShow 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

See Also

  • /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

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-status">View configure-status on skillZs</a>