# Scizorman Dotfiles Github Issue Creator

> GitHub Issue Creator

- Skill: `tomevault-io/scizorman-dotfiles-github-issue-creator` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/scizorman-dotfiles-github-issue-creator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/scizorman-dotfiles-github-issue-creator/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/scizorman-dotfiles-github-issue-creator

---


# 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.md`
- `issue_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](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.

```bash
gh issue create --title "<title>" --body-file /tmp/gh-issue-body.md
```

When targeting a different repository, use `-R OWNER/REPO`.

```bash
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](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.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/scizorman) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-14 -->