New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Create Issue

by dyoshikawa in dyoshikawa/rulesync

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

MITAuto-check passedDevelopment

Install Create Issue

skills CLI
$ npx skills add dyoshikawa/rulesync --skill create-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dyoshikawa/rulesync create-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.rulesync/skills/create-issue .claude/skills/create-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-issue
GitHub stars
1.5k
Token cost
~532 tokens
SKILL.md length
212 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 6 steps: Gather Information → Research Context → Draft the Issue → …
  • Development work in your project
  • SKILL.md covers Step 1: Gather Information, Step 2: Research Context, Step 3: Draft the Issue and Step 4: Assign Labels, plus 2 more sections
  • Calls gh

What it does

Create Issue is an agent skill from dyoshikawa/rulesync. Create a GitHub issue with detailed description, purpose, and appropriate labels

Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with GitHub. The repository describes itself as: A Utility CLI for AI Coding Agents. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/create-issue”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Gather Information
  2. Research Context
  3. Draft the Issue
  4. Assign Labels
  5. Create the Issue
  6. Report Result

What it can do on your machine

Read from SKILL.md and the folder at commit 85bcaf6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create Issue loads about 532 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 212 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~23
When it runs · the whole SKILL.md, loaded when a task matches
~532

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dyoshikawa/rulesync at commit 85bcaf6, republished under its MIT licence (© dyoshikawa). 212 words, ~532 tokens.

Download SKILL.mdSave it as .claude/skills/create-issue/SKILL.md (or your agent's skills folder).
name
create-issue
description
Create a GitHub issue with detailed description, purpose, and appropriate labels
targets
*

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)

© dyoshikawa, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .rulesync/skills/create-issue of dyoshikawa/rulesync.

Open the folder on GitHubat commit 85bcaf6

Compare with similar skills

Create Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Issue this skilldyoshikawa/rulesync1.5k—~532Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Summarise Ecosystem Resultsastral-sh/ruff50k1 repos~2.2kAutomated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Summarise Ecosystem Results

    astral-sh/ruff

    Official

    A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…

    50k GitHub starsUsed in 1 repo~2.2k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

More from dyoshikawa/rulesync

All 40 skills in this repo

  • Rulesync Feature Research

    dyoshikawa/rulesync

    Maps rulesync feature implementations to upstream coding-agent documentation.

    1.5k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Babysit Dependabot PR

    dyoshikawa/rulesync

    Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed)…

    1.5k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Commit Push PR

    dyoshikawa/rulesync

    Commit current changes, push to remote, and create or update a pull request.

    1.5k GitHub stars~458 tokensUpdated today
    Auto-check passed

  • Git Worktree Runner

    dyoshikawa/rulesync

    Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.

    1.5k GitHub stars~1.3k tokensUpdated today
    Auto-check: notes

  • Goal PR

    dyoshikawa/rulesync

    Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge.

    1.5k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Goal Release

    dyoshikawa/rulesync

    Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the…

    1.5k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Create Issue

What does Create Issue do?

Create a GitHub issue with detailed description, purpose, and appropriate labels. Create Issue is an agent skill from dyoshikawa/rulesync.

When should I use Create Issue?

Create Issue fits situations like: development work in your project.

How do I install Create Issue in Claude Code?

Run `npx skills add dyoshikawa/rulesync --skill create-issue -a claude-code`. Or copy the skill folder (.rulesync/skills/create-issue in dyoshikawa/rulesync) into .claude/skills/create-issue in your project. Claude Code loads it when a task matches its description.

How do I install Create Issue in Codex?

Run `npx skills add dyoshikawa/rulesync --skill create-issue -a codex`. Or copy the skill folder (.rulesync/skills/create-issue in dyoshikawa/rulesync) into .agents/skills/create-issue in your project. Codex loads it when a task matches its description.

Can I use Create Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dyoshikawa/rulesync --skill create-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-issue, .gemini/skills/create-issue, .github/skills/create-issue and .opencode/skills/create-issue in your project.

What does Create Issue need to run?

Going by SKILL.md and its folder, Create Issue needs the command-line tools its instructions call (gh).

Does Create Issue access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Create Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create Issue use?

Create Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Issue use?

About 532 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Issue?

Skills that share tags, products or a category with Create Issue: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Issue?

dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,507 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 8, 2026.

Source: dyoshikawa/rulesync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.