Qlty During Development

by parcadeid07ff4b06b62No license3.9K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 months ago

QLTY During Development

Instructions onlySoftware Development
AI-generated overview

Guides running QLTY lint and format checks during code writing to catch issues early.

What it does
This skill instructs an agent on when and how to run QLTY checks while writing code. It lists commands for linting, formatting, checking specific files, and auto-fixing, and describes an integration pattern of checking changed files, fixing errors, then formatting. It also states situations where checks should not be run, such as reading code or mid-refactor.
When to use it
Use it after completing a new file, after substantial edits to existing files, or before committing changes. Avoid it when only reading or exploring code, making single-line typo fixes, or in the middle of multi-file refactoring.
Requirements
Requires the QLTY command-line tool to be installed and available; the skill itself contains instructions only and ships no scripts.

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

bash
# Quick lint checkqlty check
# Format codeqlty fmt
# Check specific filesqlty check src/sdk/providers.ts
# Auto-fix issuesqlty check --fix

Integration Pattern

After writing code:

  1. Run qlty check on changed files
  2. If errors, fix them before proceeding
  3. Run qlty fmt to 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)

Source and attribution

Source:parcadei/continuous-claude-v3in.claude/skills/qlty-during-developmentat commitd07ff4b

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal