skills.rest
VidyaBodepudi
VidyaBodepudiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review-and-quality

Enforce a two-stage code review for spec compliance and quality.

2|Updated Apr 13, 2026
Search Tags:#testing#quality assurance#code review#security#spec compliance
One-click install
npx skills add https://github.com/VidyaBodepudi/Code-Skills --skill code-review-and-quality-vidyabodepudi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/VidyaBodepudi/Code-Skills/tree/main/skills/code-review-and-quality
Command: npx skills add https://github.com/VidyaBodepudi/Code-Skills --skill code-review-and-quality-vidyabodepudi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires test-driven-development, and includes scripts (resource) components.

What problem does it solve?

This Skill ensures code changes meet both functional requirements (spec compliance) and quality standards (correctness, security, performance, etc.) through a structured two-stage review process.

Core Features & Use Cases

  • Stage 1: Spec Compliance - Verifies code implements the documented requirements and acceptance criteria.
  • Stage 2: Code Quality - Checks for correctness, test coverage, readability, security, performance, and consistency.
  • Use Case: Use during PR reviews, after subagent code completion, or before merging code changes to catch errors and enforce coding standards.

Quick Start

Use the code-review-and-quality skill to review the code changes in the current branch against the specified Pull Request.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
How do I check code changes for spec compliance and code quality before merging?▼

A two-stage code review process enforces both spec compliance and code quality by first verifying code implements documented requirements, then checking correctness, security, performance, and test coverage before merging.

Can I use a structured checklist to review subagent output for production readiness?▼

Yes, reviewing subagent output for production readiness involves applying a structured checklist of quality attributes to ensure the generated code meets functional requirements, security standards, and performance expectations.

What is the best way to automate pull request reviews for security and test coverage?▼

The best way to automate pull request reviews for security and test coverage is a two-stage review process that first validates spec compliance, then systematically checks code quality attributes like security, test coverage, and performance.

Do I need test-driven development to perform a two-stage code review?▼

Yes, test-driven development is a required prerequisite for performing the two-stage code review, as it provides the foundational testing framework needed to evaluate test coverage and correctness during the code quality stage.

When should I not use a two-stage code review process for code changes?▼

A two-stage code review process should not be used when code changes lack documented requirements or acceptance criteria, as the spec compliance verification stage depends entirely on having a specification to check against.

Related Skills

Explore More Software Engineering Skills→
cabeznocabezno

subagent-driven-development

Coordinate fresh delegate_task subagents for plan-driven implementation with two-stage review.

Community
Advanced
Clawdi-AIClawdi-AI
4

merge-pr

Merge GitHub pull requests via squash after validating checks and branch status.

Official
Advanced
ThrookieThrookie
2

code-review

Guide pull request reviews with a structured, rule-based evaluation checklist.

Community
Advanced
AlexiosBluffMaraAlexiosBluffMara
2

subagent-driven-development

Dispatch a fresh subagent per task with two-stage reviews.

Community
Advanced