ReddRadar
Agent skill
github-issue-creator
Create GitHub issues with gh CLI, including standard issues and sub-issues linked to a parent issue. Use when creating a new issue, breaking down a larger issue into child issues, or establishing a parent-child relationship between issues. Detect repository issue templates, apply title and body conventions, and create the issue with gh CLI.
Install this agent skill to your Project
npx add-skill https://github.com/scizorman/dotfiles/tree/main/modules/home/coding-agent/config/skills/github-issue-creator
Metadata
Additional technical details for this skill
- short description
- Create GitHub issues and sub-issues with gh CLI
SKILL.md
GitHub Issue Creator
This skill handles the full lifecycle of creating a GitHub issue: gathering inputs, detecting repository templates, and creating the issue with gh CLI.
When a parent issue is specified, the workflow extends to link the created issue as a sub-issue.
If any required information is missing, ask the user before proceeding.
Confirm Inputs
Confirm the following before creating the issue, because creating an issue in the wrong repository or under the wrong parent is tedious to undo.
- target repository
- issue title and purpose
- labels, assignees, and milestone when specified
- parent issue number when the new issue should become a sub-issue
Detect Templates
Detect issue templates in the target repository. Following the repository's established template keeps the issue readable and consistent for maintainers. Filenames are case-insensitive.
Single-file template locations in priority order:
.github/issue_template.mdissue_template.md(repository root)docs/issue_template.md
Multiple-template directory locations:
.github/ISSUE_TEMPLATE/ISSUE_TEMPLATE/(repository root)docs/ISSUE_TEMPLATE/
If a single-file template exists, read and follow it. If a templates directory exists, list the available templates and ask the user which one to use. If no template exists, use templates/default.md. Note that this default template is written in Japanese.
Create the Issue
Write the final issue body to /tmp/gh-issue-body.md, then create the issue with --body-file.
This avoids shell parsing problems caused by headings or HTML comments in the body.
If gh is unavailable, unauthenticated, or lacks access to the target repository, stop and report the failure clearly.
gh issue create --title "<title>" --body-file /tmp/gh-issue-body.md
When targeting a different repository, use -R OWNER/REPO.
gh issue create -R OWNER/REPO --title "<title>" --body-file /tmp/gh-issue-body.md
Record the created issue URL.
Title format
Write the title as a natural-language sentence describing the issue.
This keeps issue lists and search results readable.
Commit-message format (e.g., fix(auth): bug) is meaningless outside of a git log and makes issues harder to scan.
Good examples:
- ログイン時にセッションタイムアウトが発生する
- ダークモード切り替え機能を追加したい
- Login session timeout occurs unexpectedly
Bad examples:
- fix(auth): session timeout bug
- Bug
Link a Parent Issue
When a parent issue is specified, read references/github-sub-issue-link.md for the exact commands to link the created issue as a sub-issue. Report the created issue URL after the link succeeds.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
scizorman/dotfiles
project-plan-creator
Creates project management plans in Markdown. Use when creating project plans, defining how to manage scope/schedule/risk/communication, or detailing project execution strategy. Primarily for internal projects that build systems, processes, or organizational capabilities.
scizorman/dotfiles
github-project-operator
Manages GitHub Projects v2 write operations using gh CLI. Use when adding issues or PRs to a project, creating tasks (issues) in a project, updating field values (Status, Priority, Size, Sprint, etc.), creating draft issues, creating fields, or archiving items. Also use at the start of a session when selecting a project to work with.
scizorman/dotfiles
github-issue-pr-commenter
Post structured comments to GitHub Issues and Pull Requests with gh CLI. Use when reporting completed work, sharing progress, summarizing investigation results, recording design decisions, proposing implementation plans, asking for feedback, or adding supplementary context to a pull request conversation. Do not use for inline pull request review comments on specific files or lines.
scizorman/dotfiles
github-pr-creator
Submit changes as a GitHub Pull Request with gh CLI. Covers the full workflow: issue confirmation, branch naming, ghq-based git worktree creation or reuse, commit and push, PR template detection, and PR creation with gh pr create. Use when creating a pull request, opening a PR, starting work on an issue, or cutting a working branch.
scizorman/dotfiles
project-charter-creator
Use this skill whenever the user wants to create, draft, or improve a Project Charter. Triggers include: any mention of 'project charter', 'charter', 'プロジェクト憲章', 'プロジェクトチャーター', 'プロジェクト企画書', or requests to formally authorize a project, define project scope and objectives, align stakeholders, or establish project governance. Also use when the user says 'プロジェクトの立ち上げ', 'プロジェクトの認可', 'キックオフ文書', or mentions needing to get sponsor approval for a project. This skill covers project charters for any methodology (Waterfall, Agile, Lean Six Sigma) and any domain (IT, construction, marketing, organizational change, product development, etc.). Use this skill even if the user just says 'help me start a project' or 'I need to get alignment on my project'.
scizorman/dotfiles
github-project-reporter
Reads and analyzes GitHub Projects v2 data using gh CLI. Use when listing items by status, extracting high-priority tasks, generating sprint progress summaries, detecting blockers or health issues (unassigned items, overdue items, WIP excess), or producing progress reports.
Didn't find tool you were looking for?