parcadei/continuous-claude-v3

qlty-during-development

QLTY During Development

First seen Jan 22, 2026

Installation

$ npx skills add parcadei/continuous-claude-v3 --skill qlty-during-development

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from parcadei/continuous-claude-v3 · top by installs.

npx skills add parcadei/continuous-claude-v3

Browse all from parcadei/continuous-claude-v3

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 3.9K
License LICENSE
Default branch main
Open issues 30
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 815 B
  • docs SUMMARY.md 51 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 476 installs

SKILL.md

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)