Issue Station
Sign In
Tools hereToolbox

gemini-cli - ✅(Solved) Fix Implement automated and standardized GitHub issue triage workflow [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#24960•Fetched 2026-04-09 08:16:49
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
cocosheng-gcocosheng-g
Participants
cocosheng-gcocosheng-gpsinha40898psinha40898
Assignees
cocosheng-gcocosheng-g
Timeline (top)
labeled ×2assigned ×1commented ×1cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #24958: feat(skills): add github-issue-triage skill for automated backlog maintenance

Description (problem / solution / changelog)

Introduces a new workspace-specific skill github-issue-triage to automate and standardize the GitHub issue maintenance workflow for the Gemini CLI repository. This skill helps maintainers and oncallers quickly process the backlog by automating repetitive analysis and enforcing project triage policies.

Component Breakdown

The skill is located in .gemini/skills/github-issue-triage and consists of:

  • analyze_issue.cjs: A deterministic Node.js script that fetches issue metadata (labels, timeline, cross-references) and calculates staleness/inactivity (30/60 day thresholds) and response deadlines (14 days).
  • find_issues.cjs: A helper script to find the oldest updated issues needing triage.
  • triage_rules.md: A comprehensive procedural guide for the agent covering:
    • Step 0: Immediate bypass for maintainer-only tracking issues.
    • Step 1: Automated closure for resolved issues or those with merged PRs.
    • Step 1.2: Critical evaluation and restoration of community PRs incorrectly closed by bots (with apology and sync instructions).
    • Step 1.5: Automated closure for issues where more info was requested but no response received for 14 days.
    • Step 2: Inactivity pings for bug reports.
    • Step 3: Vagueness checks for incomplete reports.
    • Step 4: Checking if a feature request is already implemented natively.
    • Step 6: Categorization into Maintainer-only vs Help-wanted with required brief explanations.

Key Features & Design Decisions

  • Maintainer-only vs Help-wanted: Strictly defines Maintainer-only tasks as those touching core architecture, IPC, token/billing logic, or key global UI/UX.
  • Bot-Closed PR Handling: Implements a "restoration with apology" flow to improve the contributor experience for those whose work was swept by the 14-day inactivity bot.
  • Deadline Enforcement: Dynamically calculates and communicates exact dates for reporter responses.

How to Use

Inside the gemini-cli repository, simply ask the agent:

  • "Use github-issue-triage to triage issues" (for discovery mode)
  • "Triage issue #123" (for targeted mode)

Fixes #24960

Changed files

  • .gemini/skills/github-issue-triage/SKILL.md (added, +39/-0)
  • .gemini/skills/github-issue-triage/references/triage_rules.md (added, +125/-0)
  • .gemini/skills/github-issue-triage/scripts/analyze_issue.cjs (added, +161/-0)
  • .gemini/skills/github-issue-triage/scripts/find_issues.cjs (added, +34/-0)
RAW_BUFFERClick to expand / collapse

Problem

Maintaining a clean and actionable backlog for the Gemini CLI repository is a repetitive and time-consuming task for oncallers and maintainers. Manual triage often leads to inconsistent application of project policies regarding staleness, inactivity pings, and task categorization (Maintainer-only vs Help-wanted).

There is also a recurring point of friction where valid community PRs are automatically closed by our 14-day inactivity bot without a clear restoration path, which negatively impacts the contributor experience.

Proposed Solution

Introduce a dedicated Gemini CLI skill (github-issue-triage) that provides a standardized, agentic workflow for backlog maintenance. This skill will:

  • Automate Analysis: Use deterministic scripts to check dates, cross-references, and PR status.
  • Enforce Project Policies: Standardize the process for closing resolved issues, handling vague reports, and pinging inactive reporters.
  • Improve Contributor UX: Detect and restore community PRs incorrectly closed by bots, including an apology and instructions for syncing.
  • Standardize Categorization: Enforce strict definitions for Maintainer-only vs Help-wanted tasks based on architectural impact.

This is implemented in PR #24958.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#orchestration issue#cache issue#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING