qa

Audit changed files with a dual-pass QA review and severity-tiered findings.

Updated Apr 16, 2026

Search Tags:#security #qa #data-integrity #code-review #diff-review #software-testing

Ready to run

npx skills add https://github.com/ejoliet/claude-skills --skill qa-ejoliet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/ejoliet/claude-skills/tree/main/qa
Command: npx skills add https://github.com/ejoliet/claude-skills --skill qa-ejoliet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full QA pass on all session changes using a two-pass diff + file review with severity-tiered findings (P1/P2/P3). Covers correctness, security, data integrity, regressions, and completeness. Use after implementing a feature or fix to catch issues before pushing.

Core Features & Use Cases

Six-step dual-pass code review for all session changes.
Step-by-step guidance from gathering changes to synthesizing findings and proposing fixes.
Use Case: After implementing a feature or bug fix, run this QA pass to surface issues and confirm readiness for PR review.

Quick Start

Run the QA pass on your latest session changes to surface issues before merging.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I run a QA pass on code changes before merging a pull request?▼

To run a QA pass on code changes before merging, execute a six-step dual-pass diff and file review to surface severity-tiered P1/P2/P3 issues. This structured audit validates correctness, security, data integrity, and regressions to confirm production readiness.

What is a two-pass diff review for software testing?▼

A two-pass diff review for software testing is a structured QA mechanism that audits changed files twice to identify bugs. It enforces a standardized issue taxonomy to categorize findings by severity, ensuring correctness, security, and data integrity are validated before pushing.

How do I classify code review findings by severity for security and data integrity issues?▼

You classify code review findings by severity using a standardized P1/P2/P3 issue taxonomy. This audit framework prioritizes security vulnerabilities, data integrity flaws, and regressions, outputting actionable tiered findings for developers to address before merging.

When should I run a dual-pass code review during feature implementation?▼

You should run a dual-pass code review immediately after implementing a feature or bug fix and before pushing to production. This timing catches correctness, security, and regression issues early, generating actionable findings for PR review.

Does this QA review process work without external testing dependencies?▼

Yes, this QA review process works without external testing dependencies. It performs a structured audit of changed files directly from the session diff, applying a standardized issue taxonomy to surface P1/P2/P3 findings independently.

What is the best way to catch regressions and security issues before pushing to production?▼

The best way to catch regressions and security issues before pushing to production is a dual-pass QA review. It synthesizes findings from a structured file audit into actionable P1/P2/P3 fixes, addressing data integrity and completeness comprehensively.