qa-auditor

Audit codebases for security vulnerabilities and quality issues with prioritized findings.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/unnamedmistress/menuspy-marketing --skill qa-auditor-unnamedmistress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-auditor
Source: https://github.com/unnamedmistress/menuspy-marketing/tree/main/qa-auditor
Command: npx skills add https://github.com/unnamedmistress/menuspy-marketing --skill qa-auditor-unnamedmistress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides focused, prioritized identification of security vulnerabilities, bugs, and code quality issues so teams can triage risk and plan remediation more effectively.

Core Features & Use Cases

  • Security auditing: Detect common vulnerabilities like SQL injection, XSS, CSRF, authentication flaws, and exposed secrets with OWASP-informed checks.
  • Quality and performance review: Highlight error handling gaps, N+1 patterns, inefficient algorithms, and potential memory or scalability concerns.
  • Accessibility and maintainability: Call out WCAG issues, keyboard navigation gaps, readability problems, and missing tests; useful for code reviews, pre-release audits, and CI gating.

Quick Start

Ask the qa-auditor to audit the provided codebase for security, performance, accessibility, and quality issues and return a prioritized list of findings with locations and impact.

Frequently Asked Questions about qa-auditor

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

FAQPage Schema
How do I audit my codebase for security vulnerabilities and quality issues?

A security and quality audit detects vulnerabilities like SQLi, XSS, and CSRF, alongside performance and accessibility issues. It applies OWASP-informed checks to your codebase and returns a prioritized list of findings with file locations, impacts, and relevant remediation guidance.

What is the best way to prioritize code review findings for remediation?

Prioritizing code review findings involves categorizing vulnerabilities and quality issues by severity from P0 to P3. This approach highlights critical risks first and reports exact file locations and impacts to help teams triage risk and plan remediation effectively.

Can I check web application accessibility and WCAG compliance during a security audit?

Yes, an audit can check web application accessibility and WCAG compliance alongside security vulnerabilities. The process identifies keyboard navigation gaps and accessibility issues, returning them in a single prioritized report with file locations and impact assessments.

Does the audit detect common backend vulnerabilities like SQL injection and exposed secrets?

Yes, the audit detects common backend vulnerabilities like SQL injection, authentication flaws, and exposed secrets. It applies OWASP-informed checks to backend applications and prioritizes these findings by severity from P0 to P3, detailing file locations and potential impacts.

How do I use vulnerability testing to gate CI/CD pipelines for web applications?

To gate CI/CD pipelines for web applications, run vulnerability testing to identify security and quality issues like XSS, CSRF, and N+1 patterns. The resulting prioritized list of findings enables automated gating by failing builds that contain P0 or P1 severity risks.

When should I use an automated security audit instead of a manual code review?

An automated security audit is ideal for pre-release checks and CI/CD gating to quickly detect common vulnerabilities like SQLi and exposed secrets. Use it to triage risk across a codebase, then apply manual code review to investigate the prioritized findings and complex business logic.