gsd-inbox

Categorize and triage GitHub issues and pull requests against project templates.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-inbox-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-inbox
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-inbox
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-inbox-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and review all open GitHub issues and PRs against project templates and contribution guidelines.

Core Features & Use Cases

  • Classify each open issue and PR by type (feature, bug, enhancement, chore) and verify against the corresponding template.
  • Review submissions against repository contribution guidelines and report completeness and compliance.
  • Optionally apply labels or close non-compliant submissions with a clarifying comment.

Quick Start

Run the inbox triage command with appropriate flags to review issues and PRs and optionally apply labels or close noncompliant items.

Frequently Asked Questions about gsd-inbox

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

FAQPage Schema
How do I automate GitHub issue triage and labeling for pull requests?

Automate GitHub issue triage by evaluating open submissions against repository templates and contribution guidelines, classifying items by type, and optionally applying labels or closing non-compliant entries.

What is the best way to check if GitHub issues match project templates?

Check GitHub issues against templates by running automated conformity checks that review repository metadata, verify submission completeness, and generate a consolidated compliance report for maintainers.

Can I close non-compliant GitHub pull requests automatically?

Yes, you can close non-compliant GitHub pull requests automatically by enabling the option to close submissions that fail template checks, which leaves a clarifying comment explaining the compliance failure.

How do I categorize open GitHub issues by type for maintainer review?

Categorize open GitHub issues by type, such as feature, bug, enhancement, or chore, by executing automated checks that verify each submission against the corresponding project template.

Does this GitHub triage process scope to issues, pull requests, or both?

Yes, the GitHub triage process respects scoping flags, allowing you to limit automated template checks and labeling actions to only issues, only pull requests, or both simultaneously.