Engineering Quality

Purpose

Code-quality and language-safety guidance spanning ESLint, SonarQube, dead code, TypeScript strictness, JavaScript fundamentals, and CSS quality boundaries.

This is a curated NgAutoPilot gateway skill for npx skills, Pi, and other broad discovery surfaces. It deliberately presents one capability boundary instead of hundreds of canonical micro-skills.

Workflow

1. Inspect the receiving repository before proposing changes.
2. Detect Angular, Node.js, TypeScript, RxJS, package-manager, test, and workspace evidence relevant to the task.
3. Read references/index.md and choose the narrowest route for the task.
4. For Angular upgrades, move one supported major hop at a time and keep modernization separate until the hop is stable.
5. Apply compatibility and risk gates before editing.
6. Make the smallest reversible change.
7. Run the receiving repository's real validation commands and report evidence, failures, and residual risk.

Routes represented by this gateway

Source packs:

• ngautopilot-quality
• ngautopilot-typescript
• ngautopilot-javascript
• ngautopilot-css

Every canonical procedure selected by this gateway is included locally under references/skills/. No second installer is required. External source citations and optional repository documentation links provide further reading; the procedures themselves are installed files.

Progressive disclosure

• Start with references/index.md; it links to the exact local references/skills/<id>/procedure.md needed.
• Those procedures are full copies of the canonical source, not pointers to another repository.
• Activate only the single appropriate procedure or Angular major hop; never load all referenced files into context.
• If the route requires a specialist, consult references/agents/ and references/agents/prompts/ when present.
• Do not load unrelated capability families merely because they are installed.

Safety

• Do not guess framework compatibility.
• Do not install dependencies unless the task requires them and the receiving project approves the change.
• Do not mix unrelated refactors with upgrade work.
• Do not claim validation that was not executed.
• Treat generated guidance as assistance, not as a replacement for tests, review, or security gates.

Expected output

Return the selected route, compatibility/risk notes, changed files, validation commands and results, and any remaining blockers.