wayq-regress

Monitor GitHub issues for regressions and report findings in audio format.

1|Updated Jun 21, 2026

Search Tags:#parallel processing #github #issue tracking #regression testing #audio reporting

Ready to run

npx skills add https://github.com/rcrath/wayq --skill wayq-regress

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wayq-regress
Source: https://github.com/rcrath/wayq/tree/main/.claude/skills/wayq-regress
Command: npx skills add https://github.com/rcrath/wayq --skill wayq-regress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill checks GitHub issues for regressions since the last successful build and reports the findings in audio format, ensuring timely issue identification and mitigation.

Core Features & Use Cases

Regression Monitoring: Tracks issues tagged with 'regress_meta' in GitHub repository.
Parallel Analysis: Spawns parallel haiku agents for each issue to analyze code changes.
Audio Reporting: Provides risk assessments and clearances in audio, aiding quick understanding.
Use Case: Use this Skill in CI/CD pipelines to get an immediate audio report on potential regressions after builds.

Quick Start

Run the /wayq-regress command to get an audio report on regressions since the last successful build.

Frequently Asked Questions about wayq-regress

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

FAQPage Schema

How do I monitor GitHub issues for regressions after a build?▼

Yes, you can automate regression testing in CI/CD pipelines by running this Skill after builds. It monitors GitHub issues for regressions and outputs audio reports to ensure timely issue identification and mitigation.

How does parallel processing work for GitHub issue analysis?▼

Parallel processing works by spawning parallel haiku agents for each detected GitHub issue. These agents conduct detailed analysis of the code changes concurrently, generating risk assessments and clearances for audio reporting.

Do I need GitHub API access to track issue regressions?▼

Yes, GitHub API access is required. The Skill queries your GitHub repository to monitor issues tagged with 'regress_meta' and fetches the necessary data for parallel analysis.

What is the best way to get audio reports for issue tracking?▼

The best way to get audio reports for issue tracking is to use this Skill, which provides risk assessments and clearances in audio format. This method aids quick understanding of potential regressions without reading logs.

Are there limitations to using parallel agents for regression testing?▼

A limitation of using parallel agents for regression testing is the requirement for parallel processing capabilities. Additionally, the system relies on specific 'regress_meta' tags in GitHub issues to function correctly.