Codex .NET ESLint for React and TypeScript Frontends
Set up repository-owned semantic linting for JavaScript and TypeScript in a .NET workspace. Define the target folders and align local and CI checks.
中文Install in Codex
Codex with a .NET checkout containing Node frontend assets, its package.json, and existing TypeScript and ESLint settings.
- Copy the entire pinned `.codex/skills/dotnet-eslint/` directory to `.agents/skills/dotnet-eslint/` in the target checkout.
- Open Codex in that checkout and invoke `$dotnet-eslint` with the example task and desired output.
Example task
Invoke `$dotnet-eslint` to add a focused TSX lint command for a practice ClientApp. Ask it to verify existing generated-folder exclusions.What to check
The repository has a repeatable command and an explicit scope. Findings correspond to the intended source files.
Original SKILL.md on GitHub · Updated
Frequently asked question
Why read tsconfig first?
Check that the TypeScript project includes the target files before enabling rules that depend on type information.