New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

GitHub Issue Creator

by tailcallhq in tailcallhq/forgecode

Creates well-structured GitHub issues with gh CLI by discovering and following the repository's own issue templates and labels.

Apache-2.0Auto-check: warningsDevelopment

Install GitHub Issue Creator

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add tailcallhq/forgecode --skill create-github-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tailcallhq/forgecode create-github-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tailcallhq/forgecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.forge/skills/create-github-issue .claude/skills/create-github-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-github-issue
GitHub stars
7.6k
Token cost
~1k tokens
SKILL.md length
458 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

Creates well-structured GitHub issues with gh CLI by discovering and following the repository's own issue templates and labels.

  • Works in 7 steps: Discover and Select Template → Gather Context → Generate Markdown Body → …
  • Filing a bug report that matches the repo's own template
  • SKILL.md covers Workflow, Guidelines and Notes
  • Calls gh and git

What it does

Templates under .github/ISSUE_TEMPLATE/ are listed and read first so the issue body matches the YAML fields, title prefix, and default labels the maintainers already defined, rather than assuming a generic bug-report shape. Labels come only from .github/labels.json, each required YAML field gets populated with real content, and the title stays under 70 characters in an imperative mood starting with a verb such as Fix, Add, or Update.

When your agent uses it

  • Filing a bug report that matches the repo's own template
  • Opening a feature request with the correct labels applied
  • Drafting an issue body from the project's required template fields

Example prompts

  • “File a bug report for the crash we just reproduced in staging.”
  • “Open a feature request for CSV export using the repo's template.”
  • “Draft an issue body for this flaky test, following the bug template.”

Requirements

  • GitHub CLI (`gh`)

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Discover and Select Template
  2. Gather Context
  3. Generate Markdown Body
  4. Choose Labels
  5. Create Title
  6. Execute Issue Creation
  7. Finalize

What it can do on your machine

Read from SKILL.md and the folder at commit e11b93e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Issue Creator loads about 1k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 458 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: warnings

The automated check found patterns that need a careful read before installing.

  • WarningTells the agent its actions are pre-authorized / not to stop for confirmationSKILL.md:99
    - **Automation**: Do not ask for confirmation before creating the issue if the user's intent is clear.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tailcallhq/forgecode at commit e11b93e, republished under its Apache-2.0 licence (© tailcallhq). 458 words, ~1,030 tokens.

