AgentStack
SKILL verified MIT Self-run

Qa

skill-szoloth-skill-pack-qa · by SZoloth

Full QA on all session changes using Codex as a second pair of eyes. Use when user says "QA", "full QA", "QA my changes", "QA all your changes", or "use codex to review". Runs git diff, sends changes to Codex for thorough review, and synthesizes findings.

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-szoloth-skill-pack-qa

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Qa? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

QA — Codex-Powered Change Review

Thorough QA on all changes in the current working tree using Codex as a second pair of eyes. Detects what changed, sends it to Codex for deep review, and presents actionable findings.

When to Use

  • After completing implementation work, before committing
  • User says "QA", "full QA", "QA my changes", "review with codex"
  • Any time you want a second opinion on everything you just built

Process

Step 1: Gather All Changes

# Get the full picture
git status --porcelain
git diff --stat
git diff --cached --stat

# Capture the actual diff (staged + unstaged)
git diff HEAD > /tmp/qa-full-diff.patch

If changes span many files, also get a summary:

git diff HEAD --name-only

Step 2: Build Context

Before sending to Codex, gather context about what was being built:

  • What task/feature was being implemented?
  • What files were touched and why?
  • Any known areas of concern?

Summarize this in 2-3 sentences to give Codex context.

Step 3: Codex Review (diff-based)

Run Codex with the full diff and context. Use -C to point at the repo so Codex can read surrounding code.

cat  /qa

Gathering changes...
  12 files changed, +342 lines, -89 lines

Sending to Codex for review...
  Context: "Implemented OAuth2 login flow with PKCE, added token refresh middleware"

[Codex reviewing... ~60s]

══════════════════════════════════════════════════════════════
QA REVIEW (via Codex)
══════════════════════════════════════════════════════════════

Files reviewed: 12
Codex verdict: ISSUES FOUND

P1 — Bugs & Security
────────────────────────────────────────────────────────────────
1. src/auth/token.ts:47 — Token stored in localStorage without encryption
   Fix: Use httpOnly cookie or encrypted session storage

P2 — Likely Problems
────────────────────────────────────────────────────────────────
1. src/middleware/refresh.ts:23 — Race condition if multiple requests
   trigger refresh simultaneously
   Fix: Add mutex/queue for token refresh

P3 — Minor Concerns
────────────────────────────────────────────────────────────────
None found

══════════════════════════════════════════════════════════════

Fix P1 issues now? [y/N]

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.