gh-issue-scheduler

Identify open GitHub issues without owner responses and generate maintenance plans.

286|24|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill gh-issue-scheduler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issue-scheduler
Source: https://github.com/Fu-Jie/openwebui-extensions/tree/main/.gemini/skills/gh-issue-scheduler
Command: npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill gh-issue-scheduler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

The skill identifies open GitHub issues that have not received replies from the repository owner and generates structured, actionable maintenance plans to address them.

Core Features & Use Cases

  • Identify unanswered issues across repositories to surface feedback and maintenance tasks.
  • Summarize core problems and user intents for each issue, and draft a concrete action plan with root-cause considerations and verification steps.
  • Produce a clear, structured report suitable for triage meetings or dev team planning.

Quick Start

Run the bundled script to fetch open issues and draft maintenance plans.

Frequently Asked Questions about gh-issue-scheduler

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

FAQPage Schema
How do I identify unanswered GitHub issues across my repositories?

To identify unanswered GitHub issues, this Skill audits open tickets lacking owner responses and generates structured maintenance plans. It fetches pending feedback across repositories to surface issues requiring immediate triage and resolution paths.

Can I automate issue triage and root-cause analysis for pending GitHub feedback?

Yes, you can automate issue triage by running the bundled script to fetch open issues. The Skill summarizes user intents and drafts root-cause analyses with verification steps, providing a deterministic workflow for automated maintenance planning.

Do I need gh and jq installed to audit open GitHub issues and draft maintenance plans?

Yes, you need the gh and jq dependencies installed to audit open GitHub issues. These command-line tools enable the bundled script to fetch repository data and parse JSON outputs for generating actionable maintenance plans.

What is the best way to generate actionable plans for unowned GitHub issues?

The best way to generate actionable plans for unowned issues is using a deterministic workflow that summarizes core problems and drafts solution paths. This Skill produces clear, structured reports suitable for triage meetings and dev team planning.

Does this issue triage Skill work for maintenance workflows across multiple repositories?

Yes, this issue triage Skill applies to maintenance workflows across multiple repositories. It audits pending feedback universally, identifying open issues without owner responses and producing structured solution paths for each repository.

What limitations should I expect when automating GitHub issue triage with scripts?

When automating GitHub issue triage, limitations include relying strictly on gh and jq for data fetching and parsing. The Skill focuses on drafting structured action plans and root-cause analyses, meaning complex collaborative interactions still require manual developer oversight.