Cmd Gh Issue
Create structured GitHub issues from conversation context using gh CLI
Install
/plugin marketplace add Olshansk/agent-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Olshansk/agent-skills --skill cmd-gh-issuegit clone --depth 1 https://github.com/Olshansk/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/cmd-gh-issue ~/.claude/skills/cmd-gh-issuePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Create GitHub Issue from Conversation Create a well-structured GitHub issue using `gh` CLI, populated with context from the current conversation. ## Instructions 1. **Determine the repo** -- confirm you're inside a git repo with a GitHub remote: ```bash gh repo view --json nameWithOwner -q '.nameWithOwner' ``` If this fails, ask the user which repo to file against. 2. **Synthesize the conversation** into a GitHub issue body following the structure below. 3. **Create the issue** using `gh`: ```bash gh issue create --title "<concise title>" --body "$(cat <<'ISSUE_EOF' <issue body here> ISSUE_EOF )" ``` 4. **Report back** with the issue URL. ## Issue Body Structure Build the issue body in this exact order: ### Section 1: What & Why Open with a short (2-4 bullet) summary answering: - **What** needs to happen? - **Why** does it matter? (user pain, system constraint, business goal) This section should stand alone -- a reader who stops here should understand the ask. ### Section 2: Context & Discussion This is the bulk of the issue. Capture everything relevant from our conversation: - **Background** -- what led to this discussion - **Current behavior** -- how things work today (or don't) - **Desired behavior** -- what success looks like - **Constraints & decisions** -- trade-offs we discussed, options we rejected and why - **Technical details** -- relevant code paths, configs, schemas, API shapes, error messages
Details
- Skill name
cmd-gh-issue- Repository
- Olshansk/agent-skills
- Path
skills/cmd-gh-issue/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Cmd Gh Issue skill do?
Create structured GitHub issues from conversation context using gh CLI
How do I install the Cmd Gh Issue skill?
Claude Code plugin: /plugin marketplace add Olshansk/agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cmd Gh Issue popular?
It lives in Olshansk/agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Cmd Agent Persona Set
9Olshansk/agent-skills
Prime the agent with a behavioral persona for the conversation
Cmd Clean Code
9Olshansk/agent-skills
Improve code readability without altering functionality using idiomatic best practices
Cmd Code What
9Olshansk/agent-skills
Catch the user up on what the agent has been doing in the current session with 3-5 ultra-tight bullet points. Use when the user invokes /cmd-what, asks "what are you doing", "what did you do", "catch me up", "status", "where are we", or otherwise needs a fast situational summary of in-flight agent work.
Cmd PR Build Context
9Olshansk/agent-skills
Build high-signal PR context for review with diff analysis, risk assessment, and discussion questions
Skill Auditor
5tlzmw001/naiyue-skills
审计第三方 skill 是否名副其实——给定 GitHub 链接或本地路径,抽取其宣称的功能为原子声称清单(claim list),在临时沙箱中通过多轮自迭代场景验证,逐条给出"证实/证伪/无法验证/受阻"结论,并结合设计解析做现象↔机制归因,最终产出证据可追溯的一致性审计报告。当用户想"测一下这个 skill"、"这个 skill 好不好用"、"验证某个 GitHub skill 是否靠谱"、"评估/审计一个 skill"、"帮我看看这个 skill 是不是虚标"时,务必使用本 skill,即使用户没有说出"审计"或"评估"字样。
Cmd PR Conflict Resolver
9Olshansk/agent-skills
Resolve merge conflicts systematically with context-aware 3-tier classification and escalation protocol
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.