uberdev-cmd-testers

Spawn adversarial QA agents to audit code and file GitHub issues.

2|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/TheFJK/UberDev --skill uberdev-cmd-testers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uberdev-cmd-testers
Source: https://github.com/TheFJK/UberDev/tree/main/codex/uberdev-codex/skills/uberdev-cmd-testers
Command: npx skills add https://github.com/TheFJK/UberDev --skill uberdev-cmd-testers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a way to perform a thorough and adversarial QA audit on code, ensuring that it meets stringent quality standards without altering the original codebase.

Core Features & Use Cases

  • Adversarial QA Audit: Spawns a squad of 8 agents (6 personas + 2 monitors) to review the target code.
  • Target Auto-detection: Automatically detects the target (web/api/native/all).
  • Findings Persistence: Auto-file findings as GitHub issues.
  • Use Case: Ideal for ensuring code quality and security before merging pull requests.

Quick Start

Run the skill by typing: /uberdev-cmd-testers <target> --watch

Frequently Asked Questions about uberdev-cmd-testers

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

FAQPage Schema
How do I run an automated adversarial QA audit on my codebase?

To run an adversarial QA audit, launch the skill on a specified code target. It spawns a squad of 8 agents with various personas to review the code and auto-files findings as GitHub issues for traceability.

What is an adversarial code review squad and how does it work?

An adversarial code review squad is a group of 6 persona agents and 2 monitors that evaluate code targets. Operating in read-only mode, it identifies quality and security issues without altering the original codebase.

Can I perform a read-only code review without risking changes to my repository?

Yes, you can execute a read-only adversarial QA audit to evaluate code quality. This process ensures no code changes are made to your repository while it identifies and reports issues.

Does the adversarial testing squad support auto-filing GitHub issues for code review?

Yes, the adversarial testing squad supports auto-filing GitHub issues. It automatically persists findings as GitHub issues on your repository, ensuring full traceability for the identified code quality problems.

What is the best way to ensure code quality before merging a pull request?

The best way to ensure code quality before merging is to launch a read-only adversarial QA audit squad. It automatically detects your target environment and thoroughly reviews the code for security and quality issues.

What are the limitations of using a read-only QA audit for code review?

The primary limitation of this read-only QA audit is that it cannot fix the identified code issues directly. It strictly evaluates the codebase and reports findings to GitHub issues, leaving the actual code changes to the developers.