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

Git Issue

by diodeme in diodeme/Gold-Band

Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification.

AGPL-3.0Auto-check passedTesting & QA

Install Git Issue

skills CLI
$ npx skills add diodeme/Gold-Band --skill git-issue -a claude-code

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

GitHub CLI
$ gh skill install diodeme/Gold-Band git-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/diodeme/Gold-Band.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/git-issue .claude/skills/git-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
git-issue
GitHub stars
143
Token cost
~1.4k tokens
SKILL.md length
720 words
Files
2
Skills in repo
11
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification.

  • Works in 4 steps: Prepare the exact final issue. → Show the user the repository, title,… → Ask the user to approve that exact… → …
  • The user asks to draft
  • SKILL.md covers Enforce the review gate, Prepare the issue, Write evidence faithfully and Publish and verify
  • Calls gh

What it does

Git Issue is an agent skill from diodeme/Gold-Band. Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification. Use when the user asks to draft, file, submit, publish, edit, or refine a GitHub issue, bug report, feature request, performance issue, or technical proposal. Always require the user to review and explicitly approve the exact final issue before any GitHub write.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Testing & QA, covering QA and bug reports and Git workflow. It works with GitHub and Git. The repository describes itself as: Desktop app for harness engineering, loop engineering, graph engineering—and whatever comes next in local AI-agent workflows. The licence is AGPL-3.0.

When your agent uses it

  • The user asks to draft
  • Refine a GitHub issue
  • Feature request
  • Performance issue

Example prompts

  • “/git-issue”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Prepare the exact final issue.
  2. Show the user the repository, title, complete body, labels, assignees, milestone, and any linked issue.
  3. Ask the user to approve that exact preview.
  4. Wait for an explicit approval in a later user response.

What it can do on your machine

Read from SKILL.md and the folder at commit 75622ac. 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

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

  • Network

    No URLs in SKILL.md. Its commands use gh, 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

Git Issue loads about 1.4k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 720 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 diodeme/Gold-Band at commit 75622ac, republished under its AGPL-3.0 licence (© diodeme). 720 words, ~1,367 tokens.

Download SKILL.mdSave it as .claude/skills/git-issue/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
git-issue
description
Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification. Use when the user asks to draft, file, submit, publish, edit, or refine a GitHub issue, bug report, feature request, performance issue, or technical proposal. Always require the user to review and explicitly approve the exact final issue before any GitHub write.

Git Issue

Create accurate GitHub issues through the official gh CLI. Treat repository files and GitHub state as authoritative; never hardcode an owner, repository, default branch, label, or template.

Enforce the review gate

Never perform a GitHub write before completing all of these steps:

  1. Prepare the exact final issue.
  2. Show the user the repository, title, complete body, labels, assignees, milestone, and any linked issue.
  3. Ask the user to approve that exact preview.
  4. Wait for an explicit approval in a later user response.

Treat the initial request to create or submit an issue only as authorization to prepare the preview. Do not treat it as approval of content the user has not seen. Do not bypass the gate when the user says "submit directly."

Bind approval to the displayed revision. If any title, body, repository, label, assignee, milestone, or link changes after approval, show the revised complete preview and obtain approval again.

Before approval, do not run gh issue create, gh issue edit, gh issue comment, or any equivalent API mutation. Read-only discovery is allowed.

Prepare the issue

  1. Read the applicable repository instructions, including AGENTS.md and routed rule files.
  2. Resolve the repository from the current Git remote, then confirm it with gh repo view.
  3. Verify gh authentication, repository access, and that Issues are enabled.
  4. Read .github/ISSUE_TEMPLATE/config.yml and every applicable template in .github/ISSUE_TEMPLATE/. Use these files as the content-schema source of truth.
  5. Search open and closed issues for the same symptom, goal, error, or affected component. Limit broad searches and refine them with distinctive terms.
  6. If a likely duplicate exists, show it to the user and ask whether to stop, add new evidence to it, or prepare a distinct issue. Do not mutate the existing issue without a separate reviewed preview.
  7. Classify the issue and select the closest repository template:
    • Bug report for observable incorrect behavior.
    • Feature request for new user-facing value.
    • Performance issue for observable latency, resource, throughput, or scale problems.
    • Technical proposal for architecture, data integrity, lifecycle, migration, or maintainability work without a primary user-facing feature.
  8. Fetch current labels and use only labels that already exist. Do not create labels, milestones, projects, or assignees unless the user explicitly requests them and reviews the final metadata.
Show full SKILL.md (343 more words)Show less

Write evidence faithfully

Use English for the published title, template headings, and prose by default. Translate a Chinese request into natural technical English while preserving code, commands, logs, identifiers, and quoted errors verbatim. Use Chinese only when the user explicitly requests a Chinese issue.

