scan-stylistic

To find refactoring opportunities for inconsistent TypeScript code styles, scan your codebase against team preferences like early returns and readonly boundaries. This process analyzes your repository to flag stylistic inconsistencies and generates a prioritized backlog of high-value changes.

Common stylistic refactoring rules for React and Hono codebases include using early returns, enforcing readonly boundaries, and ensuring exhaustive unions. Applying these rules improves readability and maintainability across API routes and UI components.

Yes, you can scan specific directories like apps/api/src and apps/web/src for code style issues. The scanning process applies repository-wide analysis to these paths and shared packages to identify targeted refactoring tasks based on your team's defined preferences.

You prioritize a TypeScript refactoring backlog by categorizing identified issues into high value, worth considering, and not worth it tiers. This approach outputs a document with file paths, current versus target code examples, and acceptance criteria to guide safe refactors.

Yes, code style scanning flags nested if/else blocks in API middleware. It scans routes and components to identify these patterns and suggests guard clauses to streamline error handling and improve overall code readability.