Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aglebionek avatar

Create Gh Issue

  • 1 installs
  • Updated July 31, 2026
  • aglebionek/agentic-coding-repo

create-gh-issue is a Claude Code skill that opens GitHub issues with the gh CLI using the repository's own issue templates.

About

create-gh-issue opens GitHub issues from the current conversation using the gh CLI. It reads the repository's .github/ISSUE_TEMPLATE/*.yml templates, picks the closest one (bug, feature, refactor, infra, config, or agent-task), extracts each required field, and runs gh issue create with a body that mirrors the template sections. A developer uses it to turn discussed work into a properly labelled issue without opening the browser.

  • Creates GitHub issues non-interactively with gh issue create
  • Selects the closest .github/ISSUE_TEMPLATE/*.yml template and fills required fields
  • Returns the created issue number and URL

Create Gh Issue by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #524 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
  • Data as of Aug 1, 2026 (Skillselion catalog sync)
At a glance

create-gh-issue capabilities & compatibility

Capabilities
issue creation · issue templating
Works with
github
Use cases
project management
Pricing
Free
From the docs

What create-gh-issue says it does

Create the issue yourself with `gh issue create`. Do not stop at a suggested draft unless the user explicitly asks for draft-only output.
SKILL.md
Create the issue non-interactively with `gh issue create --title ... --body-file ... --label ...`.
SKILL.md
Prefer `gh` over browser links or manual issue URLs.
SKILL.md
npx skills add https://github.com/aglebionek/agentic-coding-repo --skill create-gh-issue

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
Last updatedJuly 31, 2026
Repositoryaglebionek/agentic-coding-repo

What it does

Convert discussed work into a properly templated GitHub issue via the gh CLI.

Who is it for?

opening bug, feature, refactor, infra, or agent-task issues that match the repo's issue templates

Skip if: issue triage, browser-based issue creation, or repos with no issue templates

When should I use this skill?

the user wants to open, draft, or convert work into a GitHub issue

What you get

A GitHub issue is created via gh with sections matching the template and its number and URL returned.

  • a created GitHub issue
  • issue number and URL

By the numbers

  • 6 issue-template types (agent-task, bug, config, feature, infra, refactor)
  • 6-step workflow

Files

SKILL.mdMarkdownGitHub ↗

Create GitHub Issue

Create the issue yourself with gh issue create. Do not stop at a suggested draft unless the user explicitly asks for draft-only output.

Workflow

1. Read .github/ISSUE_TEMPLATE/*.yml and pick the closest template. 2. Extract every required field from that template in order. 3. If the conversation is missing required information, ask focused follow-up questions one at a time. 4. Build a markdown body whose section headings match the template labels exactly and appear in the same order. 5. Create the issue non-interactively with gh issue create --title ... --body-file ... --label .... 6. Return the created issue number and URL.

Template selection

  • .github/ISSUE_TEMPLATE/agent-task.md: Well-bounded task intended for AI-assisted execution.
  • .github/ISSUE_TEMPLATE/bug.md: Report a defect with clear scope and reproducible behavior.
  • .github/ISSUE_TEMPLATE/config.md: Define or update a configuration setting, with clear parameters and expected impact.
  • .github/ISSUE_TEMPLATE/feature.md: Request or define a scoped feature.
  • .github/ISSUE_TEMPLATE/infra.md: Infrastructure, CI, release, or automation change.
  • .github/ISSUE_TEMPLATE/refactor.md: Structural/code quality change without intended behavior changes.

Rules

  • Prefer gh over browser links or manual issue URLs.
  • Match the template's title prefix and default label.
  • Keep the body concise, but never omit required sections.
  • If a section is intentionally empty, write None. instead of leaving it blank.
  • If the user gives a plan or conversation and wants an issue, compress it into the template instead of pasting raw notes.
  • If the repository is ambiguous, resolve it before creating the issue.
  • If gh authentication or repo access is missing, surface that blocker plainly.

Body shape

Render each required field like this:

## Goal
...

## Scope
...

Use bullets when they scan better than prose. For dropdowns like risk, write the selected value as plain text in its section.

Command pattern

Use this shape, filling in the chosen template details:

gh issue create \
  --repo OWNER/REPO \
  --title "[repo] Type: concise summary" \
  --label "template-label" \
  --body-file /tmp/issue-body.md

Related skills

FAQ

Does it create the issue or just draft it?

It creates the issue itself with gh issue create; it stops at a draft only if you explicitly ask for draft-only output.

How does it choose which issue template to use?

It reads .github/ISSUE_TEMPLATE/*.yml and picks the closest template, matching your request to bug, feature, refactor, infra, config, or agent-task.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.