Skip to content
Back to skills

Ralph Two Pass Scan

ASecurity

Cuts GitHub API calls by separating lightweight list scanning from full hydration

  • 802 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
ai-agentsgitapi

Works with

  • api

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add sbroenne/mcp-server-excel --skill ralph-two-pass-scan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ralph Two Pass Scan?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ralph Two Pass Scan
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sbroenne-ralph-two-pass-scan/badge)](https://www.skillsdirectory.com/skills/sbroenne-ralph-two-pass-scan)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "ralph-two-pass-scan"
description: "Cuts GitHub API calls by separating lightweight list scanning from full hydration"
domain: "work-monitoring"
confidence: "high"
source: "extracted"
---

# 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:**

| 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 |

### 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…