How do I install the Gh Issue Push skill?

Run npx skillmds@latest add petar-djukic/gh-issue-push in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Gh Issue Push skill do?

Create a GitHub issue in the current repository. It is listed under Coding & Dev Tools on SkillMD.

Is Gh Issue Push safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Issue Push?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Issue Push free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Issue Push?

petar-djukic (@petar-djukic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Issue Push by petar-djukic — Agent Skill

Name: Gh Issue Push
Author: petar-djukic

File contents

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-pushdescription: Create a GitHub issue in the current repository.---# gh-issue-push commandApply this command workflow. Treat any text after its invocation as the command input.Create a GitHub issue in the current repository.## Input$ARGUMENTS## Steps1. Detect the repo: run `gh repo view --json nameWithOwner -q .nameWithOwner` and use the result as `<owner>/<repo>` for all `gh` commands.2. Determine type from the input: keywords like "bug", "fix", "broken", "crash" → bug; otherwise → enhancement.3. **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.4. 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.5. Create the issue: ``` gh issue create --repo <owner>/<repo> --title "<title>" --body "<body>" --label "<bug|enhancement>" ```6. Report the issue URL.

Frequently asked questions

Gh Issue Push