gh-resolve-issue

Name: gh-resolve-issue
Availability: InStock
Author: MithrilMan

Triage and resolve GitHub issues using the gh CLI.

Updated Mar 12, 2026

Search Tags:#automation #workflow #github #cli #issues #gh #triage

Ready to run

npx skills add https://github.com/MithrilMan/neomithril-ui --skill gh-resolve-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh-resolve-issue
Source: https://github.com/MithrilMan/neomithril-ui/tree/main/.codex/skills/gh-resolve-issue
Command: npx skills add https://github.com/MithrilMan/neomithril-ui --skill gh-resolve-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines triage and resolution of GitHub issues directly from the current repository, reducing manual context switching and ensuring consistent workflows.

Core Features & Use Cases

Triage issues by ID or by selecting the oldest actionable open issue without the automation:nop label.
Apply structured workflows to classify issues into fix-needed, close-no-change, or nop-needed, with guardrails and documented commands.
Use gh CLI to view, edit, and close issues, and to apply appropriate labels and closing keywords.
Recommends clarity on automated handoff and maintains a terminal automation state for subsequent runs.

Quick Start

Invoke the gh-resolve-issue skill to triage an issue by number or URL, then resolve it to a terminal automation state (fixed, manually closed, or labeled automation:nop) for automatic filtering in future runs.

Frequently Asked Questions about gh-resolve-issue

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

FAQPage Schema

How do I automate GitHub issue triage and resolution using the gh CLI?▼

Automate GitHub issue triage by invoking the skill to classify issues, apply labels like automation:nop, and use gh CLI commands to view, edit, and close issues with structured commit messaging.

Can I automatically resolve the oldest open issue in a GitHub repository?▼

Yes, you can automatically resolve the oldest open issue by triggering the skill without an explicit issue number; it auto-picks the oldest open issue lacking the automation:nop label for end-to-end handling.

What are the final states for an issue processed by this triage workflow?▼

The triage workflow processes issues and outputs a terminal automation state such as fixed, manually closed, or labeled automation:nop, ensuring consistent filtering for subsequent automated runs.

How do I exclude specific GitHub issues from automated triage?▼

Exclude specific GitHub issues from automated triage by applying the automation:nop label to them, which prevents the skill from selecting those issues during its auto-pick process.

Does this issue resolution workflow require any external dependencies?▼

No, this issue resolution workflow requires no external dependencies; it operates directly within the current repository using the existing gh CLI environment to manage and close issues.

What is the best way to classify GitHub issues into fix-needed or close-no-change categories?▼

The best way to classify GitHub issues is using the skill's structured triage rules, which evaluate issues and categorize them into fix-needed, close-no-change, or nop-needed states with applied guardrails.