github-issue-create

A skill for creating GitHub issues, which are tracked requests for bugs, features, or other tasks, with an automatically prepared title and description.

In plain words
What is it for?
Opening a new GitHub issue from a bug report, feature request, or task description.
Why use it?
It removes the need to manually format issue details and checks that the GitHub account matches the local Git identity.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/aiya000/dotfiles/github-issue-create
Any agent
npx skills add aiya000/dotfiles --skill github-issue-create
Clone the repo
git clone --depth 1 https://github.com/aiya000/dotfiles

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,214 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.01214
Opus 5 $0.00017 $0.00607
Sonnet 5 $0.00007 $0.00243
Haiku 4.5 $0.00003 $0.00121

Measured yesterday against content hash e830b601fe96, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-issue-create scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude_global/skills/github-issue-create/SKILL.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

github-issue-create

Create a GitHub issue using gh issue create with an auto-generated title and description.

Behavior

  1. Check git/gh user consistency:

    • Run git config user.name to get the local git identity
    • Run gh auth status to identify the active GitHub user
    • If gh auth status shows X Failed to log in ... (keyring) for all accounts (even though the user has authenticated):
      • This is a known keyring issue in some environments — treat it as a keyring-unavailable environment
      • Do NOT stop; proceed to the Keyring-unavailable fallback section below
    • If they differ:
      • If acting autonomously: run gh auth switch --user "$(git config user.name)"
        • If switch succeeds: continue
        • If switch fails: defer this skill. After all other work is done, report to the user: the git/gh user mismatch and that the switch failed
      • If not acting autonomously: stop the skill and ask the user to resolve the mismatch before continuing
  2. Review the context provided by the user (bug description, feature request, task details, etc.)

  3. Inspect the repository to understand context if needed:

    • git log --oneline -10 — recent commits for context
    • gh issue list — existing issues to avoid duplicates
  4. Scan for sensitive information before creating (see Secret Scan below)

  5. Generate an appropriate title and description based on the issue type

  6. Create the issue using gh issue create

Issue Types and Labels

Select appropriate labels based on the issue type:

  • bug — Something isn't working correctly
  • enhancement — New feature or improvement request
  • documentation — Documentation improvements
  • question — Further information is requested
  • chore — Maintenance or internal tasks

Issue Description Format

The issue description should be written in English and follow this structure:

Bug Report

## Description

Brief description of the bug.

## Steps to Reproduce

1. Step one
2. Step two
3. Step three

## Expected Behavior

What should happen.

## Actual Behavior

What actually happens.

## Environment

- OS / version information if relevant

Read the full file on GitHub · 147 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 147 lines · 35 tokens per session scan A e830b601fe96

Subscribe to this mod's changes

github-issue-create is a skill published in the GitHub repository aiya000/dotfiles (19 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,214 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

coding

Principles for writing and designing code, covering API and abstraction design, naming, comment discipline, and standards of evidence for claims about code behavior. Use whenever the task is to write or modify code, design an API or software architecture, or review code.

ryota2357/dotfiles · 53 tokens

validate__japanese

日本語の Markdown 文書 (README・ドキュメント・ブログ下書き・.md) を編集した後に起動する。textlint の ja-technical-writing / ja-spacing プリセットで、長すぎる一文・読点過多・文体の混在・全角半角スペースを検出する。さらに文中ハードラップ (文末でない位置で折り返した、意味のない改行) を検出し、段落・箇条書き項目を 1 行に連結して調整する。1 行に文を積み上げた箇所は、箇条書きへの変換候補として検出する。実在のシンボルを指すコードスニペットへ参照リンクも付与する。日本語の .md を変更したときに使用する。.

shunsock/dotfiles · 200 tokens

restart__pull_request

乱れた (fix-up コミット過多・議論の脱線・大規模な書き直し) プルリクエストを、 ユーザーが "restart" / "やり直し" したいときに起動する。既存 PR を close し、 ブランチを新ブランチ上の単一のクリーンなコミットに squash し、過去の PR 議論 (レビューコメント・スレッド・リアクション) を統合した説明文で新しい PR を作成する。 元のブランチを force-push してはならない。必ず新しいブランチを作成する。.

shunsock/dotfiles · 159 tokens

prepare__issue

あなたは要件定義済みの Issue を実装着手可能な状態へ引き上げるオーケストレーターである。 対象は status:acknowledged の Issue であり、完了時に status:ready へ遷移させる。.

shunsock/dotfiles · 145 tokens

rescue__pull_request_review

GitHub PR にレビュアー (人間または AI) がコメントを残した後に起動する。 レビューコメントを読み取り、要求されたコード変更を適用し、コミットして push する。 レビューフィードバックの各ラウンドごとに繰り返す。ユーザーの確認は不要 — Claude がこのプロセス全体を自律的に起動・実行する。.

shunsock/dotfiles · 104 tokens

submit__pull_request

プルリクエストを作成から完了まで一貫して提出するときに起動する。ナラティブ型の PR 説明文を生成し、PR を作成し、CI チェックを監視し、CI の失敗を自動修正する。 PR ナラティブと CI 修正のワークフローを 1 つの自律フローに統合する。.

shunsock/dotfiles · 100 tokens