gh-issue-triage

Extracts GitHub contributor profiles and generates credit-ready changelog snippets for issues.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ImBIOS/swarm-tools --skill gh-issue-triage-imbios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issue-triage
Source: https://github.com/ImBIOS/swarm-tools/tree/main/.opencode/skill/gh-issue-triage
Command: npx skills add https://github.com/ImBIOS/swarm-tools --skill gh-issue-triage-imbios

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

GitHub issues are conversations that often lack structured profiling and clear credits. This workflow automates contributor profile extraction and applies credits to changesets, improving accountability and traceability.

Core Features & Use Cases

  • Analyze issues to determine type (bug, feature, question) and extract contributor profile data
  • Create and tag hive cells to track work, including a description and linked issue
  • Capture contributor credits in changesets using profile data (name, twitter, blog) and store in semantic memory for future attribution
  • Integrate with semantic memory and hive-based coordination to streamline triage and completion

Quick Start

Provide the repository and issue number to start triage, and the system will extract the contributor profile, file a tracking cell, tag the issue, and prepare a credit-ready changeset snippet.

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 for open-source repositories?

Automate GitHub issue triage by extracting contributor profiles and generating structured credits for changesets. This workflow analyzes issue types, tags tracking cells, and prepares credit-ready snippets to improve accountability for open-source contributions.

How does automated issue triage capture contributor credits for changesets?

Automated issue triage captures contributor credits by extracting profile data like name, Twitter handle, and blog links from GitHub issues. It stores this information in a semantic memory store to apply accurate attribution to changesets.

What do I need to integrate to start triaging GitHub issues with automated tracking?

To start triaging GitHub issues, you need integration with GitHub issue data, a semantic memory store for credits, and an automated hive-based task tracker. Provide a repository name and issue number to trigger the workflow.

Can I use zod for schema validation in automated GitHub issue triage scripts?

Yes, the automated GitHub issue triage scripts use zod for schema validation during deterministic execution. This ensures structured profiling data and changeset credits are correctly validated before being stored in semantic memory.

What is the best way to track hive cells for GitHub issues requiring clarification?

The best way to track hive cells for GitHub issues is to create and tag cells with a description and linked issue during triage. This integrates with hive-based coordination to streamline analysis, tagging, and implementation tracking.

Why does GitHub issue triage require a semantic memory store for contributor profiles?

GitHub issue triage requires a semantic memory store to persist contributor profile data extracted from issues. This ensures future attribution and traceability when applying credits to changesets across multiple open-source workflows.