kmp-github-issue-governance

Govern GitHub issue hierarchies, sub-issues, and shell-safe markdown transport via gh CLI.

2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/ronjunevaldoz/kmp-agent-skills --skill kmp-github-issue-governance-ronjunevaldoz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kmp-github-issue-governance
Source: https://github.com/ronjunevaldoz/kmp-agent-skills/tree/main/skills/kmp-github-issue-governance
Command: npx skills add https://github.com/ronjunevaldoz/kmp-agent-skills --skill kmp-github-issue-governance-ronjunevaldoz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Teams filing GitHub issues for KMP projects often create ticket clutter, spam comment threads with micro-status updates, and corrupt markdown payloads when passing multi-line text through the gh CLI. This Skill enforces a disciplined issue hierarchy (Epics, sub-issues, standalone bugs/features), comment throttling rules, and safe markdown transport so issue boards stay readable and payloads render correctly. ## Core Features & Use Cases - Issue Hierarchy Decision Engine: Classifies work as Epic, Sub-Issue, Standalone Feature, or Bug using a decision tree and template matrix, then attaches sub-issues via GitHub's native GraphQL Sub-Issues API. - Anti-Spam Comment Governance: Enforces in-place progress updates (checkbox edits, PATCH on pinned comments) and restricts new comments to milestone transitions like BLOCKED or READY FOR REVIEW. - Shell-Safe Markdown Transport: Mandates --body-file and quoted heredoc patterns to prevent backtick subshell stripping and literal \n\n corruption in issue bodies. - Automation Scripts: Includes gh_sub_issue.py for add/create/list/remove sub-issue operations and validate_issue_payload.py for pre-flight linting of markdown payloads. - Use Case: When decomposing a multi-PR KMP feature into an Epic with five child tasks, use this Skill to create the Epic, attach sub-issues with gh_sub_issue.py, validate each payload, and post status updates without flooding the issue with comments. ## Quick Start Ask the agent to decompose your multi-PR feature into a GitHub Epic with attached sub-issues and generate the shell-safe gh CLI commands to file them.

Frequently Asked Questions about kmp-github-issue-governance

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

FAQPage Schema
How do I create GitHub sub-issues with the gh CLI?▼

Use the bundled gh_sub_issue.py script, which wraps GitHub's native Sub-Issues GraphQL API. Run python3 scripts/gh_sub_issue.py add <parent> <child> to attach an existing issue, or create <parent> --title ... --body-file payload.md to file and attach a new sub-issue in one step.

When should I create an Epic vs a standalone feature issue?▼

Create an Epic when work spans 3+ PRs, crosses multiple layers, or requires verification across platforms like Desktop, Wasm, and Vulkan. Use a standalone feature_request issue for a single atomic PR with no children, and attach task sub-issues to an active Epic.

Why does my GitHub issue body show literal \n\n or missing backtick text?▼

Passing markdown through -b or --body flags causes the shell to execute backticks as subshell commands and encode newlines as literal characters. Always write the payload to a temp file and use --body-file, or pipe a quoted heredoc (cat <<'EOF') to --body-file -.

How do I avoid spamming GitHub issues with status comments?▼

Limit yourself to one comment per session per issue and update progress in place by checking off task checkboxes in the description or PATCHing a pinned comment via the REST API. Reserve new comments for milestone transitions like BLOCKED, READY FOR REVIEW, or RESOLVED.

How do I validate a markdown payload before posting to GitHub?▼

Run python3 scripts/validate_issue_payload.py payload.md --template task to lint the file. It flags literal \n\n escape sequences, unclosed code fences and backticks, and missing required section headings for epic, task, bug, or feature templates.

Does gh_sub_issue.py work outside a git repository?▼

It auto-detects the repository via gh repo view, but outside a git context you must pass --repo owner/repo explicitly. The gh CLI must be installed and authenticated with gh auth status before running any sub-issue commands.