clean-code

To automatically format and lint changed files, you can run a post-implementation cleanup that detects your project's configuration and applies the corresponding formatter and lint commands. This ensures newly implemented code is reformatted and statically checked to maintain repository style.

Yes, code formatting works with both Prettier and Biome. The skill runs Prettier when supported, otherwise it automatically runs Biome formatting if a `biome.json` configuration file is present in the repository.

Yes, you can apply ESLint autofixes when an ESLint config exists. If ESLint is absent, the skill falls back to TypeScript type-checking via `tsc --noEmit` when only a `tsconfig.json` file is available.

The best way to format a Prisma schema is to run a cleanup workflow that specifically targets `prisma/schema.prisma`. This applies dedicated schema formatting to keep your database schema style consistent across updates.

Post-implementation code cleanup detects which tools to run by checking for conditional configuration files in the repository. It looks for Prettier, Biome, ESLint, or `tsconfig.json` files and executes the matching formatter and lint commands.

Yes, the limitation of running static checks on changed files is that the scope is intentionally limited. This prevents touching unrelated code and keeps reviews focused, but it means pre-existing lint issues outside the changed files will remain unresolved.