gsd-inbox

Fetch, classify, and validate GitHub issues and PRs against project templates.

Updated Jan 28, 2025
One-click install
npx skills add https://github.com/aslaii/dotfiles --skill gsd-inbox-aslaii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-inbox
Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-inbox
Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-inbox-aslaii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and streamline the review of open GitHub issues and PRs by validating submissions against repository templates and contribution guidelines, reducing manual overhead for maintainers.

Core Features & Use Cases

  • Automatically fetches all open issues and PRs from a repository.
  • Classifies each submission by type (feature, bug, enhancement, chore) and checks it against the corresponding template requirements.
  • Applies labels or comments to non-compliant items and can close them when necessary.

Quick Start

Run the inbox triage on your repository to classify, validate, and label open issues and PRs.

Frequently Asked Questions about gsd-inbox

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

FAQPage Schema
How do I automatically triage open GitHub issues and pull requests?

It validates open GitHub issues and PRs against standardized repository templates and contribution guidelines by fetching submissions, classifying them by type, and reporting compliance findings to reduce manual review overhead.

Can I automatically close non-compliant GitHub issues that fail template validation?

Yes, you can close non-compliant GitHub issues that fail template validation. This Skill identifies submissions missing required template information and optionally applies labels, comments, or closes them based on your project guidelines.

Does automated issue triage work with custom contribution guidelines and templates?

Automated issue triage works specifically with repositories using standardized templates and contribution guidelines. It checks open issues and PRs against these established formats to validate submission compliance.

What is the best way to label invalid GitHub pull requests missing template fields?

The best way to label invalid GitHub pull requests missing template fields is to run an automated triage workflow. It validates PRs against contribution guidelines and applies labels to flag non-compliant submissions for review.

How do I classify GitHub issues by type for automated repository triage?

To classify GitHub issues by type for automated triage, this Skill fetches all open submissions and categorizes them into types like feature, bug, enhancement, and chore before validating against corresponding template requirements.