gsd-inbox

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-inbox-beibei-clic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-inbox
Source: https://github.com/BeiBei-Clic/ai-skills/tree/main/gsd-inbox
Command: npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-inbox-beibei-clic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the overhead of manually reviewing a project’s GitHub inbox by automatically checking incoming issues and pull requests against the expected templates and contribution guidelines.

Core Features & Use Cases

  • Template compliance review: Classifies each submission (issues and PRs) by type and verifies completeness against the corresponding template requirements (e.g., feature/enhancement/bug/chore/fix PR).
  • Labeling and enforcement options: Can optionally auto-apply recommended labels after review and close non-compliant submissions when asked.
  • Repository-aware triage: Automatically detects the target repository (or lets you override it) to operate correctly across remotes.

Quick Start

Run the gsd-inbox skill to review and triage all open GitHub issues and PRs for the current repository, optionally applying labels and closing incomplete submissions.

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 PR template compliance checks?

Automate GitHub issue triage and PR template compliance checks by running a skill that fetches all open submissions, classifies them by type, and verifies completeness against project contribution guidelines.

Can I automatically label and close non-compliant GitHub pull requests?

Yes, you can automatically label and close non-compliant GitHub pull requests by enabling optional enforcement rules that auto-apply recommended labels and close incomplete submissions during the triage run.

What is the best way to classify open GitHub issues by type for repository inbox management?

The best way to classify open GitHub issues for repository inbox management is to fetch all active submissions and categorize each item as a feature, enhancement, bug, chore, or fix before reporting compliance.

Does the GitHub issue triage process work across multiple remote repositories?

Yes, the GitHub issue triage process works across multiple remotes by automatically detecting the target repository context, while also allowing you to manually override the repository target during execution.

How do I check if a pull request meets project contribution guidelines before reviewing it?

Check if a pull request meets project contribution guidelines by reviewing its completeness against the corresponding template requirements, categorizing it by type to ensure formatting adherence before manual review.

Why should I use automated workflow triage instead of manually reviewing my GitHub inbox?

Automated workflow triage removes the overhead of manually reviewing your GitHub inbox by instantly classifying all open issues and pull requests, reporting template compliance, and optionally closing incomplete entries.