feat(skills): add github-issue-triage skill for automated backlog maintenance#24958
feat(skills): add github-issue-triage skill for automated backlog maintenance#24958cocosheng-g wants to merge 21 commits intomainfrom
Conversation
… or help-wanted labels
…ntainer-only criteria
…eopening flawed PRs
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Hi @cocosheng-g, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this. We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines. Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed. Thank you for your understanding and for being a part of our community! |
|
Size Change: -4 B (0%) Total Size: 34 MB
ℹ️ View Unchanged
|
…ssues in closed PR re-evaluation
Introduces a new workspace-specific skill
github-issue-triageto 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-triageand 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:grep_searchto verify if a requested feature already exists natively before proceeding with triage.Key Features & Design Decisions
maintainer onlylabel, instead usinghelp wantedas the sole whitelist label for community contributions. Explicitly defines counter-examples (e.g., core architecture, IPC, telemetry) that should not receive the label.How to Use
Inside the
gemini-clirepository, simply ask the agent:Fixes #24960