mcpbeat

Qlty During Development

parcadei/qlty-during-development

QLTY During Development

203 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3880
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill qlty-during-development

The instruction itself

5 sections, as written by the author

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 check on changed files
  • If errors, fix them before proceeding
  • 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)

How to use it

Copy the folder

Take parcadei/qlty-during-development from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.