Audit changed files with a dual-pass QA review and severity-tiered findings.
npx skills add https://github.com/ejoliet/claude-skills --skill qa-ejoliet
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
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.
Run the QA pass on your latest session changes to surface issues before merging.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
netteValidate commit messages against a standardized format before commits.
synaptiaiEnforce file:line citations for code review claims with P1/P2/P3 prioritization.
Ramprasad4121Prepare codebases for security review with static analysis and documentation.
Codagent-AIResolve CI failures and review comments on GitHub pull requests.
