gh-issue-triage

Triage GitHub issues and extract contributor profiles for credits.

729|67|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/joelhooks/swarm-tools --skill gh-issue-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issue-triage
Source: https://github.com/joelhooks/swarm-tools/tree/main/.opencode/skill/gh-issue-triage
Command: npx skills add https://github.com/joelhooks/swarm-tools --skill gh-issue-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires zod, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the triage of GitHub issues by analyzing the report, extracting contributor profiles for accurate credits, and generating actionable tracking cells to streamline resolution.

Core Features & Use Cases

  • Automatic issue analysis to classify issues as bug, feature, or question, and to request clarifications when needed.
  • Contributor profile extraction to capture login, name, Twitter handle, blog, and bio for precise credits in changesets.
  • Cell generation and credit workflow to file tracking cells, tag issues, and store context in semantic memory for future reference.
  • Output templates for changeset credits and memory-store commands to accelerate release workflows.

Quick Start

Run the triage workflow on an issue to generate a summary, contributor profile, and ready-to-paste credits: bun run scripts/issue-summary.ts <owner/repo> <number> This outputs: issue summary, a cell template, and a ready-to-paste changeset credit and semantic-memory_store command.

Frequently Asked Questions about gh-issue-triage

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

FAQPage Schema
How do I automate GitHub issue triage to classify reports and request clarifications?

Automate GitHub issue triage by analyzing reports to classify them as bugs, features, or questions, and automatically requesting clarifications when details are missing. This process uses the GitHub CLI to streamline repository management and resolution tracking.

How do I extract contributor profiles for changeset credits from GitHub issues?

Extract contributor profiles for changeset credits by analyzing GitHub issues to capture the login, name, Twitter handle, blog, and bio of reporters. This generates ready-to-paste credit templates to accurately attribute work in your release workflows.

How do I generate tracking cells for GitHub issues to tag work for resolution?

Generate tracking cells for GitHub issues by creating structured summaries and cell descriptions that tag work for resolution. This workflow stores context in semantic memory, providing ready-to-use templates to accelerate future release workflows.

Can I use Bun scripts and Zod validation to analyze GitHub issues across repositories?

Yes, you can use Bun scripts and Zod validation to analyze GitHub issues across repositories. The script relies on the GitHub CLI and Zod to validate inputs, producing structured summaries and tracking cells for accurate, automated triage.

What is the best way to streamline GitHub issue resolution using semantic memory?

Streamline GitHub issue resolution by generating tracking cells and storing issue context in semantic memory for future reference. This approach pairs cell generation with semantic memory store commands to accelerate release workflows and maintain context.