Download SKILL.mdSave it as .claude/skills/create-github-issue/SKILL.md (or your agent's skills folder).
name
create-github-issue
description
Create GitHub issues using GitHub CLI with support for templates, labels, assignees, milestones, and draft issues. Use when the user asks to create a GitHub issue, file a bug report, submit a feature request, or open an issue in a GitHub repository.

Create GitHub Issue

Create comprehensive GitHub issues using gh issue create by dynamically discovering and adhering to the repository's official issue templates.

Workflow

1. Discover and Select Template

CRITICAL: You must use the repository's official templates. Do not assume the structure.

  1. List available templates:
    bash
    ls .github/ISSUE_TEMPLATE/
  2. Select the most appropriate template based on the issue type (e.g., bug_report.yml, feature_request.yml).
  3. Read the selected template to understand its required fields, structure, and any title prefixes or default labels.
    bash
    cat .github/ISSUE_TEMPLATE/<selected_template>.yml
2. Gather Context

Gather relevant information to fulfill the template requirements:

bash
# Check current git status for context
git status

# View recent commits if related to codebase changes
git log --oneline -10

# Check if related issues exist
gh issue list --search "keyword" --limit 10
3. Generate Markdown Body

MANDATORY: Structure the issue body exactly as defined in the selected YAML template without exception.

  1. Map YAML fields to Markdown: Convert each field in the template (typically found under body:) into a Markdown section.
  2. Use Headers: Use the label or id from the YAML field as an H2 header (e.g., ## Bug Description).
  3. Respect Validation: Ensure all fields marked as required: true in the YAML are populated with meaningful content.
  4. Format Correctly: Use code blocks (e.g., ```shell, ```yaml) for logs and configurations as suggested by the template's render attribute.
4. Choose Labels

Select labels by inspecting .github/labels.json.

  • Primary Label: Always include a type: label that matches the issue type.
  • Additional Labels: Add relevant state:, work:, or priority: labels if they exist in the configuration.
  • Constraint: Only use labels defined in .github/labels.json.
5. Create Title

Follow the template's title field if it provides a prefix (e.g., "[Bug]: ").

  • Be concise: Keep under 70 characters.
  • Use imperative mood: "Fix authentication timeout" instead of "Authentication is timing out".
  • Start with action verb: Fix, Add, Improve, Update, Refactor.
Show full SKILL.md (184 more words)Show less
6. Execute Issue Creation

Step 1: Write body to temp file Use the write tool to create .forge/FORGE_ISSUE_BODY.md with the structured Markdown content.

Step 2: Create issue

bash
gh issue create \
  --title "[Prefix]: Descriptive Title" \
  --body-file .forge/FORGE_ISSUE_BODY.md \
  --label "type: <type>, work: <complexity>"

Optional flags:

  • --assignee "username"
  • --milestone "name"
  • --draft (For proposals or research)
7. Finalize

Provide the user with the generated issue URL and a brief summary of the created issue.

Guidelines

  • No Exceptions: You must follow the discovered template's structure exactly. If a template asks for "Steps to Reproduce", you must provide them.
  • Dynamic Discovery: Always read the files in .github/ISSUE_TEMPLATE/ and .github/labels.json first. Never rely on hardcoded knowledge of templates or labels as they change frequently.
  • Cleanliness: Ensure no placeholder text (like "Describe the bug...") remains in the final body.
  • Contextual Awareness: If the user provides logs or code snippets, ensure they are placed in the correct sections of the template.

Notes

  • Single Source of Truth: The files in .github/ are the authoritative reference for issue structure and categorization.
  • Tooling: Use gh CLI directly. It is pre-authenticated and ready for use.
  • Automation: Do not ask for confirmation before creating the issue if the user's intent is clear.

© tailcallhq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .forge/skills/create-github-issue of tailcallhq/forgecode.

Open the folder on GitHubat commit e11b93e

Compare with similar skills

GitHub Issue Creator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Issue Creator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Issue Creator this skilltailcallhq/forgecode7.6k—~1kAutomated safety check: WarnApache-2.0
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Windows App SDK Issue Triage Reportmicrosoft/WindowsAppSDK4.7k—~3.4kAutomated safety check: PassApache-2.0
Exposed Bug Fix WorkflowJetBrains/Exposed9.3k—~3.8kAutomated safety check: PassApache-2.0
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK4.7k—~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Windows App SDK Issue Triage Report

    microsoft/WindowsAppSDK

    Official

    Generates GitHub Feature Area Status reports for the Windows App SDK repository, scoring issues so teams can see what needs attention in each area.

    4.7k GitHub stars~3.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Exposed Bug Fix Workflow

    JetBrains/Exposed

    Official

    Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.

    9.3k GitHub stars~3.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • WinAppSDK Triage Meeting Prep

    microsoft/WindowsAppSDK

    Official

    Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.

    4.7k GitHub stars~2.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • A2ui Issue Triage

    a2ui-project/a2ui

    Automates the triage of GitHub issues in the A2UI repository.

    17k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

More from tailcallhq/forgecode

All 14 skills in this repo

  • Git Merge Conflict Resolver

    tailcallhq/forgecode

    Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.

    7.6k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed

  • Forge CLI Debug Workflow

    tailcallhq/forgecode

    Gives a systematic process for debugging the forge CLI: build in debug mode, check the latest help output, test with the non-interactive -p flag, and clone conversations before reproducing bugs.

    7.6k GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

  • FIXME Resolver

    tailcallhq/forgecode

    Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.

    7.6k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Reasoning Serialization Tests

    tailcallhq/forgecode

    Checks that ReasoningConfig fields are serialized into the right provider-specific JSON for OpenRouter, Anthropic, GitHub Copilot and Codex requests.

    7.6k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Implementation Plan Creator

    tailcallhq/forgecode

    Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.

    7.6k GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed

  • Release Notes Writer

    tailcallhq/forgecode

    Pulls a GitHub release and every linked pull request, then writes polished, factual release notes from the combined set of changes.

    7.6k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about GitHub Issue Creator

What does GitHub Issue Creator do?

Creates well-structured GitHub issues with gh CLI by discovering and following the repository's own issue templates and labels. github/ISSUE_TEMPLATE/ are listed and read first so the issue body matches the YAML fields, title prefix, and default labels the maintainers already defined, rather than assuming a generic bug-report shape.json, each required YAML field gets populated with real content, and the title stays under 70 characters in an imperative mood starting with a verb such as Fix, Add, or Update.

When should I use GitHub Issue Creator?

GitHub Issue Creator fits situations like: filing a bug report that matches the repo's own template; opening a feature request with the correct labels applied; drafting an issue body from the project's required template fields.

How do I install GitHub Issue Creator in Claude Code?

Run `npx skills add tailcallhq/forgecode --skill create-github-issue -a claude-code`. Or copy the skill folder (.forge/skills/create-github-issue in tailcallhq/forgecode) into .claude/skills/create-github-issue in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Issue Creator in Codex?

Run `npx skills add tailcallhq/forgecode --skill create-github-issue -a codex`. Or copy the skill folder (.forge/skills/create-github-issue in tailcallhq/forgecode) into .agents/skills/create-github-issue in your project. Codex loads it when a task matches its description.

Can I use GitHub Issue Creator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tailcallhq/forgecode --skill create-github-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-github-issue, .gemini/skills/create-github-issue, .github/skills/create-github-issue and .opencode/skills/create-github-issue in your project.

What does GitHub Issue Creator need to run?

Going by SKILL.md and its folder, GitHub Issue Creator needs the command-line tools its instructions call (gh and git). Our summary lists: GitHub CLI (`gh`).

Does GitHub Issue Creator access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is GitHub Issue Creator safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way.

What licence does GitHub Issue Creator use?

GitHub Issue Creator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Issue Creator use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub Issue Creator?

Skills that share tags, products or a category with GitHub Issue Creator: Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars), Windows App SDK Issue Triage Report (microsoft/WindowsAppSDK, 4.7k stars), Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Issue Creator?

tailcallhq (a GitHub organization) maintains it in tailcallhq/forgecode, which has 7,641 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 8, 2026.

Source: tailcallhq/forgecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.