ralph-two-pass-scan

Name: ralph-two-pass-scan
Availability: InStock
Author: nicolehaugen

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

Updated Apr 8, 2026

Search Tags:#GitHub #efficiency #triage #API optimization #issue scanning

Ready to run

npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill ralph-two-pass-scan-nicolehaugen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ralph-two-pass-scan
Source: https://github.com/nicolehaugen/CustomMetricsDashboard/tree/main/.squad/templates/skills/ralph-two-pass-scan
Command: npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill ralph-two-pass-scan-nicolehaugen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Reduces the number of GitHub API calls required for scanning issues, thus increasing efficiency and performance.

Core Features & Use Cases

Two-Pass Scanning: Cuts API calls by 72%, optimizing issue scanning efficiency.
Custom Filter Conditions: Offers detailed skip conditions based on assignees, labels, and issue states.
Selective Hydration: Hydrates only a targeted 30% of issues that pass the first scan to further analyze.
Triage Logic Integration: Applies Ralph triage logic on the selectively hydrated issues.
Use Case: This Skill can be used by GitHub administrators to improve the scanning of open issues within an organization.

Quick Start

Run the scan with the 'gh issue list --state open --json number,title,labels,assignees --limit 100' command.

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 a large number of open issues?▼

A two-pass scan reduces GitHub API calls by performing an initial lightweight scan, then selectively hydrating only the 30% of issues that pass the first filter for further triage analysis.

Can I filter GitHub issues by assignees and labels during the scanning process?▼

Custom skip conditions allow filtering GitHub issues by assignees, labels, and issue states during the initial scan pass, ensuring only relevant issues proceed to selective hydration.

What is the best way to triage open issues in large GitHub repositories without hitting rate limits?▼

Two-pass scanning is ideal for large GitHub repositories, decreasing API calls per round by 72% through an initial lightweight scan and subsequent selective hydration of targeted issues.

How does two-pass scanning work for GitHub issue triage?▼

Two-pass scanning performs an initial lightweight scan of GitHub issues, then applies selective hydration to only the targeted 30% of issues passing the first scan, enabling deeper triage logic integration.

Does this GitHub issue scanning approach work for organizations with complex issue management scenarios?▼

Designed for GitHub administrators managing large repositories with complex issue scenarios, this two-pass scanning approach improves efficiency by significantly reducing API calls per round.