Blog

Meet the Workflows: Testing & Validation

Jan 13, 2026

Don Syme

Peli de Halleux

Mara Kiefer

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.

Meet the Workflows: Interactive & ChatOps

Jan 13, 2026

Don Syme

Peli de Halleux

Mara Kiefer

Onwards, onwards! Let’s keep exploring the wonders of Peli’s Agent Factory! To the command center where instant magic happens!

In our previous post, we explored creative and culture workflows - agents that bring joy, build team culture, and create moments of delight. We discovered that AI agents don’t have to be all business; they can have personality while making work more enjoyable.

But sometimes you need help right now, at the exact moment you’re stuck on a problem. You don’t want to wait for a scheduled run - you want to summon an expert agent with a command. That’s where interactive workflows and ChatOps come in. These agents respond to slash commands and GitHub reactions, providing on-demand assistance with full context of the current situation.

We learned that the right agent at the right moment with the right information is a valuable addition to an agent portfolio.

Interactive & ChatOps Workflows

These agents respond to commands, providing on-demand assistance whenever you need it:

• Q - Workflow optimizer that investigates performance and creates PRs
• Grumpy Reviewer - Performs critical code reviews with personality
• Workflow Generator - Creates new workflows from issue requests

Interactive workflows changed how we think about agent invocation. Instead of everything running on a schedule, these respond to slash commands and reactions - /q summons the workflow optimizer, a 🚀 reaction triggers analysis. Q (yes, named after the James Bond quartermaster) became our go-to troubleshooter - it investigates workflow performance issues and opens PRs with optimizations.

The Grumpy Reviewer gave us surprisingly valuable feedback with a side of sass (“This function is so nested it has its own ZIP code”). We learned that context is king - these agents work because they’re invoked at the right moment with the right context, not because they run on a schedule.

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:

Q:

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

Grumpy Reviewer:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/grumpy-reviewer.md

Workflow Generator:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/workflow-generator.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: Testing & Validation Workflows

While ChatOps agents respond to commands, we also need workflows that continuously verify our systems still function as expected.

Continue reading: Testing & Validation Workflows →

---

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

Meet the Workflows: Teamwork & Culture

Jan 13, 2026

Don Syme

Peli de Halleux

Mara Kiefer

Oh, my dear friends! Let’s explore the playful workshop - the most fun corner of Peli’s Agent Factory!

In our previous post, we explored security and compliance workflows - the essential guardrails that manage vulnerability campaigns, validate network security, and prevent credential exposure. These workflows let us sleep soundly knowing our agents operate within safe boundaries.

But here’s the thing: work doesn’t have to be all business. While we’ve built serious, production-critical workflows for quality, releases, and security, we also discovered something unexpected - AI agents can bring joy, build team culture, and create moments of delight. Not every workflow needs to solve a critical problem; some can simply make your day better. Let’s explore the playful side of our agent factory, where we learned that personality and fun drive engagement just as powerfully as utility.

Teamwork & Culture Workflows

These agents facilitate team communication and remind us that work can be fun:

• Daily Team Status - Shares team mood and status updates
• Daily News - Curates relevant news for the team
• Poem Bot - Responds to /poem-bot commands with creative verses (yes, really)
• Weekly Issue Summary - Creates digestible summaries complete with charts and trends
• Daily Repo Chronicle - Narrates the day’s activity like a storyteller - seriously, it’s kind of delightful.

The Poem Bot started as a whimsy in our Copilot for PRs project in 2022. Someone said “wouldn’t it be funny if we had an agent that writes poems about our code?” and then we built it. We learned that AI agents don’t have to be all business - they can build culture and create moments of joy. We brought this forward to this project.

The Daily News workflow curates relevant articles, but it also adds commentary and connects them to our work.

The Weekly Issue Summary and Daily Repo Chronicle workflows turn dry data into engaging narratives, making it easier to stay informed without feeling overwhelmed.

A theme here is the reduction of cognitive load. Having agents summarize and narrate daily activity means we don’t have to mentally parse long lists of issues or PRs. Instead, we get digestible stories that highlight what’s important. This frees up mental bandwidth for actual work.

Another theme is that tone can help make things more enjoyable. The Daily Repo Chronicle started writing summaries in a narrative, almost journalistic style. The outputs from AI agents don’t have to be robotic - they can have personality while still being informative.

These communication workflows help build team cohesion and remind us that work can be delightful.

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 Team Status:

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

Daily News:

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

Poem Bot:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/poem-bot.md

