qlty-during-development
SolidQLTY During Development
AI & Automation 501 stars
42 forks Updated yesterday MIT
Install
Quality Score: 90/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# 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
```bash
# 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)
Details
- Author
- vibeeval
- Repository
- vibeeval/vibecosystem
- Created
- 2 months ago
- Last Updated
- yesterday
- Language
- C#
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Listed
qlty-during-development
QLTY During Development
3,809 Updated 4 months ago
parcadei AI & Automation Solid
qlty-check
Code quality checks, formatting, and metrics via qlty CLI
501 Updated yesterday
vibeeval AI & Automation Solid
qlty-check
Code quality checks, formatting, and metrics via qlty CLI
3,809 Updated 4 months ago
parcadei