waiting-user-handler

Triage GitHub Issues labeled status:waiting-user and resolve or escalate them by category.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/kai-kou/gem-hunter --skill waiting-user-handler-kai-kou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: waiting-user-handler
Source: https://github.com/kai-kou/gem-hunter/tree/main/.claude/skills/waiting-user-handler
Command: npx skills add https://github.com/kai-kou/gem-hunter --skill waiting-user-handler-kai-kou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Issues labeled status:waiting-user pile up waiting for user input, but many can actually be resolved autonomously. This Skill periodically triages those Issues, auto-resolves the ones that do not truly need user judgment, and presents only genuinely user-dependent decisions with pre-researched recommendations. ## Core Features & Use Cases - A/B/C/D Classification: Sorts each waiting-user Issue into categories (autonomous reply, autonomous report handling, external factors, tool-fixable, or truly requiring user decision) based on the project's user-confirmation-minimization rules. - Autonomous Resolution: Automatically answers technical comment questions and processes periodic reports via specialist agent teams, closing Issues without user involvement when quality gates pass. - Batched User Prompts: For A-category Issues only, prepares researched recommendations and presents up to 4 questions per batch via AskUserQuestion, with the recommended option first. - Use Case: A scheduled hourly scan finds 5 waiting-user Issues; 3 are auto-resolved (duplicate close, comment reply, report triage) and the remaining 2 are presented to the user with recommended actions. ## Quick Start Ask the AI to handle the waiting-user Issues by saying: please triage and handle all Issues labeled status:waiting-user in this repository.

Frequently Asked Questions about waiting-user-handler

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

FAQPage Schema
How do I triage GitHub Issues waiting on user responses?▼

List open Issues with the status:waiting-user label, classify each into A/B/C/D categories, auto-resolve C and D categories, and present only A-category decisions to the user with pre-researched recommendations.

How to auto-reply to technical questions in GitHub Issue comments?▼

Use the C-1 autonomous reply flow: research the question, draft a response, have a reviewer role validate it, and auto-post only when all quality gates pass. Failed gates fall back to presenting the draft to the user.

Can this run in cloud environments without the gh CLI?▼

Yes. In cloud environments where gh is unavailable or returns 403, all GitHub operations use the mcp__github__* MCP tools instead, following the fallback patterns documented in the project rules.

When should waiting-user Issues not be auto-closed?▼

Auto-close only applies to C-category Issues meeting explicit conditions. Anything ambiguous is treated as A-category and escalated to the user, preventing over-closing and missed decisions.

What is the difference between waiting-user-handler and pr-review-watcher?▼

waiting-user-handler triages Issue labels and user-confirmation decisions, while pr-review-watcher handles PR review monitoring and merging. Interactive step-by-step user guidance is delegated to the interactive-guide skill.