Qlty During Development
- 463 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
qlty-during-development is an agent skill that runs QLTY lint and format checks after significant code changes during development for developers who want early issue detection with qlty check and qlty fmt before committi
About
qlty-during-development is a Code Review & Quality skill from parcadei/continuous-claude-v3 (user-invocable: false) that integrates the QLTY CLI into the code-writing workflow. Agents run qlty check after completing new files or substantial edits, fix reported errors, then run qlty fmt for formatting— including targeted checks like qlty check src/sdk/providers.ts and auto-fix with qlty check --fix. The skill specifies when not to run checks to avoid noise on trivial edits. Developers reach for qlty-during-development when agents write code incrementally and need lint and format gates embedded in the development loop rather than only at CI time.
- qlty-during-development
Qlty During Development by the numbers
- 463 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #896 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill qlty-during-developmentAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 463 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
When should you run qlty check during development?
Use qlty-during-development for development tasks
Who is it for?
Developers using the QLTY CLI who want agents to lint and format code immediately after significant file changes instead of waiting for CI.
Skip if: Projects without QLTY configured or developers who only need pre-commit hooks without in-session agent lint integration should skip this skill.
When should I use this skill?
An agent completes a new file, makes substantial edits, or is about to commit and needs qlty check and qlty fmt run on changed files.
What you get
Lint-clean, formatted source files verified by qlty check and qlty fmt before commit.
- Lint-clean source files
- Formatted code output
By the numbers
- Uses 4 QLTY commands: qlty check, qlty fmt, qlty check <file>, qlty check --fix
Files
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 --fixIntegration 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)
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kFAQ
When should agents run qlty during development?
Agents should run qlty-during-development after completing a new file, after substantial edits to existing files, and before committing changes. The skill runs qlty check first, fixes errors, then applies qlty fmt for formatting.
What QLTY commands does the skill use?
qlty-during-development uses qlty check for linting, qlty fmt for formatting, qlty check on specific file paths, and qlty check --fix for auto-fixing issues. The skill also documents when not to run checks on trivial edits.