Weekly Issue Summary:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/weekly-issue-summary.md

Daily Repo Chronicle:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/daily-repo-chronicle.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: Summon an Agent on Demand

Scheduled workflows are great, but sometimes you need help right now. Enter ChatOps and interactive workflows.

Continue reading: Interactive & ChatOps Workflows →

---

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

Meet the Workflows: Security-related

Jan 13, 2026

Don Syme

Peli de Halleux

Mara Kiefer

Splendid! How great to have you back at Peli’s Agent Factory! Now, let me show you the guardian chamber - where the watchful protectors stand vigil!

In our previous post, we explored operations and release workflows that handle the critical process of shipping software - building, testing, generating release notes, and publishing. These workflows need to be rock-solid reliable because they represent the moment when our work reaches users.

But reliability alone isn’t enough - we also need security. When AI agents can access APIs, modify code, and interact with external services, security becomes paramount. How do we ensure agents only access authorized resources? How do we track vulnerabilities and enforce compliance deadlines? How do we prevent credential exposure? That’s where security and compliance workflows become our essential guardrails - the watchful guardians that let us sleep soundly at night.

Security-related Workflows

These agents are our security guards, keeping watch and enforcing the rules:

• Security Compliance - Runs vulnerability campaigns with deadline tracking
• Firewall - Tests network security and validates rules
• Daily Secrets Analysis - Scans for exposed credentials (yes, it happens)
• Daily Malicious Code Scan - Reviews recent code changes for suspicious patterns
• Static Analysis Report - Daily security scans using zizmor, poutine, and actionlint

The Security Compliance agent manages entire vulnerability remediation campaigns with deadline tracking - perfect for those “audit in 3 weeks” panic moments.

The Firewall workflow validates that our agents can’t access unauthorized resources - it’s the bouncer that enforces network rules.

The Daily Secrets Analysis scans for exposed credentials in commits and discussions, catching those “oops, I committed my API key” moments before they become incidents.

The Daily Malicious Code Scan goes deeper, reviewing recent code changes for suspicious patterns that might indicate security threats or compromised agentic behavior.

The Static Analysis Report runs a comprehensive security audit daily using industry-standard tools (zizmor, poutine, actionlint) to catch workflow vulnerabilities. This is particularly interesting because it shows how traditional security tools can be integrated into an AI agent workflow.

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:

Security Compliance:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/security-compliance.md

Firewall:

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

Daily Secrets Analysis:

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

Daily Malicious Code Scan:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/daily-malicious-code-scan.md

Static Analysis Report:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/static-analysis-report.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: Teamwork & Culture Workflows

After all this serious talk, let’s explore the fun side: agents that bring joy and build team culture.

Continue reading: Teamwork & Culture Workflows →

---

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

Meet the Workflows: Operations & Release

Jan 13, 2026

Don Syme

Peli de Halleux

Mara Kiefer

Ah! Right this way to our next chamber in Peli’s Agent Factory! The chamber where our AI agents enhance the magical moment of shipping software.

In our previous post, we explored metrics and analytics workflows - the agents that monitor other agents, turning raw activity data into actionable insights.

Operations & Release Workflows

The agents that help us actually ship software:

• Release - Orchestrates builds, tests, and release note generation
• Changeset - Manages version bumps and changelog entries for releases
• Daily Workflow Updater - Keeps actions and dependencies current (because dependency updates never stop)

Shipping software is stressful enough without worrying about whether you formatted your release notes correctly.

The Release workflow handles the entire orchestration - building, testing, generating coherent release notes from commits, and publishing. What’s interesting here is the reliability requirement: these workflows can’t afford to be creative or experimental. They need to be deterministic, well-tested, and boring (in a good way).

The Changeset workflow automates the tedious task of version bumps and changelog entries. It analyzes commits since the last release, determines the appropriate version bump (major, minor, patch), and updates the changelog accordingly.

The Daily Workflow Updater taught us that maintenance is a perfect use case for agents - it’s repetitive, necessary, and nobody enjoys doing it manually. These workflows handle the toil so we can focus on the interesting problems.

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:

Release:

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

Changeset:

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

Daily Workflow Updater:

gh aw add https://github.com/github/gh-aw/blob/v0.37.7/.github/workflows/daily-workflow-updater.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: Security-related Workflows

After all this focus on shipping, we need to talk about the guardrails: how do we ensure these powerful agents operate safely?

Continue reading: Security-related Workflows →

---

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

Newer posts

Older posts