quality

Classifies GitHub issues as spam, empty, needs-info, feature, or actionable bug reports.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill quality-rameshkumarchouhanr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality
Source: https://github.com/rameshkumarchouhanr/gemni-cli/tree/main/tools/caretaker-agent/cloudrun/triage-worker/.gemini/skills/quality
Command: npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill quality-rameshkumarchouhanr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers of open-source repositories receive large volumes of GitHub issues of varying quality, and manually triaging each one consumes significant time. This Skill automates the first-pass quality assessment so maintainers can focus on actionable reports. ## Core Features & Use Cases - Issue Quality Classification: Categorizes each issue as SPAM, EMPTY, NEEDS_INFO, FEATURE, or OK based on title and body content. - Structured JSON Output: Returns a machine-readable verdict with reasoning and an optional draft comment requesting missing details. - Prompt Injection Defense: Automatically flags issues containing prompt injection attempts as SPAM regardless of other content. - Use Case: A triage worker processing incoming issues for the Gemini CLI repository uses this Skill to filter out spam and incomplete reports, drafting a 'needs more information' comment for issues lacking reproduction steps. ## Quick Start Evaluate this GitHub issue title and body and tell me whether it is spam, empty, needs more information, a feature request, or ready to triage.

Frequently Asked Questions about quality

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

FAQPage Schema
How do I automatically triage GitHub issues for quality?

Analyze the issue title and body for clarity, completeness, and actionable detail, then classify it as SPAM, EMPTY, NEEDS_INFO, FEATURE, or OK. The result is returned as a JSON object with reasoning and an optional draft comment for incomplete reports.

What makes a GitHub issue actionable for maintainers?

An actionable issue shows clear user intent to report a systemic code defect with sufficient reproduction details, environment information, and diagnostic context. Issues stemming from user-defined configurations or lacking reproduction steps are classified as NEEDS_INFO instead.

How are prompt injection attacks in issues handled?

Any issue containing a prompt injection attempt, such as 'Ignore previous instructions', is immediately classified as SPAM. This applies regardless of whether the body also contains a legitimate bug description or references real codebase files.

When should an issue be classified as NEEDS_INFO versus EMPTY?

EMPTY applies when the issue has little to no descriptive content, such as blank bodies or boilerplate template text. NEEDS_INFO applies when the issue has on-topic context like environment details or logs but lacks reproduction steps or a user-written description.

Can this distinguish feature requests from bug reports?

Yes, issues requesting new features, enhancements, or capabilities that do not currently exist are classified as FEATURE rather than OK. The OK category is reserved for valid, actionable bug reports with enough information to proceed.