qsd-code-review

Analyze phase-changed source files for bugs, security issues, and code quality problems.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/thecomputer07/qsd --skill qsd-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qsd-code-review
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-code-review
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review source files changed during a phase for bugs, security issues, and code quality problems.

Spawns the qsd-code-reviewer agent to analyze code at the specified depth level. Produces REVIEW.md artifact in the phase directory with severity-classified findings.

Core Features & Use Cases

  • Spawns a code-review agent to analyze diffs at quick, standard, or deep depth.
  • Supports phase-scoped reviews by focusing on changes in a given phase.
  • Optional file scoping via --files to target specific files; outputs a phase-level REVIEW.md with categorized findings.

Quick Start

Run the code-review workflow for the desired phase, providing the phase number and optional depth and files flags.

Frequently Asked Questions about qsd-code-review

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

FAQPage Schema
How do I automate code review for phase diffs to find bugs and security issues?

Code review for phase diffs analyzes changed source files to identify bugs, security issues, and quality problems. It spawns a reviewer agent that outputs a severity-classified REVIEW.md artifact in the phase directory.

What is phase-scoped static analysis and when do I need it?

Phase-scoped static analysis evaluates only the source files modified during a specific development phase. You need it to verify incremental code changes meet quality and security standards without reviewing the entire repository.

Can I target specific files instead of reviewing all changes in a phase?

Yes, you can target specific files using the optional files flag. This scopes the code quality review to only the explicitly defined files, outputting categorized findings in the phase-level REVIEW.md.

Does automated security review support different levels of analysis depth?

Automated security review supports quick, standard, and deep depth levels. You specify the desired depth when running the workflow to control the thoroughness of the bug, security, and quality analysis.

What is the best way to generate a REVIEW.md report for software quality findings?

Generating a REVIEW.md report for software quality is best handled by applying phase-wide code review automation. It analyzes phase diffs and outputs categorized findings with severity classifications into the artifact.

What are the limitations of phase-scoped code review for unchanged files?

Phase-scoped code review limits analysis strictly to files changed during the specified phase. Unchanged files are excluded from the security and quality review unless explicitly targeted using optional file scoping parameters.