Reduce GitHub API calls during issue monitoring by scanning basic issue details first, then fetching full descriptions and comments only for selected issues. Filters use assignees, status labels, and title patterns to narrow the list.
Cuts GitHub API calls by separating lightweight list scanning from full hydration
Review the instructions the agent will receive before you install.
Confidence: high Domain: work-monitoring Last validated: 2026-03-24
Cuts GitHub API calls from N+1 to ~7 per round (~72% reduction) by separating list scanning from full hydration. Addresses the scanning inefficiency described in issue #596.
gh issue list --state open --json number,title,labels,assignees --limit 100
Skip hydration if ANY of these match:
| Condition | Skip reason |
|---|---|
assignees non-empty AND no status:needs-review | Already owned |
Labels contain status:blocked or status:waiting-external | Externally gated |
Labels contain status:done or status:postponed | Closed loop |
Title matches stale/noisy pattern ([chore], [auto]) | Low-signal |
For each issue surviving Pass 1:
gh issue view <number> --json number,title,body,labels,assignees,comments,state
Then apply normal Ralph triage logic. Rule of thumb: hydrate ≤ 30% of scanned list. If more than 30% survive Pass 1, tighten filter rules.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.
Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.
Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.
Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.
Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.
Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.