Automate GitHub issue triage with gh CLI and bun scripts.
npx skills add https://github.com/primeinc/swarm --skill gh-issue-triage-primeinc
Please help me install this Agent Skill. Skill: gh-issue-triage Source: https://github.com/primeinc/swarm/tree/main/.opencode/skill/gh-issue-triage Command: npx skills add https://github.com/primeinc/swarm --skill gh-issue-triage-primeinc
GitHub issue triage is error-prone and time-consuming. This Skill automates the process by analyzing issues, extracting contributor profiles (including social handles), and preparing transplantable cells, labels, and credits to accelerate resolution.
Run the triage workflow on a repository/issue: bun run scripts/issue-summary.ts <owner/repo> <number>, then bun run scripts/get-contributor.ts <login> [<issue-number>], followed by hive and GitHub CLI actions to file the cell and apply labels.
High-intent search queries and answers about installing and using this skill.
Automating GitHub issue triage involves extracting issue details and contributor profiles to inform decision-making and accelerate resolution. This process analyzes open issues to determine their type, gathers context, and prepares transplantable cells with appropriate labels for traceability.
Contributor profiling during issue triage retrieves user profiles including names, social handles, and blogs. This data generates ready-to-paste credit lines for changesets and persists contributor context in semantic memory to coordinate credits across releases.
Yes, automated GitHub issue triage relies on the gh CLI and bun to fetch repository data and execute triage scripts. These tools extract issue details and contributor profiles necessary for the workflow to function.
Creating traceable hive cells from GitHub issues involves extracting issue context and applying labels that link back to the source issue. This approach uses the Swarm hive and semantic-memory workflow to persist results and guide implementation steps.
Generating changeset credit lines from GitHub contributor profiles involves retrieving the contributor's name, Twitter handle, and blog URL. This information is formatted into ready-to-paste credit lines to coordinate attribution across releases.
Yes, the Swarm hive and semantic-memory workflow persists GitHub issue triage context across sessions. This mechanism retains contributor profiles and issue analysis results, enabling continuous coordination of credits and implementation steps.
nahtonajAutomate GitHub issue tracking, board synchronization, and sprint planning with swarm coordination.
ImBIOSExtracts GitHub contributor profiles and generates credit-ready changelog snippets for issues.
primeincCreate, update, and track git-backed hive cells across swarm workflows.
joelhooksTriage GitHub issues and extract contributor profiles for credits.
