skills.rest
jeremylongshore
jeremylongshoreCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

repo-scanning

Scan GitHub repositories to gather evidence for bug cluster analysis.

Updated Mar 23, 2026
Search Tags:#automation#github#evidence#triage#scanning#bug#repo
One-click install
npx skills add https://github.com/jeremylongshore/x-bug-triage-plugin --skill repo-scanning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-scanning
Source: https://github.com/jeremylongshore/x-bug-triage-plugin/tree/main/skills/repo-scanning
Command: npx skills add https://github.com/jeremylongshore/x-bug-triage-plugin --skill repo-scanning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scanning GitHub repositories to collect evidence that explains bug clusters, enabling faster root cause analysis and more reliable triage.

Core Features & Use Cases

  • Stepwise repository scanning to gather open issues, recent commits, code-path changes, and deploy history for evidence.
  • Evidence tiering to prioritize strongest signals guiding triage decisions.
  • Degradation handling to continue operation and report failures when repos or API calls fail.

Quick Start

Process clusters by triggering the repo-scanner agent to collect evidence for mapped repositories.

Frequently Asked Questions about repo-scanning

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

FAQPage Schema
How do I automate GitHub repo scanning to gather evidence for bug triage?▼

Automating GitHub repo scanning involves triggering a stepwise agent workflow to collect open issues, recent commits, code-path changes, and deploy history as evidence for bug triage. The process scans up to three mapped repositories per cluster to identify root causes.

What is evidence tiering when scanning GitHub repositories for bug clusters?▼

Evidence tiering is the process of prioritizing the strongest signals gathered from GitHub repository scans to guide triage decisions. It ranks collected evidence from issues, commits, and deploy history to highlight the most critical data explaining bug clusters.

Can I scan multiple GitHub repositories for a single bug cluster?▼

Yes, you can scan multiple GitHub repositories for a single bug cluster. The scanning workflow prioritizes up to three mapped repositories per cluster, gathering issues, commits, code-path changes, and deploy history to explain the cluster.

What happens if a GitHub repository is unavailable during bug triage scanning?▼

When a GitHub repository is unavailable during bug triage scanning, the workflow degrades gracefully and continues operation. It handles API failures by skipping unavailable repos and reports the failures while completing the evidence gathering for remaining mapped repositories.

How do I analyze code-path changes and deploy history to explain bug clusters?▼

Analyzing code-path changes and deploy history to explain bug clusters requires a stepwise scanning workflow that inspects recent commits and deployment records. This evidence gathering identifies correlations between code modifications and clustered bug occurrences.

Does the repo scanning workflow search GitHub issues as part of bug triage?▼

Yes, the repo scanning workflow searches GitHub issues as part of bug triage. The step-by-step process includes issue search, commit inspection, code-path analysis, and deploy checks to gather comprehensive evidence explaining bug clusters.

Related Skills

Explore More Software Engineering Skills→
tutur3ututur3u
53

github

Automate GitHub issue, PR, CI, and API tasks via gh CLI.

Official
Intermediate
VictorHueniVictorHueni

ops-bug-rca

Run a structured 4-phase bug root cause analysis with Python.

Community
Advanced
prismaprisma
419

create-pr

Generate GitHub pull requests with conventional commit titles and narrative descriptions.

Official
Advanced
ArabelaTsoArabelaTso
142

szz-bug-introducing-commit-identifier

Identify bug-introducing commits using SZZ-style analysis with git and Python 3.

Community
Advanced