From configure-plugin
Interactively selects and configures infrastructure standards like CI/CD hooks, GitHub Actions, Dockerfiles, Skaffold for detected project types (infrastructure, frontend, Python, Rust).
How this skill is triggered — by the user, by Claude, or both
Slash command
/configure-plugin:configure-selectThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interactively select which infrastructure standards checks to run.
Interactively select which infrastructure standards checks to run.
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up selected components interactively | Running all components (use /configure:all) |
| Choosing specific standards to implement | Checking status only (use /configure:status) |
| Customizing configuration scope for project | Single component needed (use specific /configure:X skill) |
| User wants control over which components to configure | Automated full setup preferred |
| Building configuration incrementally | Complete infrastructure setup needed immediately |
find . -maxdepth 1 -name \'.project-standards.yaml\'grep -m1 "^project_type:" .project-standards.yamlfind . -maxdepth 2 \( -name '*.tf' -o -type d -name 'terraform' \) -print -quitfind . -maxdepth 1 -name \'package.json\'find . -maxdepth 1 -name \'pyproject.toml\'find . -maxdepth 1 -name \'Cargo.toml\'Parse from $ARGUMENTS:
--check-only: Report status without offering fixes (CI/CD mode)--fix: Apply fixes automatically to all selected componentsExecute this interactive component selection workflow:
.project-standards.yaml if it exists (check project_type field)terraform/, helm/, argocd/, or *.tf filespackage.json with vue/react dependenciespyproject.toml or requirements.txtCargo.tomlUse AskUserQuestion with multiSelect to present four category-based questions:
Question 1: CI/CD & Version Control
| Option | Description |
|---|---|
| Pre-commit hooks | Git hooks for linting, formatting, commit messages |
| Release automation | release-please workflow and changelog generation |
| GitHub Actions | CI/CD workflows for testing and deployment |
| All CI/CD | Includes: pre-commit, release-please, workflows, github-pages, makefile |
Question 2: Container & Deployment
| Option | Description |
|---|---|
| Dockerfile | Alpine/slim base, non-root user, multi-stage builds |
| Container infra | Registry, scanning, devcontainer setup |
| Skaffold | Kubernetes development configuration |
| All container | Includes: dockerfile, container, skaffold, sentry, justfile |
Question 3: Testing
| Option | Description |
|---|---|
| Test framework | Vitest, Jest, pytest, or cargo-nextest setup |
| Code coverage | Coverage thresholds and reporting |
| API testing | Pact contracts, OpenAPI validation |
| All testing | Includes: tests, coverage, api-tests, integration-tests, load-tests, ux-testing, memory-profiling |
Question 4: Code Quality
| Option | Description |
|---|---|
| Linting & Formatting | Biome, Ruff, Clippy configuration |
| Security scanning | Dependency audits, SAST, secrets detection |
| Documentation | TSDoc, JSDoc, pydoc, rustdoc generators |
| All quality | Includes: linting, formatting, dead-code, docs, security, editor, package-management |
| Selection | Commands |
|---|---|
| Pre-commit hooks | /configure:pre-commit |
| Release automation | /configure:release-please |
| GitHub Actions | /configure:workflows |
| All CI/CD | pre-commit, release-please, workflows, github-pages, makefile |
| Dockerfile | /configure:dockerfile |
| Container infra | /configure:container |
| Skaffold | /configure:skaffold |
| All container | dockerfile, container, skaffold, sentry, justfile |
| Test framework | /configure:tests |
| Code coverage | /configure:coverage |
| API testing | /configure:api-tests |
| All testing | tests, coverage, api-tests, integration-tests, load-tests, ux-testing, memory-profiling |
| Linting & Formatting | /configure:linting, /configure:formatting |
| Security scanning | /configure:security |
| Documentation | /configure:docs |
| All quality | linting, formatting, dead-code, docs, security, editor, package-management |
Run each selected command with appropriate flags:
--check-only first, then offer --fix--check-only flag: Only audit, no fixes offered--fix flag: Apply fixes automaticallyReport results as each check completes.
Print a summary for selected components only:
Selected Components Summary:
+-----------------+----------+---------------------------------+
| Component | Status | Notes |
+-----------------+----------+---------------------------------+
| Pre-commit | WARN | 2 outdated hooks |
| Linting | PASS | Biome configured |
| Formatting | PASS | Biome configured |
+-----------------+----------+---------------------------------+
| Context | Command |
|---|---|
| Interactive component selection | /configure:select |
| Select and auto-fix | /configure:select --fix |
| Check mode only | /configure:select --check-only |
| Detect project type | test -f .project-standards.yaml && grep "^project_type:" .project-standards.yaml | sed 's/.*:[[:space:]]*//' |
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply fixes automatically to all selected |
| Command | Use Case |
|---|---|
/configure:all | Run everything (CI, full audit) |
/configure:select | Choose specific components interactively |
/configure:status | Quick read-only overview |
/configure:<component> | Single component only |
/configure:all - Run all checks/configure:status - Read-only status overviewnpx claudepluginhub laurigates/claude-plugins --plugin configure-pluginRuns 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.
Generates CI/CD workflows, Dockerfiles, and deployment configs from a tech stack definition. Use when scaffolding infrastructure for a project.
Configures Arness Infra for projects by selecting cloud providers, IaC tools like Terraform/Pulumi, environments, CI/CD platforms, scanning existing artifacts, and persisting to CLAUDE.md.