test-pass

Log linting, test, benchmark, and playtest issues to GitHub.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/WayneWalterBerry/MMO --skill test-pass
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-pass
Source: https://github.com/WayneWalterBerry/MMO/tree/main/.squad/skills/test-pass
Command: npx skills add https://github.com/WayneWalterBerry/MMO --skill test-pass

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This QA governance skill provides a structured, read-only audit that surfaces all issues from linting, unit tests, parser benchmarks, and end-to-end playtests, and logs them to GitHub without making changes to the codebase.

Core Features & Use Cases

  • Parallel quality checks: lint, unit tests, parser benchmarks, and playtests run concurrently to shorten validation time.
  • Issue generation: for every failure, results are transformed into GitHub issues with standardized titles and labels.
  • Non-fix policy: the workflow does not modify code; it only reports findings for triage and remediation planning.

Quick Start

Run a full audit by triggering the test-pass workflow to log all issues without applying fixes.

Frequently Asked Questions about test-pass

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

FAQPage Schema
How do I log automated QA audit results to GitHub issues?

To log automated QA audit results to GitHub issues, trigger a full test-pass sweep that runs linting, unit tests, benchmarks, and playtests in parallel, automatically generating labeled GitHub issues for every detected failure.

Can I run linting, unit tests, and playtests concurrently during a code audit?

Yes, you can run linting, unit tests, and playtests concurrently during a code audit by executing a parallel QA sweep that validates the full codebase and transforms all identified issues into standardized GitHub issue entries.

Does this QA automation tool fix code errors it finds?

No, this QA automation tool enforces a strict non-fix policy and does not modify code. It only surfaces issues from linting, tests, benchmarks, and playtests, producing a summary with labels for efficient triage and remediation.

What is the best way to benchmark parsers and log failures for triage?

The best way to benchmark parsers and log failures for triage is to run a read-only QA governance sweep that executes parser benchmarks alongside other checks, automatically generating labeled GitHub issues for any failures detected.

How do I generate standardized GitHub issues from end-to-end playtest failures?

To generate standardized GitHub issues from end-to-end playtest failures, run a complete QA pass that executes playtests in parallel with other quality checks, transforming every failure into a labeled GitHub issue for remediation planning.