qa-full-review

Name: qa-full-review
Availability: InStock
Author: Grig

Map code features to UI elements and verify system behavior.

4|Updated Dec 7, 2025

Search Tags:#automation #testing #qa #verification #quality-assurance #code-review

Ready to run

npx skills add https://github.com/grigb/gas-prompt-library --skill qa-full-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-full-review
Source: https://github.com/grigb/gas-prompt-library/tree/main/agents/agent-qa-full-review
Command: npx skills add https://github.com/grigb/gas-prompt-library --skill qa-full-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the lack of systematic, repeatable quality assurance in software development by providing a rigorous framework for code analysis and interactive UI testing.

Core Features & Use Cases

Comprehensive QA Audits: Conducts end-to-end testing including code traceability, behavioral analysis, and UI interaction verification.
Automated Defect Documentation: Generates standardized, enterprise-ready issue reports with evidence-based screenshots and root cause analysis.
Use Case: Use this agent to perform a full pre-release audit of a web application, ensuring all interactive elements, API endpoints, and navigation paths function correctly before deployment.

Quick Start

Invoke the qa-full-review agent to perform a comprehensive quality assurance audit of the current project codebase and user interface.

Frequently Asked Questions about qa-full-review

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

FAQPage Schema

How do I perform a pre-release quality assurance audit for a web application?▼

A pre-release quality assurance audit maps code features to interactive UI elements, verifying system behavior through browser interaction and CLI code analysis to validate functionality before deployment.

What is code traceability and how does it verify UI behavior?▼

Code traceability maps backend code features to interactive UI elements, verifying that system behavior functions correctly through rigorous testing and browser-based interaction analysis.

How do I automate defect documentation with root cause analysis?▼

Automated defect documentation generates standardized, enterprise-ready issue reports featuring evidence-based screenshots and root cause analysis derived from systematic code and UI verification.

Do I need browser-based interaction tools and CLI access for QA testing?▼

Yes, browser-based interaction tools and CLI access are required to perform code analysis, backend verification, and interactive UI testing during the quality assurance review.

Can I use this for end-to-end testing of API endpoints and navigation paths?▼

End-to-end testing of API endpoints and navigation paths is supported by conducting comprehensive QA audits that verify interactive elements and backend functionality before release.

What are the limitations of automated code and UI integrity verification?▼

Limitations include reliance on browser-based interaction tools and CLI access for execution, meaning environments lacking these interfaces cannot perform the required code analysis and backend verification.