gh-issue-push

Create a GitHub issue in the current repository.

跳到安装

仓库: petar-djukic/coding-skills
最近来源活动: 2026年7月26日 03:31
检测到的 SKILL.md 语言: 英语
星标: 2
分支: 0

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/petar-djukic/coding-skills --skill gh-issue-push

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

gh-issue-push command

Apply this command workflow. Treat any text after its invocation as the command input.

Create a GitHub issue in the current repository.

Input

$ARGUMENTS

Steps

Detect the repo: run gh repo view --json nameWithOwner -q .nameWithOwner and use the result as <owner>/<repo> for all gh commands.

Determine type from the input: keywords like "bug", "fix", "broken", "crash" → bug; otherwise → enhancement.

Trace what the change touches. Before drafting, identify every file and field affected — not just the primary target. The executor will do exactly what the issue says and nothing else, so anything omitted will be missed.

Read the files involved to understand their structure.
grep for identifiers, names, or values being added, changed, renamed, or deleted. Search the full project, not just the obvious files.
For each hit, note the file path, the field or line, and what needs to change.
Check for status fields, summary fields, titles, index entries, cross-reference IDs, and out_of_scope references — these are the most commonly missed.

Draft a concise title and well-structured body.

Bug: problem, expected vs actual behavior, reproduction steps if provided.
Enhancement: description and acceptance criteria.
Both: include a "Files to Create/Modify" section listing every file. Under each file, list the specific fields or lines to change. If a value appears in multiple places in the same file, list each occurrence.
Code issues: include an Estimated LOC: line — the model's prediction of production lines of code (and test lines if separable). This is the estimate of record; the actual count is captured at completion by /gh-issue-pop, so estimation accuracy can be tracked over time.

Create the issue:

gh issue create --repo <owner>/<repo> --title "<title>" --body "<body>" --label "<bug|enhancement>"

Report the issue URL.

name	gh-issue-push
description	Create a GitHub issue in the current repository.

gh-issue-push command

Apply this command workflow. Treat any text after its invocation as the command input.

Create a GitHub issue in the current repository.

Input

$ARGUMENTS

Steps

Detect the repo: run gh repo view --json nameWithOwner -q .nameWithOwner and use the result as <owner>/<repo> for all gh commands.
Determine type from the input: keywords like "bug", "fix", "broken", "crash" → bug; otherwise → enhancement.
Trace what the change touches. Before drafting, identify every file and field affected — not just the primary target. The executor will do exactly what the issue says and nothing else, so anything omitted will be missed.
- Read the files involved to understand their structure.
- grep for identifiers, names, or values being added, changed, renamed, or deleted. Search the full project, not just the obvious files.
- For each hit, note the file path, the field or line, and what needs to change.
- Check for status fields, summary fields, titles, index entries, cross-reference IDs, and out_of_scope references — these are the most commonly missed.
Draft a concise title and well-structured body.
- Bug: problem, expected vs actual behavior, reproduction steps if provided.
- Enhancement: description and acceptance criteria.
- Both: include a "Files to Create/Modify" section listing every file. Under each file, list the specific fields or lines to change. If a value appears in multiple places in the same file, list each occurrence.
- Code issues: include an Estimated LOC: line — the model's prediction of production lines of code (and test lines if separable). This is the estimate of record; the actual count is captured at completion by /gh-issue-pop, so estimation accuracy can be tracked over time.

Create the issue:

gh issue create --repo <owner>/<repo> --title "<title>" --body "<body>" --label "<bug|enhancement>"

Report the issue URL.

gh-issue-push

来源信息

安装方式

检查来源文件

同仓库更多 Skills

gh-issue-push command

Input

Steps

gh-issue-push command

Input

Steps

同仓库更多 Skills