qlty-during-development
Runs QLTY commands to format code and verify quality standards before commits.
Install
mkdir -p .claude/skills/qlty-during-development && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2358" && unzip -o skill.zip -d .claude/skills/qlty-during-development && rm skill.zipInstalls to .claude/skills/qlty-during-development
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
QLTY During DevelopmentKey capabilities
- →Run lint checks on code
- →Format source files
- →Check specific files for quality
- →Auto-fix style issues
How it works
The skill executes command-line tools to validate and reformat code based on defined quality rules.
Inputs & outputs
When to use qlty-during-development
- →Formatting code
- →Checking for quality regressions
- →Auto-fixing style issues
About this skill
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)
When not to use it
- →Reading or exploring code
- →Making single-line typo fixes
- →During multi-file refactoring
Limitations
- →Not suitable for complex refactoring tasks
How it compares
It automates the quality gate process directly within the development workflow instead of relying on manual checks.
Compared to similar skills
qlty-during-development side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| qlty-during-development (this skill) | 2 | 7mo | Review | Beginner |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| angular-best-practices | 21 | 3mo | No flags | Advanced |
| validate-typescript | 5 | 9mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by parcadei
View all by parcadei →You might also like
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
angular-best-practices
sickn33
Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.
validate-typescript
BerryKuipers
Run TypeScript compiler type-checking (tsc --noEmit) to validate type safety and catch type errors. Works with any TypeScript project. Returns structured output with error counts, categories (type/syntax/import errors), and affected files. Used for quality gates and pre-commit validation.
ts-testing
johnlindquist
Design, implement, and maintain high‑value TypeScript test suites using popular JS/TS testing libraries. Use this skill whenever the user is adding tests, debugging failing tests, or refactoring code that should be covered by tests.
react-best-practices
redpanda-data
Client-side React performance optimization patterns.
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.