Overview

QLTY During Development runs checks as you write code to detect issues early. It emphasizes running after significant changes, before commits, and provides quick commands to lint, format, and auto-fix issues.

How This Skill Works

As you write code, run qlty check on the changed files. If issues are found, fix them before proceeding, then run qlty fmt to ensure consistent formatting. You can target specific files and use --fix to auto-correct problems.

When to Use It

• After completing a new file
• After substantial edits to existing files
• Before committing changes
• When validating a batch of changes for lint and style
• When preparing code for a code review or PR

Quick Start

1. Step 1: Run qlty check on changed files
2. Step 2: If errors exist, fix them before proceeding
3. Step 3: Run qlty fmt to ensure formatting

Best Practices

• Run qlty check on changed files after edits to catch issues early
• If issues are found, fix them before proceeding to avoid compounding problems
• Run qlty fmt after fixes to ensure consistent formatting
• Use qlty check with a specific path when you know where issues may exist (e.g., qlty check src/sdk/providers.ts)
• Avoid running during exploration or mid-refactor; run at the end of a development session before commit

Example Use Cases

• Create a new module in src/sdk/providers.ts and run qlty check on the changed file
• Make substantial edits to a file, run qlty check, fix errors, then run qlty fmt
• Before committing, run qlty check on all changed files and then qlty fmt
• Test a specific file by running qlty check src/sdk/providers.ts to focus on a suspected area
• Run qlty check --fix to auto-fix issues before opening a PR

Frequently Asked Questions