Skip to content

Latest commit

 

History

History
51 lines (31 loc) · 2.88 KB

File metadata and controls

51 lines (31 loc) · 2.88 KB

devtools

Developer tooling setup and management plugin for Claude Code.

Skills

Skill Command Purpose
sops-setup /devtools:sops-setup Set up SOPS + age encryption for .env files
sops-encrypt /devtools:sops-encrypt Encrypt .env files
sops-decrypt /devtools:sops-decrypt Decrypt .env.encrypted files
sops-add-key /devtools:sops-add-key Add a machine's public key and re-encrypt
code-env-setup /devtools:code-env-setup Interactive Claude Code environment setup wizard
quality-stack /devtools:quality-stack JVM project quality/testing tooling audit and setup
taskfile-setup /devtools:taskfile-setup Install Taskfile and scaffold/audit Taskfile.yml

Claude Code Setup

Interactive environment setup wizard that detects existing Claude Code configuration and guides through best-practice setup for Global CLAUDE.md, project scaffolding, MCP servers, hooks, custom agents, keybindings, and settings.

Run /devtools:code-env-setup to start the wizard, or /devtools:code-env-setup [category] to configure a specific category (e.g., hooks, mcp).

SOPS + age Overview

SOPS (Secrets OPerationS) encrypts file values while keeping keys in plaintext for meaningful git diffs. Combined with age, it provides simple, secure encryption for sharing .env files across machines without external services.

Multi-Machine Workflow

Each machine generates its own age key pair. Public keys are listed in .sops.yaml (committed to git). Encrypted files can be decrypted by any authorized machine. To add a new machine, run /devtools:sops-add-key.

Taskfile Setup

Install Taskfile and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates. Auto-detects Node.js/pnpm, JVM/Gradle, Python/uv, Docker, and recommends single-file or multi-file patterns based on project complexity.

Two-Phase Workflow

  1. Audit (when Taskfile exists) — Analyze for best-practice violations (missing desc, no preconditions on deploy tasks, no dotenv config, etc.) and offer fixes
  2. Scaffold (when no Taskfile exists) — Detect ecosystems, choose pattern (single-file or multi-file), generate Taskfile.yml with ecosystem-specific task groups

Run /devtools:taskfile-setup to get started.

Quality Stack

Scans JVM projects (Gradle/Maven) to detect configured quality and testing tools, cross-references against research-backed recommendations, and assists with setup.

Two-Phase Workflow

  1. Recommend — Run the scanner, fetch research docs, cross-reference, generate a prioritized report
  2. Setup — User selects tools from the report, skill configures build files, creates config files, and verifies detection

Run /devtools:quality-stack to audit your project's tooling.