qlty-during-development

Solid

QLTY During Development

AI & Automation 501 stars 42 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
38
Issue Health 10%
50
License 10%
100
Description 5%
100

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