skills.rest
skylarsabo
skylarsaboCOMMUNITY
Explore all skills by this author →
GitHub

quality-scan

Detect and document defect-causing code issues with tiered evidence findings.

Updated Jun 22, 2026
Search Tags:#code quality#quality control#issue tracking#bug detection#defect analysis
One-click install
npx skills add https://github.com/skylarsabo/code-ops --skill quality-scan-skylarsabo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-scan
Source: https://github.com/skylarsabo/code-ops/tree/main/plugins/rigor/skills/quality-scan
Command: npx skills add https://github.com/skylarsabo/code-ops --skill quality-scan-skylarsabo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill finds and documents real, defect-causing quality issues in code, ensuring high-quality software development with evidence and tiered findings.

Core Features & Use Cases

  • Quality Assessment: Identifies issues like complexity hotspots, error-handling gaps, resource leaks, type-safety holes, and fragile coupling.
  • Evidence Tiers: Provides tiered findings with impact, reachability, and disconfirmation pass for each issue.
  • Quick Start: Use the /rigor:quality-scan command to start the quality scan on your codebase.

Quick Start

Invoke the quality scan on your codebase with the command: /rigor:quality-scan.

Frequently Asked Questions about quality-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect defect-causing code quality issues in my codebase?▼

A quality scan identifies defect-causing issues like complexity hotspots, error-handling gaps, resource leaks, and fragile coupling by applying verification-first quality control to your codebase.

What is the best way to track bug detection findings with evidence tiers?▼

The best way to track bug detection findings is to use a tiered system that documents each issue with impact analysis, reachability, and a disconfirmation pass for verification-first quality control.

Do I need a defined toolchain and ground-truth for defect analysis?▼

Yes, accurate defect analysis requires a codebase with a defined toolchain and ground-truth data to ensure verification-first quality control and precise identification of defect-causing issues.

How does a quality scan handle type-safety holes and resource leaks?▼

A quality scan handles type-safety holes and resource leaks by documenting them as tiered findings, providing impact analysis, reachability metrics, and a disconfirmation pass for each detected issue.

When should I not use automated quality control for issue tracking?▼

You should avoid automated quality control for issue tracking if your codebase lacks a defined toolchain or ground-truth data, as accurate defect analysis depends on these verification-first prerequisites.

Related Skills

Explore More Software Engineering Skills→
skylarsaboskylarsabo

ground-truth

Run a toolchain to capture ground truth and coverage maps.

Community
Advanced
sumilee-pcusumilee-pcu

tech-debt

Scan source code for TODOs and complexity hotspots to manage technical debt.

Community
Intermediate
summarybotngsummarybotng
2

QE Defect Intelligence

Predict defect-prone code and analyze root causes from historical defects.

Official
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced