qlty-during-development
QLTY During Development
When & Why to Use This Skill
The QLTY During Development skill is an automated code quality and static analysis tool designed to catch programmatic issues and stylistic inconsistencies in real-time. By integrating linting and formatting directly into the coding workflow, it helps developers maintain high-quality standards, reduce technical debt, and ensure code reliability before the peer review or commit stage.
Use Cases
- Real-time Error Detection: Run 'qlty check' immediately after writing a new file to identify syntax errors or potential bugs before they propagate.
- Automated Style Enforcement: Use 'qlty fmt' to automatically format code according to project standards, ensuring a consistent codebase across the team.
- Pre-Commit Quality Gate: Execute targeted checks on modified files (e.g., 'qlty check src/sdk/providers.ts') to validate changes before pushing to version control.
- Rapid Issue Resolution: Leverage the 'qlty check --fix' command to automatically resolve common linting warnings and formatting issues without manual editing.
| name | qlty-during-development |
|---|---|
| description | QLTY During Development |
| user-invocable | false |
QLTY During Development
Run QLTY checks during code writing to catch issues early.
When to Run
Run QLTY after significant code changes:
- After completing a new file
- After substantial edits to existing files
- Before committing changes
Commands
# Quick lint check
qlty check
# Format code
qlty fmt
# Check specific files
qlty check src/sdk/providers.ts
# Auto-fix issues
qlty check --fix
Integration Pattern
After writing code:
- Run
qlty checkon changed files - If errors, fix them before proceeding
- Run
qlty fmtto ensure formatting
Don't Run When
- Just reading/exploring code
- Making single-line typo fixes
- In the middle of multi-file refactoring (run at end)