gsd-inbox

To triage GitHub issues and pull requests, this Skill checks open submissions against repository templates and contribution guidelines. It evaluates compliance by classifying submission types, checking completeness, and recommending follow-up actions like labeling, commenting, or closing items.

Automating GitHub inbox review involves classifying open pull requests by submission type and checking completeness against contribution guidelines. This Skill produces actionable review outcomes that drive labeling, commenting, or closing incomplete submissions to clear the queue.

Yes, you can label and close incomplete GitHub issues based on contribution guidelines. The Skill evaluates issue metadata against repository templates to determine compliance and recommends specific follow-up actions, including applying labels, requesting more information, or closing non-compliant items.

Classifying open issues requires GitHub repository access and issue or pull request metadata. The Skill uses this access to evaluate submissions against repository-specific templates and contribution guidelines, checking compliance to decide whether items should be labeled, commented on, or closed.

Yes, the GitHub triage process works for both issues and pull requests in a busy repository. It classifies each submission type, checks completeness against templates, and helps maintainers quickly identify which items are ready to merge, need more information, or should be closed.

Automated GitHub triage recommends commenting on pull requests when submissions lack required information or fail to meet template requirements. By checking pull request metadata against contribution guidelines, the Skill identifies incomplete items and suggests follow-up comments to request missing details from contributors.