Skip to content
Agentmart
Submit a tool

create-issue

Create a GitHub issue with detailed description, purpose, and appropriate labels

Skill by dyoshikawa

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/dyoshikawa-create-issue

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Create a GitHub issue with detailed description, purpose, and appropriate labels

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/create-issue

What's inside

Skill name
create-issue
Description
Create a GitHub issue with detailed description, purpose, and appropriate labels
License
MIT
Instructions
72 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Create GitHub Issue

## Step 1: Gather Information

Receive the issue topic from $ARGUMENTS or the user's description.

If the information is insufficient, ask the user to clarify the following:

- What needs to be done (the task or problem)
- Why it needs to be done (the purpose or motivation)

## Step 2: Research Context

Before writing the issue, investigate the relevant parts of the codebase to understand:

- Which files and modules are affected
- Existing related code patterns
- Potential impact and scope of the change

## Step 3: Draft the Issue

**Important: All issue content (title, body, labels) must be written in English**, regardless of the language used in the conversation with the user.

Create a well-structured issue with the following sections:

```markdown
## Summary

A concise one-liner describing what this issue is about.

## Motivation / Purpose

Why this change is needed. Explain the problem, user impact, or improvement opportunity.

## Details

Detailed description of what needs to be done:

- Specific changes required
- Files or modules likely affected
- Acceptance criteria or expected behavior

## Additional Context

Any relevant links, screenshots, or references (if applicable).
```

## Step 4: Assign Labels

First, get the available labels from the repository:

```bash
gh label list
```

Then choose appropriate labels from the existing repository labels based on the issue content. Also evaluate whether the issue is suitable for newcomers. If the contribution is straightforward (e.g., small scope, well-defined, minimal domain knowledge required), also assign the `good first issue` label if it exists in the repository.

## Step 5: Create the Issue

```bash
gh issue create --title "<concise title>" --body "<drafted body>" --label "<label1>,<label2>,..."
```

## Step 6: Report Result

Output the created issue URL and a summary of:

- Issue title
- Assigned labels
- Whether `good first issue` was applied and why (or why not)

From dyoshikawa/skills, MIT.

More from dyoshikawa/skills

Signals

Stars
0
Forks
0
Open issues
1
Last commit (this folder)
Aug 23, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from dyoshikawa

Cite this page

create-issue skill. Agent Mart. https://agentmart.dev/skills/dyoshikawa-create-issue (last updated 2026-10-24)