Follow the selected template instead of duplicating a private format in this skill. Apply these evidence rules:

  • Ask reporters only for information they can reliably provide. Maintainer-owned analysis must not block preparing an issue.
  • For bugs, require actual behavior, expected behavior, reproduction steps, and environment; treat evidence, impact, design intent, root cause, and acceptance criteria as optional investigation results.
  • For features, require the user problem, desired outcome, and a concrete use case; do not require the reporter to define scope, research implementations, or write acceptance criteria.
  • For performance reports, require the observed problem, workload, and environment; measurements and profiler evidence are helpful but optional.
  • For technical proposals, require the current problem, proposed direction, and alternatives considered. Add design context, migration, risks, performance impact, or acceptance considerations only when evidence already supports them.
  • When independently diagnosing a bug, mark root cause as Verified, Hypothesis, or Unknown; never present an inference as fact.
  • Include only claims supported by repository evidence or clearly attribute them to the reporter.
  • Remove secrets, credentials, personal data, private URLs, and unnecessary absolute local paths.
  • Use Closes #N only when the proposed outcome fully resolves the linked issue; otherwise use Refs #N.

Publish and verify

After approval:

  1. Reconfirm that the approved preview still matches the pending title, body, and metadata.
  2. Create or update the issue with gh using a body file or other quoting-safe input for multiline Markdown.
  3. Read the result back with gh issue view and verify the repository, number, title, body, labels, state, and URL.
  4. Report the URL and any metadata GitHub rejected or normalized.
  5. Do not perform follow-up edits or comments without another complete preview and explicit approval.

If authentication, permissions, repository identity, template selection, duplicate handling, or requested metadata remains ambiguous, stop before publishing and ask the user.

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

Files

SKILL.md and 1 other file in .agents/skills/git-issue of diodeme/Gold-Band.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 75622ac

Compare with similar skills

Git Issue 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.

Git Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Issue this skilldiodeme/Gold-Band143—~1.4kAutomated safety check: PassAGPL-3.0
Handsontable Demo Page Generatorhandsontable/handsontable22k—~1.8kAutomated safety check: PassCustom licence
Releaseakitaonrails/my-skills212—~1.9kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Handsontable Demo Page Generator

    handsontable/handsontable

    Builds two throwaway HTML test pages for a Handsontable pull request, one on the released CDN version and one on the local build, to compare behavior side by side.

    22k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Release

    akitaonrails/my-skills

    Cut and publish a project release — verify or derive the version number (patch/minor/major) from the changelog and accumulated changes, follow the repo's own branch and versioning strategy, rebase…

    212 GitHub stars~1.9k tokensUpdated 14 days ago
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Creating Description For Gh PR

    redis/jedis

    Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed

More from diodeme/Gold-Band

All 11 skills in this repo

  • Rust Async Patterns

    diodeme/Gold-Band

    Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns.

    143 GitHub starsUsed in 10 repos~3.1k tokens
    Auto-check passed

  • Rust Profiling

    diodeme/Gold-Band

    Rust profiling skill for performance analysis. An agent skill from diodeme/Gold-Band.

    143 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check: notes

  • Memory Leak Debugging

    diodeme/Gold-Band

    Diagnoses and resolves memory leaks in JavaScript/Node.js applications.

    143 GitHub stars~712 tokensUpdated 7 days ago
    Auto-check passed

  • Git Changelog

    diodeme/Gold-Band

    Create and localize user-facing release notes from an explicit Git change range.

    143 GitHub stars~1.4k tokensUpdated 7 days ago
    Auto-check passed

  • Git PR

    diodeme/Gold-Band

    Prepare, review, publish, or update a complete GitHub pull request for the current repository, including local commit readiness, safe push strategy, semantic title validation, repository-native PR…

    143 GitHub stars~1.5k tokensUpdated 7 days ago
    Auto-check passed

  • Stitch Design

    diodeme/Gold-Band

    Unified entry point for Stitch design work. An agent skill from diodeme/Gold-Band.

    143 GitHub starsUsed in 1 repo~925 tokens
    Auto-check passed

Works with

Categories

Questions about Git Issue

What does Git Issue do?

Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification. Git Issue is an agent skill from diodeme/Gold-Band. Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification.

When should I use Git Issue?

Git Issue fits situations like: the user asks to draft; refine a GitHub issue; feature request; performance issue.

How do I install Git Issue in Claude Code?

Run `npx skills add diodeme/Gold-Band --skill git-issue -a claude-code`. Or copy the skill folder (.agents/skills/git-issue in diodeme/Gold-Band) into .claude/skills/git-issue in your project. Claude Code loads it when a task matches its description.

How do I install Git Issue in Codex?

Run `npx skills add diodeme/Gold-Band --skill git-issue -a codex`. Or copy the skill folder (.agents/skills/git-issue in diodeme/Gold-Band) into .agents/skills/git-issue in your project. Codex loads it when a task matches its description.

Can I use Git Issue 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 diodeme/Gold-Band --skill git-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/git-issue, .gemini/skills/git-issue, .github/skills/git-issue and .opencode/skills/git-issue in your project.

What does Git Issue need to run?

Going by SKILL.md and its folder, Git Issue needs the command-line tools its instructions call (gh).

Does Git Issue access the network?

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

Is Git Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Git Issue use?

Git Issue is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Issue use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Git Issue?

Skills that share tags, products or a category with Git Issue: Handsontable Demo Page Generator (handsontable/handsontable, 22k stars), Release (akitaonrails/my-skills, 212 stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Issue?

diodeme (a GitHub user) maintains it in diodeme/Gold-Band, which has 143 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 30, 2026.

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