Diagnose ESLint and TypeScript errors in the AFENDA-NEXUS monorepo.
npx skills add https://github.com/pohlai88/AFENDA-NEXUS2 --skill lint-types-debug
Please help me install this Agent Skill. Skill: lint-types-debug Source: https://github.com/pohlai88/AFENDA-NEXUS2/tree/main/.agents/skills/lint-types-debug Command: npx skills add https://github.com/pohlai88/AFENDA-NEXUS2 --skill lint-types-debug
This Skill helps developers quickly diagnose and resolve ESLint and TypeScript errors within the AFENDA-NEXUS monorepo, ensuring code quality and adherence to strict standards.
noUncheckedIndexedAccess, exactOptionalPropertyTypes, and project references.pnpm lint command fails with obscure errors, use this Skill to pinpoint the exact configuration or type issue and apply the correct fix according to AFENDA-NEXUS best practices.Use the lint-types-debug skill to diagnose why pnpm lint is failing in the packages/crud directory.
High-intent search queries and answers about installing and using this skill.
Resolve TypeScript strict mode failures by diagnosing specific compiler options like `noUncheckedIndexedAccess` and `exactOptionalPropertyTypes`, ensuring project references are correctly configured within the monorepo.
Your `pnpm lint` command fails due to misconfigured ESLint flat config or TypeScript project references; pinpoint the exact configuration issue and apply the correct fix to resolve type checking failures.
TypeScript project reference configuration failures during linting are caused by incorrect path mappings or strict compiler options, requiring validation of reference structures to ensure proper type checking across packages.
Resolve `noUncheckedIndexedAccess` and `exactOptionalPropertyTypes` errors in strict mode by adjusting type definitions and applying strict TypeScript compiler options according to monorepo best practices.
Yes, you can use ESLint flat config with TypeScript strict mode in a monorepo setup by validating the configuration structure and ensuring project references align with strict compiler options.
Limitations of debugging lint and type errors across monorepo packages include complex dependency chains and strict mode compiler options that require understanding ESLint flat config and TypeScript project referencing to resolve.
pohlai88Configure scalable ESLint rules for pnpm/Turborepo monorepos with typed linting and CI boundaries enforcement.
QunnnnRun Dart static analysis and apply automated lint fixes.
Mte90Configure ESLint, Prettier, Jest, and build tools for TypeScript projects.
dotBeepsRun tsc and ESLint to detect, interpret, and prioritize TypeScript errors.