Text of github.github.com › gh-aw › blog › 2 as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Blog | GitHub Agentic Workflows

Skip to main content Blog Most agentic workflow examples stop at one trigger and one comment. svennijhuis/agentic-workflows goes further. It is a catalog of eleven installable workflows that take an issue to a reviewed pull request, with a reviewer that can send work back a limited number of times before handing it to a human. It is aimed at teams that want a working, opinionated build loop they can install with gh aw add and adapt, rather than designing one from scratch.

Why it’s awesome Section titled “Why it’s awesome” A hard cap on the loop. Each workflow enforces its own limit in its if: condition, so the runner decides whether a run starts, not prompt text. issue-builder.md starts only for a new build or fix rounds 1 and 2. pr-reviewer.md runs review rounds 1 to 3 only, so the builder gets at most two send-backs. The reviewer also derives the round from its own history of Reviewer: changes needed reviews, so a wrong input cannot reset the count.

Review that never merges. The reviewer allows only COMMENT reviews. The workflow explains why: without a separate builder identity, builder PRs and reviews share github-actions[bot] , and GitHub rejects REQUEST_CHANGES on your own PR. A maintainer stays the merge gate. The reviewer can add ready-to-merge or needs-help labels, but it never approves, merges or pushes. Four axes plus a conditional security pass. The reviewer starts standards , spec , deslop and blast-radius sub-agents, each in a fresh context and each asked for path:line evidence.

A security sub-agent runs only when the diff touches a trust boundary, such as endpoints, auth, permissions, .github/workflows/* , dependency manifests, secrets, shell calls, outbound network or deserialization. Each axis keeps its own heading and is not reranked, so a reader can see which axis raised a concern. Fail-closed defaults in shared fragments. shared/security.md closes the network except for gh-aw defaults, requires importers to name any extra host, and keeps threat detection on. shared/defaults.md pins the engine version. max-ai-credits and max-daily-ai-credits use the main workflow’s values when set, then fall back to the first usable imported value.

Other limits such as max-turns and timeout-minutes stay in each workflow’s own frontmatter because the compiler ignores them in imports. Vendored skills with provenance. The shared/skills/ folder holds local copies of eleven skills, mostly from mattpocock/skills . The shared README records the source path, commit SHA and license for each one, along with the update procedure. How it works Section titled “How it works” aw.yml is the package manifest.

It lists the eleven workflows under includes: and sets min-version: v0.93.4 , so gh aw add knows what to install. An issue-builder run implements an issue and opens a builder/* pull request labeled builder . The builder then dispatches pr-reviewer for round 1. The reviewer posts a COMMENT review that starts with Reviewer: ready to merge. when clean. Otherwise it posts inline comments and dispatches the builder for a fix round.

If round 3 still has findings, the reviewer adds needs-help and posts one summary of open points for a maintainer. It starts nothing further. Try it Section titled “Try it” From the README, in a target repository: Terminal window gh aw add svennijhuis/agentic-workflows/workflows/issue-builder.md@<tag> gh aw compile Pin <tag> to a released version rather than a branch. Each workflow names the other in dispatch-workflow , so installing either one brings the other along.

The builder also references a CI_TRIGGER_TOKEN secret for an extra empty commit that starts CI. It is a placeholder name, so rename it to match your setup. The install guide covers tokens, secrets and labels for an organization. Patterns worth borrowing even without the full loop: Put the loop cap in the trigger if: so the runner enforces it. Make the reviewer comment-only when the author and reviewer share an identity.

Gate expensive security review on a path-based trust-boundary check. Learn more Section titled “Learn more” Explore svennijhuis/agentic-workflows , starting with its workflows README and the builder and reviewer pair. To build your own, start with GitHub Agentic Workflows . Some workflows report on the code they touch. Today’s spotlight goes to one that reads its own codebase for patterns worth linting, then tries to turn what it finds into a fix.

It is also the workflow that failed on its most recent scheduled run, which makes it a useful case study in how these systems break. Agent of the Day: Actions and AW Linter Factory Section titled “Agent of the Day: Actions and AW Linter Factory” Actions and AW Linter Factory runs once a day. Each run picks one lint rule for the AST checks under pkg/workflow/lint/ , looks for real evidence that the pattern matters, and proposes a rule with a fix.

It skips a new run while a pull request with [actions-aw-linter] in its title is still open, so it does not stack up competing proposals. This is the first time this workflow has been featured, so the rotation put it ahead of workflows that had been spotlighted before. What the live evidence shows Section titled “What the live evidence shows” The last three scheduled runs tell three different stories. Run Date (UTC) Conclusion Duration Audit signal 43267067168 Nov 12 failure 3.4m “Agent reported that it could not complete the task”; threat detection failed 43066035425 Nov 11 success 13.0m High token usage (about 995k tokens) 42862531335 Nov 10 success 18.6m High token usage (about 1.36M tokens) The November 12 failure is the one to read closely.

The audit classes it as a critical workflow failure, with three errors. The agent stopped before it could finish. The threat detection job also failed, with the reason agent_failure . The audit calls that a tooling error, not a security finding. The failed steps were the “Install AWF binary” steps in both the agent job and the detection job. The run lasted only 3.4 minutes, so this was an early stop, not a timeout in the middle of analysis.

The two successful runs completed in one turn with no reported errors. Their audits still flag two things: high token usage and a “Resource Heavy For Domain” finding. For a daily job that reads a whole codebase, that cost is expected, but it is worth tracking as the rule set grows. Where its work has landed Section titled “Where its work has landed” The workflow has already produced a steady stream of pull requests.

Each one is titled with the [actions-aw-linter] prefix and is now closed: #69972 : Add the daily Actions and AW AST linter factory itself. #71189 : Fix workflow_run positive branch cancellation detection. #71929 : Add a step-reference lint rule. #73253 : Fix release cache lint for Python and Java setup actions. #73832 : Fix artifact execution detection for option-prefixed scripts. The fixes are the clearest sign that the loop works.

A lint rule that produces a false positive gets a follow-up pull request that narrows it, rather than a quiet ignore. Why it matters Section titled “Why it matters” A linter that writes its own rules is only as trustworthy as its validation. This workflow has a gate that stops it when a run cannot complete, which is what the November 12 failure shows. A stopped run is far better than a half-finished proposal that looks finished.

The question for the next few weeks is whether the install step that failed on November 12 is a one-off or a pattern. Try it Section titled “Try it” Read the workflow source to see how it selects rules and gates its runs. To build something similar, start at github/gh-aw . Some workflows fail with a stack trace. Others fail on a schedule, every morning, with nothing to show for it. This week’s spotlight is a workflow that has now missed three daily runs in a row, and the audit of its latest run tells a more useful story than the red X does.

Agent of the Day: Daily A/B Tes

The rest of this page is on the live site.