quality-scan

Analyze the socket-btm monorepo for code quality risks across packages.

3|1|Updated Nov 8, 2025
One-click install
npx skills add https://github.com/SocketDev/socket-btm --skill quality-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-scan
Source: https://github.com/SocketDev/socket-btm/tree/main/.claude/skills/quality-scan
Command: npx skills add https://github.com/SocketDev/socket-btm --skill quality-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated, end-to-end quality scanning of the socket-btm codebase by coordinating specialized AI agents to detect critical bugs, logic errors, caching issues, and workflow problems before releases or incident investigations.

Core Features & Use Cases

  • Agent-driven analysis: Spawns distinct agents to cover critical, logic, cache, and workflow perspectives and aggregates results.
  • Prioritized findings: Produces a consolidated, severity-ordered report with actionable fixes and file references.
  • Partial scans: Allows running only selected scan types to fit CI time or risk tolerance.
  • Before-release validation: Use as part of release gates to catch regressions in code quality.
  • Audit-ready output: Generates both human-readable reports and structured data for integration into ticketing systems.

Quick Start

Run the quality scan against the repository root to begin.

Frequently Asked Questions about quality-scan

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

FAQPage Schema
How do I automate code quality scans for a monorepo before release?

Partial monorepo quality scans allow running only selected scan types—critical, logic, cache, or workflow—to fit CI time constraints or risk tolerance. This selective approach prevents CI bottlenecks while maintaining essential risk coverage.

How does agent-driven code analysis identify logic and caching issues?

Agent-driven analysis spawns distinct autonomous agents to evaluate code from critical, logic, cache, and workflow perspectives. It aggregates these specialized findings into a consolidated, severity-ordered report with file references and actionable fixes.

Can I generate structured code quality reports for CI pipelines?

Code quality scans generate both human-readable reports and structured data suitable for CI pipelines and ticketing system integration. This audit-ready output includes severity prioritization, file:line references, and scan coverage metrics.

What is the best way to run partial quality scans to fit CI time limits?

Running selective quality scans allows targeting only critical, logic, cache, or workflow issues to fit CI time limits. You can adjust scan coverage based on risk tolerance while still receiving prioritized findings with file:line references.