gsd-inbox

Triage GitHub issues and pull requests against project templates and contribution guidelines.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-inbox-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-inbox
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-inbox
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-inbox-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the time-consuming task of manually reviewing GitHub issues and PRs to ensure they follow the right templates and contribution guidelines.

Core Features & Use Cases

  • One-command inbox triage: Fetches all open issues and pull requests from the target repository in a single run.
  • Template compliance review: Classifies each submission by type (feature, enhancement, bug, chore, fix PR, enhancement PR, feature PR) and checks it against the corresponding template requirements.
  • Optional enforcement actions: Can auto-apply recommended labels and optionally close submissions that fail template compliance with an explanatory comment.

Quick Start

Run the inbox triage for your repository by asking: "Triage open issues and PRs, apply recommended labels, and close anything that is not template-compliant."

Frequently Asked Questions about gsd-inbox

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

FAQPage Schema
How do I triage GitHub issues and pull requests in one pass?

To triage GitHub issues and pull requests, fetch all open items from your repository in a single run and review them against project templates and contribution guidelines for consistent classification.

Can I automatically close non-compliant GitHub pull requests?

Yes, you can automatically close non-compliant GitHub pull requests and issues by applying recommended labels and leaving an explanatory comment when submissions fail template compliance checks.

What issue types are supported for label automation during repo maintenance?

Label automation during repo maintenance supports classifying feature, enhancement, bug, and chore issues, alongside fix and feature pull requests, mapping each item to the correct template.

Does this work for high-throughput contribution guidelines enforcement?

Yes, it is designed for repository maintainers who need consistent, high-throughput compliance checks across multiple submission patterns without manually reviewing every open item.