skills.rest
1thirteeng3
1thirteeng3COMMUNITY
Explore all skills by this author →
GitHub

github-triage

Analyze open GitHub issues and PRs and generate evidence-backed reports.

Updated Mar 24, 2026
Search Tags:#automation#reports#github#evidence#triage#read-only#permalink
One-click install
npx skills add https://github.com/1thirteeng3/greenmoire --skill github-triage-1thirteeng3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/1thirteeng3/greenmoire/tree/main/integrations/oh-my-openagent/.opencode/skills/github-triage
Command: npx skills add https://github.com/1thirteeng3/greenmoire --skill github-triage-1thirteeng3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only GitHub triage for issues and PRs that analyzes all open items and generates evidence-backed reports without mutating GitHub state.

Core Features & Use Cases

  • 1 item = 1 background task (category: quick). Analyzes all open issues and PRs and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof.
  • ZERO GitHub mutations; reports only; per-item evidence required in each report.
  • Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.

Quick Start

Run the github-triage workflow to analyze all open items and generate per-item reports in /tmp.

Frequently Asked Questions about github-triage

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

FAQPage Schema
How do I generate evidence-backed triage reports for open GitHub issues and PRs?▼

To generate evidence-backed triage reports for open GitHub issues and PRs, run a triage workflow that analyzes all open items read-only and writes per-item reports to a temporary directory, requiring a GitHub permalink as proof for every claim.

Can I automate GitHub triage without modifying repository state?▼

Yes, you can automate read-only GitHub triage without modifying repository state by enforcing a zero-action policy that only analyzes open issues and PRs to produce reports without mutating any GitHub data.

What is the best way to triage all open GitHub items at scale?▼

The best way to triage all open GitHub items at scale is to spawn a background quick subagent per item, analyzing each open issue and PR individually to generate evidence-backed reports with permalinks.

Does GitHub triage require write permissions to generate issue reports?▼

No, GitHub triage does not require write permissions to generate issue reports because it operates with a read-only policy and stores the resulting evidence-backed reports in a write-only local directory.

Why should I use permalinks in GitHub issue triage reports?▼

You should use permalinks in GitHub issue triage reports because every claim requires a GitHub permalink as proof, ensuring all evidence is verifiable and permanently accessible.

Related Skills

Explore More Software Engineering Skills→
gerald-icagerald-ica

github-triage

Analyze open GitHub issues and PRs into evidence-backed triage reports.

Community
Advanced
howlowckhowlowck
2

github-triage

Analyze open GitHub issues and PRs with read-only GET requests and generate evidence-backed reports.

Community
Advanced
openclawopenclaw
9.3k

clawhub-pr-maintainer

Summarize ClawHub GitHub issues and pull requests with CI and review evidence.

Official
Intermediate
code-yeongyucode-yeongyu
67.6k

github-triage

Fetch and classify open GitHub issues and pull requests into reports.

Community
Advanced