dxkit-configlisted

# dxkit-config This skill modifies the three configuration files dxkit reads. Reach for it when the user asks to "ignore this vendored directory," "stop flagging X," "make the guardrail stricter/laxer," or "what controls Y." ## The three config files | File | Purpose | When to edit | |---|---|---| | `.dxkit-ignore` | Extra paths dxkit's analyzers should skip (gitignore-style format) | Vendored code, generated code, test fixtures, large data files | | `.npx vyuh-dxkit.json` | Manifest of detected stack + custom settings (regenerated by `init` / `update`) | Rare — usually let `dxkit update` regenerate. Override version pins or framework detection here. | | `.dxkit/policy.json` | Severity policy for guardrail check | Customize what blocks a PR (e.g., demote `medium` to warning) | | `.dxkit/tools.json` | Where dxkit looks for / installs scanner binaries | Tools live in a non-standard or corp-managed directory, or PATH detection misses them (common on Windows / locked-down machines) | ## Adding a path to `.dxkit-ignore` Format mirrors `.gitignore`: directory/, file-glob, multi-segment paths. ```bash # Append a vendored directory echo 'vendor/' >> .dxkit-ignore # Append a generated-code dir echo 'src/generated/' >> .dxkit-ignore # Append a glob (auto-generated TypeScript types) echo '*.generated.ts' >> .dxkit-ignore ``` Or use Edit to add multiple entries cleanly. The file accepts comments (`#`). After editing, the **next** `baseline create` picks up the change. Existing