What problem does it solve? Keeping shared configuration packages (Biome, TypeScript, Renovate, markdownlint, release-it, and more) consistent across repositories is tedious and error-prone. This Skill audits a repository against the DNBHQ package registry, classifies each package's state, and coordinates targeted onboarding, updates, migrations, or repairs without touching unrelated configuration. ## Core Features & Use Cases - Read-only audits: Classify every registry package as missing, partial, current, outdated, legacy, duplicated, mixed, invalid, or unknown, with evidence and a recommended action per package. - Guided initialization: Parse prose instructions into include/exclude lists, sort selected packages by registry weight, and delegate setup to package-specific workflows. - Safe migrations: Preserve repository-specific overrides, avoid removing legacy tools like ESLint or Prettier until replacement coverage is confirmed, and validate each package independently. - Use Case: You inherit a repository with a hand-copied ESLint config and an outdated tsconfig. Run an audit to see which DNBHQ packages apply, then initialize only Biome and TypeScript configs while leaving release tooling untouched. ## Quick Start Ask the assistant to audit this repository's DNBHQ configuration packages and recommend which ones to onboard or update.
