inconsistency-scan

Name: inconsistency-scan
Availability: InStock
Author: Startale

Scan TypeScript/JavaScript source files for coding rule violations and generate a prioritized report.

3|3|Updated Aug 19, 2025

Search Tags:#typescript #linting #e2e #code-quality #static-analysis #code-standards

Ready to run

npx skills add https://github.com/StartaleGroup/app-sdk --skill inconsistency-scan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: inconsistency-scan
Source: https://github.com/StartaleGroup/app-sdk/tree/main/.claude-lib/shared/skills/inconsistency-scan
Command: npx skills add https://github.com/StartaleGroup/app-sdk --skill inconsistency-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full codebase consistency scan. Checks all hand-written source files against project coding rules for style, pattern, and quality violations. Excludes auto-generated files and node_modules. Use periodically (e.g. before a release or after onboarding new team members) to catch drift from project standards.

Core Features & Use Cases

Scan targets: src/ application source code
e2e/ end-to-end test specs, page objects, and helpers
Always exclude auto-generated paths such as api/, api-zod/, data-api/, data-api-zod/
Produce a prioritized, actionable report with known rule exceptions respected

Quick Start

Run the inconsistency-scan to generate a prioritized report of coding violations across the codebase.

Frequently Asked Questions about inconsistency-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I scan my TypeScript codebase for coding standard violations?▼

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.

What's the best way to check e2e test files for consistency with project coding rules?▼

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.

Does the codebase consistency scan work with auto-generated API files?▼

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.

How does static analysis identify inconsistencies in JavaScript source files?▼

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.

When should I run a full codebase consistency scan for code quality?▼

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.

Can I define custom coding rules for static analysis of my TypeScript project?▼

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.