π Repository Snapshot
verkyyi/github-agent-runner β Claude Code plugin to discover and install GitHub agentic workflows into your repo.
π¦ Release Status
Latest release: v0.2.1 β shipped April 20, 2026
Notable v0.2.1 highlights:
- β‘ Implementer "trust the plan" directive: 20m54s β 6m41s (β68% wall-clock)
- π‘οΈ Workflow-scope preflight catches first-time OAuth gotchas before half-installs
- π
safe-outputs.threat-detection: false saves ~4 min per full agent-team run
- π§ͺ Tier-1 + tier-2 test framework added, CI green in under 80s
π§ Code Activity
Last commit to main: April 23, 2026 β d688265 β fix agent-team manual workflow_dispatch inputs (#69)
The codebase has been stable for 25 days. β
π Open Issue Backlog (15 enhancement/bug issues)
A rich set of improvements identified during the v0.2.0 dogfood session is waiting for action:
π Bugs (high priority)
| # |
Title |
#47 |
install-agent-team: pin catalog SHA instead of @main (workaround for gh-aw#27407) |
#57 |
install-agent-team: pre-flight checks (labels, lock files, canary dispatch) |
#53 |
Reviewer agent should run the test command and fail-closed on skip |
#48 |
Raise implementer timeout to 20 min + add npm/pip cache guidance |
β¨ Enhancements (agent-team pipeline)
| # |
Title |
#50 |
Thread spec/plan/impl run_id through dispatch inputs for deterministic reviewer summary |
#51 |
On stage failure, post a self-describing retry comment on the parent issue |
#52 |
Implementer writes a pipeline-state table at top of PR; reviewer updates it |
#49 |
Add opt-in human checkpoint after spec (state:spec-approved) |
#54 |
Wrap superseded spec/plan/review blocks in <details> tags on next iteration |
#56 |
Support .agent-team.yml for per-stage timeouts, test commands, and model overrides |
β¨ Enhancements (plugin-level)
| # |
Title |
#60 |
Ship /sync-workflows skill to orchestrate plugin + gh-aw updates |
#58 |
Ship a consumer-facing feedback skill that analyzes runs and drafts upstream issues |
#61 |
Codex engine: evaluate subscription auth path alongside Claude OAuth tweak |
#59 |
test-e2e: handle playground state race between concurrent --install-from-ref runs |
π¨ Draft PR Backlog β Needs Triage
The update-docs workflow has generated ~20 draft PRs (all from github-actions[bot]) covering the same 3β4 documentation gaps since April 28. The most recent is #123 (May 17).
All cover:
gh workflow run examples for manual re-dispatch after input propagation failures
state:in-progress β agent-team:reviewed label fix in README uninstall instructions
- "No automated test harness" claim fix in
CONTRIBUTING.md
## Publishing section in README.md
Recommended action: Review and merge #123, then close the older drafts.
β° Overdue: awesome-claude-code Submission
Issue #63 has been open since April 21. The form was ready to submit from April 26 onward β that deadline passed 22 days ago. The submission goes to the hesreallyhim/awesome-claude-code repo via web UI only.
β
Recommended Next Steps
- Merge
#123 β most up-to-date docs PR; verify gh workflow run commands match the workflow_dispatch.inputs blocks in each agent .md file, then merge
- Close draft PRs
#83β#121 β docs will be current after #123 merges; close older drafts with a pointer to #123
- Submit to awesome-claude-code β follow the web UI instructions in
#63 and close the issue
- Tag v0.2.2 β the d688265 fix (fail-loud on bad dispatch inputs) is user-visible and deserves a release entry
- Pick a bug from the backlog β
#47 (SHA pinning) and #57 (pre-flight checks) have the highest user-impact per effort
π‘ Project Health
| Metric |
Status |
| CI |
β
Green (tier-1 + tier-2, ~80s) |
| Latest release |
v0.2.1 (Apr 20) |
| Days since last code commit |
25 |
| Open enhancement/bug issues |
15 |
| Draft docs PRs pending triage |
~20 |
| awesome-claude-code submission |
β οΈ Overdue (ready since Apr 26) |
The core plugin is solid and CI is green! The main housekeeping tasks are the draft PR triage and the overdue catalog submission. After those land, a v0.2.2 tag would round things off nicely. π
Generated by Daily Repo Status Β· β·
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/daily-repo-status.md@96b9d4c39aa22359c0b38265927eadb31dcf4e2a
Generated by Daily Repo Status Β· β·
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/daily-repo-status.md@96b9d4c39aa22359c0b38265927eadb31dcf4e2a
π Repository Snapshot
verkyyi/github-agent-runner β Claude Code plugin to discover and install GitHub agentic workflows into your repo.
π¦ Release Status
Latest release: v0.2.1 β shipped April 20, 2026
Notable v0.2.1 highlights:
safe-outputs.threat-detection: falsesaves ~4 min per full agent-team runπ§ Code Activity
Last commit to
main: April 23, 2026 βd688265β fix agent-team manual workflow_dispatch inputs (#69)The codebase has been stable for 25 days. β
π Open Issue Backlog (15 enhancement/bug issues)
A rich set of improvements identified during the v0.2.0 dogfood session is waiting for action:
π Bugs (high priority)
#47install-agent-team: pin catalog SHA instead of@main(workaround for gh-aw#27407)#57install-agent-team: pre-flight checks (labels, lock files, canary dispatch)#53#48β¨ Enhancements (agent-team pipeline)
#50spec/plan/implrun_id through dispatch inputs for deterministic reviewer summary#51#52#49state:spec-approved)#54<details>tags on next iteration#56.agent-team.ymlfor per-stage timeouts, test commands, and model overrides⨠Enhancements (plugin-level)
#60/sync-workflowsskill to orchestrate plugin + gh-aw updates#58#61#59test-e2e: handle playground state race between concurrent--install-from-refrunsπ¨ Draft PR Backlog β Needs Triage
The
update-docsworkflow has generated ~20 draft PRs (all fromgithub-actions[bot]) covering the same 3β4 documentation gaps since April 28. The most recent is#123(May 17).All cover:
gh workflow runexamples for manual re-dispatch after input propagation failuresstate:in-progressβagent-team:reviewedlabel fix in README uninstall instructionsCONTRIBUTING.md## Publishingsection inREADME.mdRecommended action: Review and merge
#123, then close the older drafts.β° Overdue: awesome-claude-code Submission
Issue
#63has been open since April 21. The form was ready to submit from April 26 onward β that deadline passed 22 days ago. The submission goes to thehesreallyhim/awesome-claude-coderepo via web UI only.β Recommended Next Steps
#123β most up-to-date docs PR; verifygh workflow runcommands match theworkflow_dispatch.inputsblocks in each agent.mdfile, then merge#83β#121β docs will be current after#123merges; close older drafts with a pointer to#123#63and close the issue#47(SHA pinning) and#57(pre-flight checks) have the highest user-impact per effortπ‘ Project Health
The core plugin is solid and CI is green! The main housekeeping tasks are the draft PR triage and the overdue catalog submission. After those land, a v0.2.2 tag would round things off nicely. π