Meet the Workflows: Testing & Validation

Jan 13, 2026

Right this way! Let’s continue our grand tour of Peli’s Agent Factory! Into the verification chamber where nothing escapes scrutiny!

In our previous post, we explored ChatOps workflows - agents that respond to slash commands and GitHub reactions, providing on-demand assistance with full context.

But making code better is only half the battle. We also need to ensure it keeps working. As we refactor, optimize, and evolve our codebase, how do we know we haven’t broken something? How do we catch regressions before users do? That’s where testing and validation workflows come in - the skeptical guardians that continuously verify our systems still function as expected. We learned that AI infrastructure needs constant health checks, because what worked yesterday might silently fail today. These workflows embody trust but verify.

Testing & Validation Workflows

These agents keep everything running smoothly through continuous testing:

Code Quality & Test Validation

Daily Testify Uber Super Expert - Analyzes test files daily and suggests testify-based improvements
Daily Test Improver - Identifies coverage gaps and implements new tests incrementally
Daily Compiler Quality Check - Analyzes compiler code to ensure it meets quality standards

User Experience & Integration Testing

Daily Multi-Device Docs Tester - Tests documentation across devices with Playwright (mobile matters!)
CLI Consistency Checker - Inspects the CLI for inconsistencies, typos, and documentation gaps

CI/CD Optimization

CI Coach - Analyzes CI pipelines and suggests optimizations
Workflow Health Manager - Meta-orchestrator monitoring health of all agentic workflows

The Daily Testify Expert and Daily Test Improver work together to continuously improve our test suite - one analyzes existing tests for quality improvements, the other identifies coverage gaps and implements new tests. The Compiler Quality Check and Breaking Change Checker maintain code quality and API stability.

The Multi-Device Docs Tester uses Playwright to test our documentation on different screen sizes - it found mobile rendering issues we never would have caught manually. The CLI Consistency Checker helps maintain developer experience by catching UX inconsistencies.

The CI Coach suggests pipeline optimizations to keep builds fast, while the Workflow Health Manager watches all these watchers, ensuring the testing infrastructure itself stays healthy.

These workflows embody the principle: trust but verify. Just because it worked yesterday doesn’t mean it works today.

Using These Workflows

You can add these workflows to your own repository and remix them. Get going with our Quick Start, then run one of the following:

Daily Testify Uber Super Expert:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/daily-testify-uber-super-expert.md

Daily Test Improver:

gh aw add githubnext/agentics/workflows/daily-test-improver.md

Daily Compiler Quality Check:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/daily-compiler-quality.md

Daily Multi-Device Docs Tester:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/daily-multi-device-docs-tester.md

CLI Consistency Checker:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/cli-consistency-checker.md

CI Coach:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/ci-coach.md

Workflow Health Manager:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/workflow-health-manager.md

Then edit and remix the workflow specifications to meet your needs, recompile using gh aw compile, and push to your repository. See our Quick Start for further installation and setup instructions.

Learn More

GitHub Agentic Workflows - The technology behind the workflows
Quick Start - How to write and compile workflows

Next Up: Monitoring the Monitors

But what about the infrastructure itself? Who watches the watchers? Time to go meta.

Continue reading: Tool & Infrastructure Workflows →

This is part 14 of a 19-part series exploring the workflows in Peli’s Agent Factory.