qa

Review current Git working tree changes with Codex and synthesize findings.

11|1|Updated Mar 3, 2026

Search Tags:#automation #git #qa #codex #diff #code-review

Ready to run

npx skills add https://github.com/SZoloth/skill-pack --skill qa-szoloth

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thorough QA on all changes in the current working tree using Codex as a second pair of eyes, ensuring issues are detected before they reach production.

Core Features & Use Cases

Gather diffs and status to show exactly what changed.
Build a concise context for Codex to review, then synthesize actionable findings.
Use on demand after implementation work or before commits to improve code quality.

Quick Start

Run the QA workflow on your current Git working tree to trigger a Codex-based review.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I automate code review on my git diff before committing?▼

Automate code review on your git diff by gathering working tree changes, building a concise context, and sending it to Codex for a structured QA synthesis. This process detects issues in your code changes before they reach production or your commit history.

What is the best way to run QA on uncommitted code changes?▼

Running QA on uncommitted changes involves collecting the git diff and status, constructing a 2-3 sentence context, and leveraging Codex as a second pair of eyes to synthesize actionable findings. It works on demand after implementation to improve code quality.

Can I use Codex to review my current working tree?▼

Yes, you can use Codex to review your current working tree by collecting the diff, building a short context, and sending it for a structured review. The tool synthesizes the findings into actionable feedback for your code.

Do I need to provide context for an automated diff review?▼

Yes, providing context is required for an automated diff review. You need to construct a concise 2-3 sentence context alongside the collected git diff so Codex can perform a structured review and synthesize accurate findings.

When should I run an automated QA workflow on my code?▼

You should run an automated QA workflow on your code after implementation work is complete or before committing changes. Running it on demand across the current working tree ensures issues are detected early by Codex.