gsd-inbox

Review open GitHub issues and pull requests against contribution templates.

4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-inbox-electroheadfx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-inbox
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-inbox
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-inbox-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly review a project's open GitHub issues and pull requests against the repository's contribution templates and guidelines, reducing manual inbox triage overhead.

Core Features & Use Cases

  • Inbox triage: Fetch and classify open issues and PRs so you can see what needs attention first.
  • Template compliance review: Check submissions against the expected requirements for features, enhancements, bugs, chores, and PR types.
  • Optional enforcement actions: Apply labels or close incomplete submissions when the workflow calls for it.
  • Use case: A maintainer wants to audit all open repository submissions, identify incomplete reports, and standardize the queue before a release cycle.

Quick Start

Use the gsd-inbox skill to review this repository's open issues and pull requests and summarize any template violations.

Frequently Asked Questions about gsd-inbox

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

FAQPage Schema
How do I triage open GitHub issues and pull requests against project templates?

To triage open GitHub issues and pull requests, this Skill fetches open submissions and validates them against repository contribution templates, checking if bug reports, features, and PRs meet required guidelines before classifying them.

Can I automatically close incomplete GitHub issues that violate contribution guidelines?

Yes, you can automatically close incomplete GitHub issues that violate contribution guidelines. This Skill supports optional enforcement actions that apply labels or close submissions when template compliance checks fail during repository maintenance workflows.

How does template compliance validation work for GitHub pull requests?

Template compliance validation for GitHub pull requests works by fetching open PRs and checking their content against repository-specific templates. The Skill reviews submissions for required fields and formats, then flags violations for features, enhancements, bugs, or chores.

Do I need any special permissions to fetch and label GitHub issues for triage?

Fetching and labeling GitHub issues for triage requires standard repository access permissions. The Skill performs repository detection, issue and PR fetching, and optional labeling or closure actions, so appropriate write access is needed if enforcement actions are applied.

What's the best way to standardize a GitHub issue queue before a release cycle?

The best way to standardize a GitHub issue queue before a release cycle is auditing all open submissions against contribution templates. This Skill identifies incomplete reports and applies labels or closes violations to ensure the queue meets compliance standards.

When should I not use automated triage for GitHub repository maintenance?

Automated triage for GitHub repository maintenance should not be used when repositories lack defined contribution templates or guidelines. The Skill requires template-specific validation rules to check submissions, so without templates the compliance checks cannot function properly.