跳到正文
cccskills
免费在 GitHub 公开

ralph-two-pass-scan

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

集成工具GitHub
查看安装方法

适用场景

  • Reducing API calls during recurring issue monitoring
  • Filtering out assigned or blocked issues
  • Fetching descriptions and comments only for relevant issues

包含的文件(1)

  • SKILL.md1.3 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Skill: Ralph — Two-Pass Issue Scanning

Confidence: high Domain: work-monitoring Last validated: 2026-03-24

Context

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.

Pattern

Pass 1 — Lightweight Scan

gh issue list --state open --json number,title,labels,assignees --limit 100

Skip hydration if ANY of these match:

ConditionSkip reason
assignees non-empty AND no status:needs-reviewAlready owned
Labels contain status:blocked or status:waiting-externalExternally gated
Labels contain status:done or status:postponedClosed loop
Title matches stale/noisy pattern ([chore], [auto])Low-signal

Pass 2 — Selective Hydration

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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示英语简介。

  • Locate team files across separate working directories
  • Record decisions that affect other agents
  • Request input from another specialist
github/gh-aw54222026年10月20日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Share development rules across multiple agents
  • Keep team-specific agent names out of code and tests
  • Check affected tests before declaring work complete
github/gh-aw54222026年10月20日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Designing a new workflow through questions
  • Investigating failed runs and recurring errors
  • Upgrading workflows and addressing deprecations
github/gh-aw54222026年10月20日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Proposing a major architecture change
  • Replanning milestones after a foundation change
  • Comparing technical options before seeking approval
github/gh-aw54222026年10月20日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Updating the firewall version used by gh-aw
  • Reviewing release notes for integration changes
  • Checking configuration schema differences
github/gh-aw54222026年10月20日 更新

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.

中文简介正在准备中。当前显示英语简介。

  • Reviewing git operations after repository checkout
  • Checking tokens for private cross-repository access
  • Reviewing sparse and shallow checkout changes
github/gh-aw54222026年10月20日 更新

查看 github 的全部技能

报告此技能的问题