hos-gh-issue

Write and file GitHub issues, sub-issues, and hub issues using the gh CLI.

32|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/openreachtech/hora-skills-ort-support --skill hos-gh-issue-openreachtech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hos-gh-issue
Source: https://github.com/openreachtech/hora-skills-ort-support/tree/main/kit/skills/hos-gh-issue
Command: npx skills add https://github.com/openreachtech/hora-skills-ort-support --skill hos-gh-issue-openreachtech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing GitHub issues that clearly state the current situation and direction—without leaking implementation details that belong in pull requests—is hard to do consistently. This Skill enforces a structured issue format (As-is, To-be, Note, Checklist, Sub-issues), typed titles with emoji, and safe filing through the gh CLI only after explicit approval. ## Core Features & Use Cases - Structured issue bodies: Generates the five H1 sections in order, writing only sections that carry content, with rules for when H2 subsections, tables, and one-target-per-line checkboxes apply. - Hub and sub-issue support: Writes hub issues that gather children with no checklist of their own, files sub-issues via gh issue create --parent, and fills in bodies of sub-issues GitHub created empty. - Approval-gated filing: Shows title and body in fenced blocks first, files with gh issue create --body-file only after you say yes, and hands over the command when gh is unavailable. - Use Case: Ask for an issue to track raising a dependency across several packages, and receive a typed title, an observed As-is section, a per-package checklist, and a ready-to-run gh command. ## Quick Start Write a GitHub issue for adding a quick start guide to the docs directory and file it once I approve the text.

Frequently Asked Questions about hos-gh-issue

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

FAQPage Schema
How do I write a well-structured GitHub issue?

Structure the body with five H1 sections in order: As-is (observed current state), To-be (direction, not implementation), Note (constraints), Checklist (one target per line), and Sub-issues. Write only sections that carry content, and open the title with a type emoji.

How do I create a GitHub sub-issue with the gh CLI?

Run gh issue create with --parent <number> to file a child issue directly under a parent. Alternatively, list full titles under a Sub-issues section and convert them with GitHub's native sub-issue feature, which removes the line from the body.

What is the difference between a GitHub issue and a pull request body?

An issue states where things stand and which direction to take; the pull request describes how the work was carried out and links back with Close #<issue>. This Skill writes issues only—pull request bodies belong to a separate skill.

Can I file a GitHub issue when gh CLI is not authenticated?

No. When gh is missing or gh auth status fails, the Skill says which occurred and stops at the text, handing over the gh issue create command so whoever logs in later can file it without reassembling anything.

Why should issue bodies be passed with --body-file instead of --body?

Issue bodies contain backticks, hash symbols, and newlines that the shell interprets before gh sees them. Passing the body through --body-file lets gh read the file directly, so nothing inside needs escaping; use - to read from standard input.

When should a GitHub issue be a hub issue?

Use a hub when asked to gather several pieces of work, such as a release or a change spanning two repositories. A hub carries As-is, To-be, Note, and Sub-issues but no Checklist—any work of its own belongs in a child issue.