npx skills add smithery/parcadei --skill qlty-during-development
parcadei/continuous-claude-v3
qlty-during-development
QLTY During Development
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.
This skill should be used when the user asks to "create an agent", "add an agent", "write a sub…
18.1K installsThis skill should be used when the user wants to "create a skill", "add a skill to plugin", "wr…
18K installsThis skill should be used when the user asks to "create a slash command", "add a command", "wri…
13.5K installsThis skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/…
13.2K installsDevelop, debug, and deploy Apify Actors - serverless cloud programs for web scraping, automatio…
10.3K installsThis skill should be used when the user asks to "create an agent", "add an agent", "write a sub…
6.2K installsAlso in this package
Other skills from parcadei/continuous-claude-v3 · top by installs.
npx skills add 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.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md815 B -
docs
SUMMARY.md51 B
History
- First seen on skills.sh
- 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:
- Run
qlty checkon changed files - If errors, fix them before proceeding
- Run
qlty fmtto 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)