ironlint-init

# IronLint Init Start with IronLint's generic baseline, then help the user choose checks for their stack and installed linters. A check is two fields — `files` (a glob or list) and `run` (a shell command that exits nonzero to block); there are no engines or severities. This skill is user-driven. Do not silently install tools or add checks. Every step below is a proposal the user accepts or declines. ## Step 1: Run `ironlint init` `ironlint init` writes a small, stack-agnostic starter `.ironlint.yml` and trusts it for you. It does not inspect manifest files or wrap linters: ```bash ironlint init ``` This creates `.ironlint.yml` with generic starter checks (and, outside this Claude session, can also wire hooks into other agents — not needed here, the PreToolUse hook is already running). Review the generated checks. ## Step 2: Wrap the project's linters as checks For each linter the user has installed (ruff, biome, eslint, tsc, phpstan, clippy, …) that runs per file, propose a check that feeds the proposed content on stdin; any nonzero exit blocks: ```yaml checks: ruff-check: files: ["**/*.py"] run: "ruff check --quiet --stdin-filename \"$IRONLINT_FILE\" -" ``` Test each candidate against a sample file before adding it (see `/ironlint-config` for the fixture loop). Only add checks that pass on clean input and block on dirty input. Skip repo-wide tools that aren't per-file (e.g. `cargo clippy`) — they don't map to a per-file check; suggest running them as a pr...