tpo-code-ux-qa-review-checklist

Reviews AI developer output against code, UX, QA, and security checklists.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-code-ux-qa-review-checklist-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tpo-code-ux-qa-review-checklist
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/tpo-code-ux-qa-review-checklist
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-code-ux-qa-review-checklist-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing AI-generated code and features often lacks structure, leading to inconsistent decisions, missed security issues, and vague feedback. This Skill provides a single combined checklist so every review ends with a clear decision and documented findings. ## Core Features & Use Cases - Structured Review Decisions: Every review concludes with Approved, Approved with fixes, Needs revision, Blocked, or Rejected, plus an acceptance gate. - Multi-Domain Checklists: Covers requirement fit, code structure and error handling, UX/UI and accessibility, QA test coverage, and security (secrets, auth, input validation, rate limiting). - Issue Severity Table: Standardized template for logging issues by severity, area, impact, and required fix. - Use Case: A technical product owner receives a completed feature from an AI developer agent and uses this checklist to verify acceptance criteria, flag a hardcoded token as a blocker, and return a structured Needs revision decision with required fixes. ## Quick Start Review the attached feature implementation using the code, UX, QA, and security review checklist and give me a decision with an issue table.

Frequently Asked Questions about tpo-code-ux-qa-review-checklist

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

FAQPage Schema
How do I review AI-generated code before approval?

Use a structured checklist covering requirement fit, code structure, error handling, security, and test coverage. End every review with an explicit decision such as Approved, Needs revision, or Blocked, plus an issue table with severity and required fixes.

What should a code review checklist include?

A complete checklist covers requirement fit, code structure and maintainability, error handling, configuration and secrets, UX flow and accessibility, QA test coverage, and security checks for authentication, input validation, and rate limiting.

How do I decide between approved and needs revision in a review?

Approve only when all acceptance criteria pass, no blocker or high issues remain, and tests and security gates pass. Use Needs revision when required behavior is missing, key tests are absent, or medium and high issues require developer work.

What security checks should block a release?

Block releases when API keys or tokens are committed, credentials appear in logs, authentication or object-level authorization is missing, or input validation is absent. Secrets must come from environment variables and sample env files must not contain real values.

What are the limitations of checklist-based reviews?

Checklists standardize coverage but cannot replace running the application or executing tests. Manual QA on staging, verifying the main user flow, and confirming test results are still required before final approval.