Setup code quality

Install and wire the requested quality stack, preserving checks with unique coverage. Scope is tooling setup and verification. Do not automatically repair pre-existing code findings, delete unused application code, remove existing comments, reformat the repository, or refactor duplication. Creating this skill is not an instruction to run it against the current repository.

Establish compatibility before edits

• Read applicable project instructions and inspect the existing working changes, package manifests, lockfiles, source languages, framework, TypeScript configs, and quality commands. Follow commands into their actual orchestrators, CI jobs, hooks, and editor settings.
• A package manifest alone does not establish compatibility. Require an actual TypeScript project that can run the full requested stack. For a JavaScript-only, pure Rust, Python, or other incompatible project, report the reason and make no changes, including no new package manifest or lockfile.
• In a mixed repository, scope changes to compatible TypeScript packages. Preserve other languages' tools. Use the existing workspace owner for shared dependencies and avoid duplicate per-package installs. If the target package or root scope is materially ambiguous, resolve that before edits.
• Check current official package documentation and registry metadata for Node engines, package-manager support, TypeScript 7 support, peer dependencies, framework requirements, and configuration syntax. Do not assume the latest package versions are mutually compatible. Respect the project's runtime and dependency policies; do not upgrade its runtime, framework, or unrelated packages to force compatibility.
• Use the latest compatible stable TypeScript 7.x release, not an unbounded latest tag, a preview, or a different major. If that or another required tool cannot work with the project, leave the target unchanged and report the concrete blocker. Do not silently install a partial stack. Do not introduce TypeScript aliases or compatibility fallbacks without explicit approval.

Configure the stack

Use the project's existing package manager to add or reconcile these devDependencies and its authoritative lockfile. Run the installed local tools, not dlx, global executables, or commands that fetch packages on demand. Preserve an already suitable version rather than upgrading unnecessarily.