code-quality

You can automate TypeScript typecheck, lint, and formatting in CI pipelines by invoking the finalize script to run quality gates. This skill relies on Bun and standard TypeScript tooling to catch type errors, style issues, and Markdown problems before they reach pull requests.

Yes, you can use Bun to run ESLint and Prettier checks for local development. The skill automates these checks locally and supports pre-commit hooks, applying Prettier auto-fixes in agent mode to enforce consistent code formatting.

The best way to enforce code quality gates for TypeScript and Markdown files is to automate type checking, linting, formatting, and Markdown validation. This skill targets local development and CI pipelines to ensure consistent quality across small to large codebases.

Yes, this code quality automation works with pre-commit hooks. It targets local development environments and CI pipelines, running typecheck, lint, and format checks to gate PRs and maintain high-quality code before changes are committed.

Markdown validation fails on trailing whitespace during lint checks because the skill enforces strict Markdown structure and quality rules. It identifies formatting issues and validates documentation to prevent structural problems from reaching your repository.

Yes, you need Bun installed to run TypeScript type checking and linting. The skill explicitly relies on Bun and standard TypeScript tooling to execute typecheck, lint, and format checks across your project codebase.