qe-audit

Schedule and run QE audits on code repositories to identify test-coverage gaps.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill qe-audit-zillabunny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qe-audit
Source: https://github.com/zillabunny/GoblinVolleyball-1.1/tree/main/.claude/skills/qe-audit
Command: npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill qe-audit-zillabunny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QE audits are essential to identify test-coverage gaps and regressions in code changes before deployment.

Core Features & Use Cases

  • Schedule and run quality engineering audits on commits and features.
  • Generate GitHub issues for findings and update the QE issues tracker.
  • Support bash stress-testing mode to explore under-tested areas.

Quick Start

Run a quick manual audit with /qe-audit now to start validating recent commits.

Frequently Asked Questions about qe-audit

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

FAQPage Schema
How do I automate quality engineering audits for recent git commits?

You can automate code audits for recent git commits by scheduling automated execution to identify test-coverage gaps and potential bugs. The system supports cron-based scheduling with commands to run audits immediately or at intervals.

How does automated code audit scheduling handle time zones and lifecycle?

Automated code audit scheduling handles time zones and lifecycle by using cron-based commands like 'every', 'now', 'stop', and 'next'. It generates time-zone aware outputs to track and manage the audit execution lifecycle accurately.

Can I create GitHub issues automatically from QE audit findings?

Yes, you can create GitHub issues automatically from QE audit findings. The audit system integrates with a QE issues tracker to generate GitHub issues for identified bugs and updates the issues log accordingly.

Does the code audit tool support bash stress-testing for under-tested areas?

Yes, the code audit tool supports bash stress-testing for under-tested areas. This optional mode explores under-tested areas of code changes to identify potential regressions and test-coverage gaps more thoroughly.

How do I stop or check the next scheduled run for an issues tracker audit?

You can stop or check the next scheduled run for an issues tracker audit using the 'stop' and 'next' cron lifecycle commands. These commands manage the automated scheduling and provide time-zone aware output for tracking.