Monitor git HEAD changes and trigger regression tests for SubAgent workflows.
npx skills add https://github.com/blackplume233/Actant --skill qa-monitor
Please help me install this Agent Skill. Skill: qa-monitor Source: https://github.com/blackplume233/Actant/tree/main/.agents/skills/qa-monitor Command: npx skills add https://github.com/blackplume233/Actant --skill qa-monitor
Monitors git HEAD changes and triggers full regression tests when new commits appear for SubAgent workflows.
Start the QA watch loop with default settings to monitor HEAD changes and trigger regression tests.
High-intent search queries and answers about installing and using this skill.
To configure continuous testing, set polling intervals to check for HEAD changes, define idle limits, and select specific scenarios to run. Tests execute in isolated temporary directories with both mock and real launcher modes available.
Yes, you can run regression tests in isolated temporary directories specifically for SubAgent workflows. This approach ensures end-to-end test coverage and traceability without interfering with your main working directory.
Continuous QA monitoring is the process of watching repository HEAD changes to trigger automated regression tests, applying to continuous integration-like environments to ensure ongoing quality assurance with trendable metrics.
Yes, the regression test monitoring supports both mock and real launcher modes, allowing you to validate test configurations safely before executing full regression cycles against real environments.
You generate trendable QA metrics and standardized reports by running continuous regression test cycles that produce per-round logs and aggregated results, ensuring end-to-end test coverage and traceability.
VirtoCommerceValidate vc-mcp-testing-module QA tooling before regression execution.
Euraika-LabsDetect flaky tests in CI logs from GitHub Actions, Unity, Godot, or Unreal.
webn77Capture baseline metrics and compare test results in CI/CD workflows.
Marshall-HallenbeckDiagnose and repair failing test suites across multiple language ecosystems.
