What is create-issue?

A workflow that creates a formatted issue in the current Git repository after your approval. It detects whether the repository uses GitHub, GitLab, or Forgejo and uses the matching command-line tool.

Use it to turn a supplied topic or description into a labeled issue after reviewing the repository's available labels.

It removes the repetitive work of formatting an issue and choosing the correct tool while ensuring labels already exist in the repository.

create-issue — Skill for Claude Code by sgaunet/claude-plugins

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add sgaunet/claude-plugins --skill create-issue

Clone the repo

git clone --depth 1 https://github.com/sgaunet/claude-plugins

Made for: Claude Code.

Or install software-engineering, the plugin that ships this one along with the rest of its 18 skills, 7 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sgaunet/claude-plugins/create-issue/github.svg)](https://agentmods.dev/skills/sgaunet/claude-plugins/create-issue)

Your own site

<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/create-issue"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/create-issue/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/create-issue"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/create-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 661 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.00661
Opus 5.5	$0.00007	$0.00264
Sonnet 5.5	$0.00003	$0.00132
Haiku 4.5	$0.00002	$0.00066

Measured 22d ago against content hash 9e575cc0fe5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 22d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/software-engineering/skills/create-issue/SKILL.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Issue

Create an issue for the current git repository. This skill automatically detects whether the repository is hosted on GitHub, GitLab, or Forgejo and uses the appropriate CLI tool (gh, glab, or fgj).

Process

Detect Repository Host: Use the detect-repo-host skill to identify the hosting service (GitHub, GitLab, or Forgejo) and extract owner/repo details.
Validate Arguments: Ensure the issue topic/description is provided as $argument
Always list available labels before creating the issue. Do not add labels that do not exist in the host repository.
- GitHub: Use gh label list --repo <owner>/<repo> via Bash
- GitLab: Use glab label list
- Forgejo: Use fgj label list -R <owner>/<repo>
Create Issue: Use the appropriate CLI tool:
- GitHub: Use gh issue create --repo <owner>/<repo> --title "<title>" --body "<body>" --label "<label1>" --label "<label2>"
- GitLab: Use glab issue create --title "<title>" --description "<body>" --label "<label1>" --label "<label2>"
- Forgejo: Use fgj issue create -R <owner>/<repo> -t "<title>" -b "<body>" -l <label1> -l <label2>
Request Permission: Always ask the user for permission before creating the issue

Issue Content Guidelines

The issue content should be based on: $argument

Requirements:

Title: Clear, concise summary (max 80 characters)
Description: Detailed explanation including:
- Problem description or feature request
- Steps to reproduce (if bug)
- Expected behavior
- Current behavior
- Additional context or screenshots
Labels: Suggest appropriate labels based on those available in the host repository.

Formatting:

Use proper markdown formatting
Include code blocks with syntax highlighting when relevant
Add checklists for actionable items
Reference related issues or PRs when applicable

Error Handling

If repository host detection fails: The detect-repo-host skill provides detailed error messages (not a git repo, no remotes, unsupported host)
If gh/glab/fgj CLI not installed: Inform user and suggest installing the appropriate CLI tool

Read the full file on GitHub · 64 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

22d ago First seen · 64 lines · 17 tokens per session scan A 9e575cc0fe5b

Subscribe to this mod's changes

create-issue is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 17 tokens to every session and 661 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-25.

Claude Code DevOps and cloud Git and workflow Project management ai-agents claude-code-marketplace claude-code-plugins developer-tools

glab

Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.

NikiforovAll/claude-code-rules · 59 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

retro

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

phuryn/pm-skills · 52 tokens

create-issue