Skip to main content
AI/MLparcadei

qlty-during-development

QLTY During Development

Stars
3,795
Source
parcadei/Continuous-Claude-v3
Updated
2026-01-26
Slug
parcadei--Continuous-Claude-v3--qlty-during-development
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/parcadei/Continuous-Claude-v3/HEAD/.claude/skills/qlty-during-development/SKILL.md -o .claude/skills/qlty-during-development.md

Drops the SKILL.md into .claude/skills/qlty-during-development.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

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:

  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)