skills.rest
barichter
barichterCOMMUNITY
Explore all skills by this author →
GitHub

ralph-two-pass-scan

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

Updated Apr 12, 2026
Search Tags:#github#efficiency#api optimization#issue scanning#scanning process
One-click install
npx skills add https://github.com/barichter/squad --skill ralph-two-pass-scan-barichter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralph-two-pass-scan
Source: https://github.com/barichter/squad/tree/main/.squad/skills/ralph-two-pass-scan
Command: npx skills add https://github.com/barichter/squad --skill ralph-two-pass-scan-barichter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Ralph — Two-Pass Issue Scanning Skill addresses the inefficiency of scanning GitHub issues by reducing the number of API calls and optimizing the scanning process.

Core Features & Use Cases

  • API Call Reduction: Cuts GitHub API calls from N+1 to ~7 per round, significantly reducing the load on the API.
  • Selective Hydration: Hydrates only the necessary issues, minimizing the data processing required.
  • Scanning Efficiency: Enhances the efficiency of GitHub issue scanning, particularly useful for large repositories.

Quick Start

Run the Ralph — Two-Pass Issue Scanning Skill to streamline your GitHub issue scanning process.

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 reduce GitHub API calls when scanning issues in large repositories?▼

Implementing a two-pass scanning process reduces GitHub API calls for issue scanning from N+1 to roughly 7 per round. This approach selectively hydrates only necessary issues, significantly optimizing API usage and data processing for large repositories.

What is two-pass issue scanning and how does it optimize API usage?▼

Two-pass issue scanning is a process that reduces GitHub API calls by scanning issues first, then selectively hydrating only the necessary ones. This minimizes data processing and optimizes API usage, addressing inefficiencies particularly for large repositories.

How do I handle GitHub API rate limits when scanning a large number of issues?▼

Handle GitHub API rate limits during issue scanning by using a two-pass process that reduces API calls to approximately 7 per round. By selectively hydrating only necessary issues, it minimizes the API load and enhances scanning efficiency for large repositories.

Does selective hydration work for optimizing GitHub issue scanning?▼

Selective hydration optimizes GitHub issue scanning by hydrating only the necessary issues rather than all of them. This minimizes the data processing required and significantly reduces the number of GitHub API calls needed per scanning round.

What's the best way to scan GitHub issues without hitting API call limits?▼

The best way to scan GitHub issues without hitting API limits is a two-pass scanning process that reduces API calls to roughly 7 per round. This method selectively hydrates only necessary issues, minimizing data processing and enhancing overall scanning efficiency.

Related Skills

Explore More Software Engineering Skills→
EntroVyxEntroVyx
3

github-issues

Manage GitHub issue lifecycles via CLI or REST API.

Community
Intermediate
drillandrillan

issue-reporter

Post formatted Markdown progress comments to GitHub Issues.

Community
Intermediate
workinprogress-aiworkinprogress-ai

devenv-triage-issue

Automate GitHub issue triage, classification, labeling, and duplicate detection.

Official
Advanced
nicolehaugennicolehaugen

ralph-two-pass-scan

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

Community
Advanced