OpenParable
Skip to content
← Back to skills

GH Issue Scheduler

Productivity
gh-issue-scheduler

GH Issue Scheduler is an Agent Skill for productivity published in the Fu-Jie/openwebui-extensions repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Finds all open GitHub issues that haven't been replied to by the owner, summarizes them, and generates a solution plan. Use when the user wants to audit pending tasks or plan maintenance work.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Fu-Jie/openwebui-extensions/blob/HEAD/.agent/skills/gh-issue-scheduler/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gh-issue-scheduler, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Gh Issue Scheduler

Overview

The gh-issue-scheduler skill helps maintainers track community feedback by identifying unaddressed issues and drafting actionable technical plans to resolve them.

Workflow

  1. Identify Unanswered Issues: Run the bundled script to fetch issues without owner replies.
    • Command: bash scripts/find_unanswered.sh
  2. Analyze and Summarize: For each identified issue, summarize the core problem and the user's intent.
  3. Generate Solution Plans: Draft a technical "Action Plan" for each issue, including:
    • Root Cause Analysis (if possible)
    • Proposed Fix/Implementation
    • Verification Strategy
  4. Present to User: Display a structured report of all pending issues and their respective plans.

Tool Integration

Find Unanswered Issues

bash scripts/find_unanswered.sh

Report Format

When presenting the summary, use the following Markdown structure:

📋 Unanswered Issues Audit

Issue #[Number]: [Title]

  • Author: @username
  • Summary: Concise description of the problem.
  • Action Plan:
    1. Step 1 (e.g., Investigate file X)
    2. Step 2 (e.g., Apply fix Y)
    3. Verification (e.g., Run test Z)