gsd-inbox

Triage GitHub issues and PRs against project templates and contribution requirements.

1|Updated Sep 6, 2015

Search Tags:#github #issue triage #repository maintenance #contribution guidelines #pull request review #template compliance #labeling automation

Ready to run

npx skills add https://github.com/deerawan/dotfiles --skill gsd-inbox-deerawan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-inbox
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-inbox
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-inbox-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the time-consuming manual effort of reviewing open GitHub issues and PRs, ensuring submissions match the project’s templates and contribution guidelines.

Core Features & Use Cases

Inbox triage for issues and PRs: Reviews open issues and/or PRs and classifies each submission by likely type (e.g., feature, enhancement, bug, chore).
Template compliance checks: Verifies that required template sections are present and that the submission aligns with the expected contribution format.
Optional corrective actions: Can auto-apply recommended labels and close non-compliant items with an explanatory comment.

Quick Start

Run gsd-inbox with your repo context and choose whether to review only issues, only PRs, or both.

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 check pull requests against contribution guidelines?▼

Automating GitHub issue triage involves fetching open inbox items and matching each submission against project templates to verify required sections. This Skill classifies issues and PRs by type like feature or bug, scoring completeness and optionally applying labels to enforce contribution guidelines.

What is template compliance for open GitHub pull requests and how does it work?▼

Template compliance for GitHub pull requests means verifying that submissions contain required template sections and align with expected contribution formats. The mechanism fetches PRs, checks them against template expectations, reports compliance results, and optionally applies labels or closes incomplete submissions.

Can I use labeling automation to close non-compliant GitHub issues automatically?▼

Yes, you can use labeling automation to close non-compliant GitHub issues automatically. This Skill applies recommended labels to open issues and PRs and can close incomplete submissions with an explanatory comment after checking them against repository templates.

What's the best way to classify GitHub pull requests by type for repository maintenance?▼

The best way to classify GitHub pull requests for repository maintenance is to automate the triage process against contribution requirements. This Skill classifies submissions by likely type including feature, enhancement, bug, chore, and fix, providing rapid classification and consistency enforcement.

Do I need project templates to run automated pull request review and completeness scoring?▼

Yes, you need project templates to run automated pull request review and completeness scoring. The Skill matches each open PR against the appropriate template expectations to report compliance results and enforce consistency across feature, bug, and chore categories.

Why does my GitHub repository maintenance struggle with inconsistent issue triage?▼

GitHub repository maintenance struggles with inconsistent issue triage when submissions lack template compliance and proper labeling. Automating the triage of open issues and PRs enforces contribution guidelines, applies labels, and closes incomplete submissions to maintain repository consistency.