explainx.ainewsletter3.4k
Productivity

qlty-check▌

parcadei/continuous-claude-v3 · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill qlty-check
0 commentsdiscussion
summary

Universal code quality tool supporting 70+ linters for 40+ languages via qlty CLI.

skill.md

Qlty Code Quality

Universal code quality tool supporting 70+ linters for 40+ languages via qlty CLI.

When to Use

  • Check code for linting issues before commit/handoff
  • Auto-fix formatting and style issues
  • Calculate code metrics (complexity, duplication)
  • Find code smells

Quick Reference

# Check changed files with auto-fix
uv run python -m runtime.harness scripts/qlty_check.py --fix

# Check all files
uv run python -m runtime.harness scripts/qlty_check.py --all

# Format files
uv run python -m runtime.harness scripts/qlty_check.py --fmt

# Get metrics
uv run python -m runtime.harness scripts/qlty_check.py --metrics

# Find code smells
uv run python -m runtime.harness scripts/qlty_check.py --smells

Parameters

Parameter Description
--check Run linters (default)
--fix Auto-fix issues
--all Process all files, not just changed
--fmt Format files instead
--metrics Calculate code metrics
--smells Find code smells
--paths Specific files/directories
--level Min issue level: note/low/medium/high
--cwd Working directory
--init Initialize qlty in a repo
--plugins List available plugins

Common Workflows

After Implementation

# Auto-fix what's possible, see what remains
uv run python -m runtime.harness scripts/qlty_check.py --fix

Quality Report

# Get metrics for changed code
uv run python -m runtime.harness scripts/qlty_check.py --metrics

# Find complexity hotspots
uv run python -m runtime.harness scripts/qlty_check.py --smells

Initialize in New Repo

uv run python -m runtime.harness scripts/qlty_check.py --init --cwd /path/to/repo

Direct CLI (if qlty installed)

# Check changed files
qlty check

# Auto-fix
qlty check --fix

# JSON output
qlty check --json

# Format
qlty fmt

Requirements

vs Other Tools

Tool Use Case
qlty Unified linting, formatting, metrics for any language
ast-grep Structural code patterns and refactoring
morph Fast text search
how to use qlty-check

How to use qlty-check on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add qlty-check
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill qlty-check

The skills CLI fetches qlty-check from GitHub repository parcadei/continuous-claude-v3 and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/qlty-check

Reload or restart Cursor to activate qlty-check. Access the skill through slash commands (e.g., /qlty-check) or your agent's skill management interface.

⚠

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.5★★★★★40 reviews
  • ★★★★★Min Patel· Dec 24, 2024

    qlty-check has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Chen Haddad· Dec 20, 2024

    qlty-check fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Ganesh Mohane· Dec 8, 2024

    qlty-check fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Isabella Shah· Dec 8, 2024

    qlty-check is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Shikha Mishra· Dec 4, 2024

    Useful defaults in qlty-check — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Sakshi Patil· Nov 27, 2024

    Registry listing for qlty-check matched our evaluation — installs cleanly and behaves as described in the markdown.

  • ★★★★★Xiao Flores· Nov 27, 2024

    Solid pick for teams standardizing on skills: qlty-check is focused, and the summary matches what you get after install.

  • ★★★★★Zara Khan· Nov 15, 2024

    Keeps context tight: qlty-check is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Emma Jackson· Nov 11, 2024

    Registry listing for qlty-check matched our evaluation — installs cleanly and behaves as described in the markdown.

  • ★★★★★Chaitanya Patil· Oct 18, 2024

    qlty-check reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 40

1 / 4