dev-tooling
Installation
SKILL.md
Dev tooling
Every project should arrive at the same standard toolchain for its stack, whoever set it up and whenever. This skill detects the stack, compares the project against a catalog of preferred tools, and reports or closes the gap.
The catalog is the opinion; this file is only the loop. Tools, versions, configs and the reasons behind them live in references/, one file per layer, so adding a stack never touches the workflow.
Modes
- Check — report what is present, missing, partial or conflicting, with the planned action for each. Change nothing. Use it when the user asks to check, audit or list what is missing, or when the request does not say.
- Init — check, then apply the plan and verify it. Use it when the user asks to set up, initialize, install or bring the project up to standard.
The loop
- Detect. Run
python3 scripts/detect.py <project-dir>. It prints facts: the layers; each JavaScript package with its package manager, TypeScript files and catalog tools with versions; Composer tools and whether each is required directly or arrives transitively; CSS grouped by the package that owns it; each Go module with its Go version and tool directives; the environment and whether DDEV is running; existing configs, with framework-scaffolded ones flagged; how tools are already run (GrumPHP, gulp, mise tasks, hooks, CI); gitignore rules that affect config file names; and machine binaries. Do not guess the stack from file names yourself; if the script misses something, fix the script.