mcpField
Q
qlty-during-development

qlty-during-development

github.com/parcadeiTesting & quality3.9k483 installsUpdated 39w ago
Repository

About qlty-during-development

qlty-during-development is a coding skill for running QLTY checks while writing code. It recommends checking changed files and formatting after substantial edits, rather than during exploration or small typo fixes.

Key features

  1. 01Run QLTY checks on changed files
  2. 02Format code with qlty fmt
  3. 03Check after substantial edits
  4. 04Defer checks during exploration

Use cases

  1. 01Linting a newly completed file
  2. 02Checking edits before a commit
  3. 03Formatting code after implementation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill qlty-during-development

After installing, type/qlty-during-developmentin Claude Code to confirm it loaded.

Details

From the project README

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)

Comments

Markdown supported