skills.rest
DeDuva
DeDuvaCOMMUNITY
Explore all skills by this author →
GitHub

ralph-two-pass-scan

Scan GitHub issues with lightweight fields, then hydrate selected matches.

1|Updated Apr 18, 2026
Search Tags:#automation#github#scanning#hydration#api-calls#issue-triage#two-pass
One-click install
npx skills add https://github.com/DeDuva/squad --skill ralph-two-pass-scan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralph-two-pass-scan
Source: https://github.com/DeDuva/squad/tree/main/.squad/skills/ralph-two-pass-scan
Command: npx skills add https://github.com/DeDuva/squad --skill ralph-two-pass-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Lightweight issue scanning to identify candidates without full hydration.
  • Selective hydration for a small subset of issues that require detailed data.
  • Use Case: When analyzing open issues across a large repo, perform a quick scan to filter out irrelevant items, then hydrate only those that match criteria.

Quick Start

Execute a two-pass issue scan to minimize GitHub API calls while preserving hydration when needed.

Frequently Asked Questions about ralph-two-pass-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I minimize GitHub API calls when scanning large issue lists?▼

Two-pass scanning is an issue triage technique that separates lightweight issue listing from full data hydration. It first scans open issues with minimal fields, then selectively hydrates only the subset matching predefined criteria to reduce API usage.

What is the best way to reduce GitHub API usage during open issue triage?▼

Two-pass scanning is an issue triage technique that separates lightweight issue listing from full data hydration. It first scans open issues with minimal fields, then selectively hydrates only the subset matching predefined criteria to reduce API usage.

How does two-pass scanning apply to GitHub issue triage workflows?▼

Two-pass scanning is an issue triage technique that separates lightweight issue listing from full data hydration. It first scans open issues with minimal fields, then selectively hydrates only the subset matching predefined criteria to reduce API usage.

Can I filter open issues before hydration across large GitHub repositories?▼

Two-pass scanning is an issue triage technique that separates lightweight issue listing from full data hydration. It first scans open issues with minimal fields, then selectively hydrates only the subset matching predefined criteria to reduce API usage.

Why does scanning large GitHub repositories cause excessive API calls?▼

Two-pass scanning is an issue triage technique that separates lightweight issue listing from full data hydration. It first scans open issues with minimal fields, then selectively hydrates only the subset matching predefined criteria to reduce API usage.

Related Skills

Explore More Software Engineering Skills→
nicolehaugennicolehaugen

ralph-two-pass-scan

Scan GitHub issues with two-pass filtering and selective hydration.

Community
Advanced
getty104getty104
4

triage-created-issue

Automate triage of GitHub issues labeled 'cc-issue-created' using comment history and labels.

Community
Intermediate
sefllessseflless

write-issue

Standardize GitHub issue titles, labels, and metadata for the tldraw repository.

Community
Basic
CommunityToolkitCommunityToolkit
619

ralph-two-pass-scan

Scan GitHub issues with a two-pass approach to reduce API calls.

Official
Intermediate