inconsistency-scan

To scan a TypeScript codebase for coding standard violations, run a full consistency scan against your project rules. It checks hand-written source files in src/ and e2e/ directories while ignoring auto-generated paths and node_modules to produce a prioritized report.

Checking e2e test files for consistency involves scanning end-to-end test specs, page objects, and helpers against your defined project coding rules. The scan targets the e2e/ directory specifically to identify style and pattern violations while excluding generated artifacts.

The codebase consistency scan explicitly excludes auto-generated API files. It automatically ignores paths such as api/, api-zod/, data-api/, and data-api-zod/ to ensure the report focuses only on hand-written source code violations.

Static analysis identifies inconsistencies in JavaScript source files by parsing the repository and checking hand-written code against rules defined in .claude/rules. It focuses on readability and maintainability violations, respecting intentional rule exceptions in the final prioritized report.

You should run a full codebase consistency scan for code quality periodically, such as before a release or after onboarding new team members. This timing catches drift from project standards early by identifying style and pattern violations across hand-written files.

You can define custom coding rules for static analysis by placing them in the .claude/rules directory. The inconsistency scan relies on these specific rules to identify violations and generate a prioritized, actionable report tailored to your project standards.