Best use case
qlty-during-development is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
QLTY During Development
Teams using qlty-during-development should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/qlty-during-development/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How qlty-during-development Compares
| Feature / Agent | qlty-during-development | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
QLTY During Development
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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)
Related Skills
skill-development
Skill Development Rules
qlty-check
Code quality checks, formatting, and metrics via qlty CLI
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
variant-analysis
Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.
validate-agent
Validation agent that validates plan tech choices against current best practices
tracing-patterns
OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries
tour
Friendly onboarding tour of Claude Code capabilities for users asking what it can do.