Blog | GitHub Agentic Workflows
Skip to main content Blog Codebases rarely collapse in one commit. They drift: a file gains a few hundred lines, a function picks up one more branch, a package exports one more symbol. Today’s spotlight goes to the workflow that watches for that drift. Agent of the Day: Architecture Guardian Section titled “Agent of the Day: Architecture Guardian” Architecture Guardian analyzes commits from the last 24 hours and looks for code structure violations in Go and JavaScript files: large files, oversized functions, high export counts, and import cycles.
It runs on a schedule, around 14:00 UTC on weekdays, and can also be dispatched manually. Its permissions are read-only ( contents: read , actions: read ), which suits a reviewer whose job is to observe and report. What the live evidence shows Section titled “What the live evidence shows” Today’s scheduled run, 42632762703 , started at 14:14 UTC on main and finished successfully in about 7 minutes. A structured audit of the run reports: Signal Value Conclusion success Turns 1 Tool types 2 Errors / warnings 0 / 0 Token usage ~104k Execution style directed, read-only The audit labels the execution path “directed”: one linear turn, a narrow set of tools, no writes.
The one flag it raised was medium-severity high token usage, a reminder that scanning a day of commits for structure has a real cost, and a useful number to watch over time. The same day’s scheduled fleet included Dead Code Removal Agent , PR Sous Chef and Daily Fact . In this run the audit shows no issue or pull request was created, so there is nothing to link beyond the run itself. Why it matters Section titled “Why it matters” Structural checks are easy to postpone and hard to retrofit.
Running them daily, against only the newest commits, keeps feedback close to the change that caused it. Try it Section titled “Try it” Browse the workflow source, copy the pattern, and build your own guardian at github/gh-aw . Two releases landed in github/gh-aw this week, with a focus on durability, observability, and security. Here’s what you can use today. Release: v1.2.1 Section titled “Release: v1.2.1” v1.2.1 (November 6) focuses on workflow durability, safer updates, and broader engine and auth support.
Durable workflow continuation ( #75097 ): Artifact-backed continuation lets work carry across agents. Specification-aware PR reviewer ( #75207 ) and an experimental Atomic declarative engine ( #75196 ). Smarter create-issue ( #75323 , #74941 ): Issue artifacts and label-scoped title deduplication. GitHub App auth for repo-memory ( #74937 ) and deployment controls on workflow environments ( #74938 ). Safer updates ( #74948 , #74945 ): gh aw update preserves source refs, frontmatter comments, and formatting.
Security reviews fail closed when unresolved ( #75335 ), and a new warning flags dynamic checkout refs ( #74951 ). Release: v1.2.0 Section titled “Release: v1.2.0” v1.2.0 (November 4) is a security and observability release. Breaking: pull_request_target forks now require explicit opt-in for unrestricted use ( #74884 ). Review fork-facing workflows and add the opt-in where intended. Breaking: the -l shorthand was removed from project new ( #74561 ).
OpenTelemetry : opt-in OTLP session logs ( #74599 ) and dependency-free OTLP protobuf support for Azure Monitor ( #74594 ). Hardening : bounded ZIP extraction ( #74906 ) and stricter run-step expression sanitization ( #74793 ). Notable Pull Requests Since Section titled “Notable Pull Requests Since” #75995 replaces the Pi durable runtime with native session chaining. #75927 adds OpenAI workload identity federation for Codex. #75988 supports name-based artifact upserts in update-issue .
Agent of the Week: PR Specification Reviewer Section titled “ Agent of the Week: PR Specification Reviewer” It reviews PRs for conformance and updates specifications on the PR branch so implementation and specs stay aligned. It was just promoted in v1.2.1, and the logs show it busy: in its three most recent runs it was triggered on pull requests within about an hour of each other. Two finished successfully (about 7 minutes each), each in a single turn.
The third run failed after 26 seconds, so even the spec police occasionally trip on the way in. Usage tip : Scope a reviewer like this to paths that matter ( pkg/** , specs/** ) so it runs only when specs could drift. → View the workflow on GitHub Try It Out Section titled “Try It Out” Upgrade to v1.2.1 and check the pull_request_target opt-in from v1.2.0. Feedback and contributions are welcome in github/gh-aw .
One AI reviewer that comments on everything tends to produce vague, overlapping feedback. witt3rd/review-council takes a different approach: five narrowly scoped reviewers, each a gh-aw agentic workflow compiled into a reusable workflow. A repository calls the reviewers it wants from a short caller file and gets one required commit status per reviewer on the pull request head. It is aimed at teams that want consistent, enforceable AI review across many repositories without copying prompts around.
Why it’s awesome Section titled “Why it’s awesome” Sharp scopes, one verdict each. The council has a Steward (written law and PR claims), an Architect (layers and contracts), an Inspector (bugs), a Warden (abuse) and an Editor (prose, for documents repositories). Each workflow states what is not its job. The Warden , for example, requires every finding to name a concrete path: who sends what, and what they get that they should not.
“No path, no finding” and no defense-in-depth requests “just in case” keeps the output actionable. A thin, pinned caller. caller/review-council.yml uses YAML anchors to share permissions, inputs and secrets across one job per reviewer. Each uses: is pinned to a release commit SHA with the tag as a comment, and a pins.yml workflow reports which callers lag behind the newest release. The consumer’s law is read from the base commit.
According to AGENTS.md , the council reads the repository’s principles.md and AGENTS.md from the PR’s base commit, so a PR cannot rewrite the rules it is judged by. The council holds no key and no consumer’s law: each caller supplies its own OPENROUTER_API_KEY . Defensive by default. Reviewers only run on non-draft, same-repo pull requests, because fork PRs get no secrets. Permissions are read-only for contents and pull requests.
Turns and minutes are bounded ( max-turns: 100 , timeout-minutes: 40 ), and a newer push cancels the review of the older head. Evaluated releases. Releases are tagged only when an eval run on golden pull requests passes. The fixtures carry planted defects and even a prompt injection on purpose. The changelog records eval scores and spend; AGENTS.md cites roughly $0.80 for five reviewers on a small PR. How it works Section titled “How it works” Each reviewer is a .md source under .github/workflows/ with an on: workflow_call trigger, compiled by a pinned gh-aw version into a .lock.yml that callers reference.
The shared contract (review format, rounds, memory and the verdict rule) lives once in .github/workflows/shared/ , so the five frontmatters are identical apart from the description, name and a reviewer input default. Two details show real gh-aw experience. Every lock uses inlined-imports: true , because when called from another repository nothing from the council repository is on disk. And because github.workflow is the caller’s name inside a called workflow, status names and concurrency IDs use the reviewer’s fixed name, and the verdict is set on pull_request.head.sha .
CI recompiles the locks and requires no diff. Try it Section titled “Try it” The adoption steps in AGENTS.md are short: Copy caller/review-council.yml to .github/workflows/review-council.yml and keep the reviewers you want, pinned to a release SHA. Copy caller/principles.md to .github/review-council/principles.md and write your own principles and che
The rest of this page is on the live site.