gsd-inbox

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

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-inbox-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-inbox
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-inbox
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-inbox-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams quickly review incoming GitHub issues and pull requests to ensure they match the project’s templates and contribution guidelines, reducing missed requirements and inconsistent submissions.

Core Features & Use Cases

  • Inbox triage with template compliance checks: Fetches open issues and PRs, classifies them by type, and verifies completeness against the appropriate template fields.
  • Actionable reporting and optional remediation: Produces a compliance report and can optionally apply labels or close items that fail requirements with an explanation.
  • Targeted scope control: Limits reviews to issues or PRs and supports running against a specific repository override.

Quick Start

Run the gsd-inbox skill to review all open issues and PRs in your repository, then automatically label compliant items and optionally close non-compliant submissions.

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 for template compliance?

To triage open GitHub issues and pull requests for template compliance, you can run an automated inbox review that classifies items by type and verifies required template fields are complete before acceptance.

What is the best way to enforce contribution guidelines on incoming GitHub submissions?

The best way to enforce contribution guidelines is to automatically check incoming submissions against project templates, apply labels to compliant items, and close non-compliant submissions with explanatory comments.

Can I automatically label or close non-compliant GitHub submissions?

Yes, you can automatically label or close non-compliant GitHub submissions. The triage process optionally applies labels to compliant items and closes incomplete submissions while adding explanatory comments for the author.

How do I filter the triage process to only review GitHub issues or PRs?

You can filter the triage process to only review GitHub issues or PRs by using targeted scope control, which explicitly limits the classification and template compliance checks to your specified item type.

Does this triage process work with a specific repository override?

Yes, this triage process works with a specific repository override. It enforces repository detection by default but supports providing a specific repository override to review issues and PRs outside the current context.

Why are my GitHub issue triage workflows missing required template fields?

GitHub issue triage workflows miss required template fields when submissions lack automated classification and completeness checks against the appropriate template fields before acceptance into the repository.