Set up strict TypeScript/JavaScript linting with Oxlint, dprint, jscpd, and knip via Gatefile.
npx skills add https://github.com/pyronaur/ngents --skill ts-lint-setup
Please help me install this Agent Skill. Skill: ts-lint-setup Source: https://github.com/pyronaur/ngents/tree/main/skills/ts-lint-setup Command: npx skills add https://github.com/pyronaur/ngents --skill ts-lint-setup
Set up or upgrade strict TypeScript/JavaScript linting with Oxlint (type-aware), dprint (formatter), jscpd (0% duplication), and knip, routed through gate. Use when a repo needs lint tooling installed, Gatefile validation wired, or lint configuration standardized without silencing rules.
This skill provides a standardized, maintainable baseline for linting across TypeScript/JavaScript projects. It coordinates installation of lint tooling, Gatefile integration for policy control, and the application of shared configuration templates (dprint.json, .oxlintrc.json, .jscpd.json, .jscpd.tests.json, knip.json). It enables consistent lint policy enforcement and delta reporting when comparing repos to the skill, including rule presence/absence, rule values, custom messages, duplication thresholds, and coverage. It emphasizes safe, non-disruptive wiring and clear governance for lint-related changes.
Follow the workflow to install lint tooling, update Gatefile entries, copy templates, wire lint through Gatefile, and validate with gate.
High-intent search queries and answers about installing and using this skill.
To set up strict TypeScript linting, this skill installs Oxlint, dprint, jscpd, and knip, then wires them through Gatefile to enforce standardized configuration policies without silencing rules.
Enforcing zero code duplication requires configuring jscpd with a strict threshold. This skill applies standardized .jscpd.json configuration templates routed through Gatefile to validate JavaScript repositories.
Integrating lint configuration into a Gatefile involves adding validation entries for your tooling. This skill wires Oxlint, dprint, jscpd, and knip through Gatefile references to control policy enforcement.
No, this strict linting setup does not silence TypeScript rules. It applies standardized baseline configurations using Oxlint and knip to enforce policy without disrupting existing project governance.
Yes, you can use knip alongside Oxlint. This skill coordinates the installation of both tools, applying shared knip.json configurations to detect unused code while Oxlint handles type-aware linting.
A TypeScript linting baseline modifies package.json, Gatefile references, and shared configuration templates like .oxlintrc.json and dprint.json to apply standardized lint policies across projects.
maxenergyAutomate Husky pre-commit hook setup with lint-staged and Prettier for JavaScript/TypeScript projects.
parisgroup-aiEnforce code coverage thresholds and generate structured diagnosis reports.
zcaceresDetect dead code, duplicate logic, and circular dependencies with knip, jscpd, and madge.
samChang72Automate linting and static analysis for Node.js and Python projects.
