code-review-and-quality

Runs a nine-check quality gate on code-complete slices before QA invocation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces a consistent, non-negotiable quality bar on every completed code slice, catching pattern drift, security gaps, scope creep, and unmet quality contract requirements before the slice reaches QA. ## Core Features & Use Cases - Nine-check quality gate: Validates pattern compliance, data sourcing, expandability, cleanliness, scope discipline, documentation, stack compliance, quality contract adherence, and security on every slice. - Class-based security checks: Runs baseline security checks (input sanitization, injection prevention, secrets exposure) plus targeted checks for Personal, Financial, Authentication, Multi-tenant, Confidential, and Regulated data classes. - Figma design fidelity check: For Figma-sourced slices, verifies the interactive element inventory, element completeness, classification honoring, and traceable visual values. - Use Case: After a build marks slice SL-12 code-complete, the gate reads its four anchors and quality contract from the backlog, runs all checks, and either logs the pass and triggers QA or returns the slice to In Build with specific failure notes. ## Quick Start Run the code review quality gate on slice SL-12 now that it is marked code-complete.

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 run a code review quality gate on a completed slice?

The gate triggers automatically when the build marks a slice code-complete; it is never invoked manually. It reads the slice's four anchors and quality contract from the backlog, runs all nine checks, and reports pass or fail per check.

What checks does an automated code review gate include?

It covers pattern compliance, data sourcing to the mock layer, expandability, cleanliness, scope discipline, documentation, stack compliance against tech-context, quality contract line-by-line verification, and security. Figma-sourced slices also get a design fidelity check.

What security checks run on code that handles personal or financial data?

Baseline checks cover input sanitization, data scoping, server-side auth, injection prevention, and secrets exposure. Personal class adds PII logging, encryption at rest, and deletion paths; Financial adds raw card data bans, access logging, and retention enforcement.

What happens when a slice fails the code review gate?

Each failed check returns a specific note naming the problem and required fix. The slice status returns to In Build, QA is not invoked, and a failure signal is appended to the session signals file.

When is the Figma design fidelity check skipped?

The check is skipped when the slice's design anchor does not reference a Figma file, and the report marks it as N/A. For Figma-sourced slices, it verifies the interactive element inventory, element completeness, classification honoring, and traceable visual values.