cleanup

Run code quality checks by executing sequential frontend, backend, and styling compliance passes across your specified scope. This process catches React hooks issues, Python ruff linting errors, and TypeScript type inconsistencies before review.

Yes, you can automatically fix issues during a pre-release check by enabling the fix option. The cleanup process applies fixes sequentially across React hooks, Python ruff, and TypeScript tsc passes, then outputs an end-to-end summary of proposed and applied changes.

A React hooks audit flags unnecessary or harmful patterns such as redundant effects, overly-cautious memoization, and missing React Query usage for server state. This ensures your frontend code follows standardized conventions before shipping.

Yes, this code quality tool enforces design token usage, Tailwind-local styling, and consistent logger usage instead of print or console.log. It also checks import conventions to ensure Python absolute imports and TypeScript frontend aliases are used correctly.

The best way to ensure TypeScript tsc type checking and Python ruff linting pass is to run sequential code quality gates across your changes. This validates style and correctness while enforcing import conventions and logging compliance.

Running sequential compliance checks instead of individual linters prevents risky merges by ensuring the repo's core checks execute in the correct order. This coordinated approach catches React Query, design token, and logger consistency issues that isolated linters might miss.