qa-sec

Audit git diffs with parallel QA and security reviews.

8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Gold-b/claude-code-governance --skill qa-sec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-sec
Source: https://github.com/Gold-b/claude-code-governance/tree/main/bundle/skills/qa-sec
Command: npx skills add https://github.com/Gold-b/claude-code-governance --skill qa-sec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch correctness, integration, performance, and security issues before release by coordinating a structured audit across all changed files. It reduces the risk of shipping broken features, insecure code, or unverified infrastructure changes.

Core Features & Use Cases

  • Parallel audit orchestration: Dispatches QA, Security, and Integration agents at the same time to review the same change set from different angles.
  • Change-aware review flow: Detects changed files with git, skips docs-only updates, and tailors checks to backend, frontend, infrastructure, and config changes.
  • Fix-and-verify workflow: Prioritizes CRITICAL and HIGH findings, allows agents to fix serious issues directly, and synthesizes a final release-readiness report.
  • Use cases: Ideal before merging a feature branch, after a large refactor, before deployment, or whenever you need a combined code quality and security gate.

Quick Start

Ask the qa-sec skill to audit the current git changes, run parallel QA and security checks, and report any blocking issues before release.

Frequently Asked Questions about qa-sec

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

FAQPage Schema
How do I run a pre-release code review and security audit on my git diff?

A pre-release code review and security audit detects modified files via git diff and dispatches parallel QA, Security, and Integration agents to analyze the changes. It synthesizes release-blocking findings into a structured PASS, FAIL, or WARN report with remediation steps.

What is the best way to automate OWASP security checks before merging a feature branch?

Automating OWASP security checks before a merge is best handled by running parallel specialist agents that review active git diffs for vulnerabilities. This approach prioritizes CRITICAL and HIGH findings, allowing agents to fix serious issues directly before synthesizing a final release-readiness report.

Can I run parallel QA and security checks on infrastructure and configuration changes?

Yes, parallel QA and security checks support infrastructure and configuration changes. The audit orchestrator is change-aware, tailoring validation checks to backend, frontend, infrastructure, and config modifications while skipping documentation-only updates.

Does the qa-sec skill require a specific project configuration file to operate?

Yes, the skill requires a CLAUDE.md file for project convention discovery and uses git-based scope detection to identify changed files. It relies on these inputs to tailor parallel specialist reviews and structured reporting accurately.

How do integration tests and code review agents handle critical release-blocking findings?

Integration tests and code review agents handle critical findings by prioritizing CRITICAL and HIGH severity issues, allowing agents to fix serious problems directly. This fix-and-verify workflow remediates severe issues immediately before generating the final release report.