github-issue

Automate GitHub issue lifecycle management with structured frontmatter and conventional commit titles.

15|2|Updated Dec 16, 2025

Search Tags:#automation #github #graphql #issues #sub-issues #conventional-commit

Ready to run

npx skills add https://github.com/enitrat/skill-issue --skill github-issue-enitrat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-issue
Source: https://github.com/enitrat/skill-issue/tree/main/plugins/base-config/skills/github-issue
Command: npx skills add https://github.com/enitrat/skill-issue --skill github-issue-enitrat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ghapi>=1.0.5, typer>=0.9.0, rich>=13.0.0, pyyaml>=6.0, and includes scripts (resource) components.

What problem does it solve?

GitHub issue lifecycle management is error-prone and repetitive. This skill automates the end-to-end workflow from creating to closing issues, with structured frontmatter support to enable round-trip editing and cross-repo references.

Core Features & Use Cases

Create, view, edit, label, assign, link sub-issues, and close issues using conventional commit titles for consistency.
Dump issue trees to Markdown with YAML frontmatter for offline editing or migration, then push changes back to GitHub.
Manage cross-repo references, sub-issues, and linking relationships via GraphQL or gh CLI, with optional project and milestone associations.

Quick Start

Create a new GitHub issue in a repository by providing a conventional-commit style title and optional body content.

Frequently Asked Questions about github-issue

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

FAQPage Schema

How do I automate GitHub issue lifecycle management across repositories?▼

Automating GitHub issue lifecycle management across repositories is done by pushing structured issue changes with YAML frontmatter through the GitHub API. This workflow handles creation, editing, labeling, and closing issues while enforcing conventional commit title formats for consistency.

Can I link GitHub sub-issues automatically using GraphQL?▼

Linking GitHub sub-issues automatically using GraphQL is supported through the GitHub API. This feature manages cross-repo references and hierarchical linking relationships, optionally associating issues with specific projects and milestones during the lifecycle workflow.

How do I dump GitHub issue trees to Markdown for offline editing?▼

Dumping GitHub issue trees to Markdown with YAML frontmatter enables offline editing or repository migration. After making local changes to the structured files, you can parse the frontmatter and push the updates back to GitHub to sync the issue state.

Does this issue automation tool enforce conventional commit formats?▼

This issue automation tool enforces conventional commit title formats for creating, viewing, and editing issues. Applying structured title formats ensures consistency across cross-repo references and the entire issue lifecycle management process.

What's the best way to manage cross-repo references for GitHub issues?▼

The best way to manage cross-repo references for GitHub issues is using structured frontmatter and gh CLI or GraphQL integrations. This approach enables round-trip editing and synchronizes linking relationships across multiple repositories via the GitHub API.

Do I need specific dependencies to run GitHub issue automation scripts?▼

Running GitHub issue automation scripts requires specific dependencies including ghapi for API calls, typer for CLI interface, rich for terminal formatting, and pyyaml for parsing frontmatter. These packages enable the full lifecycle management and Markdown dump features.