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

Explain Issue

by dyoshikawa in dyoshikawa/rulesync

Explain a GitHub issue: the background problem and the proposed solution

MITAuto-check passedDevelopment

Install Explain Issue

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

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

GitHub CLI
$ gh skill install dyoshikawa/rulesync explain-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/explain-issue .claude/skills/explain-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
explain-issue
GitHub stars
1.5k
Token cost
~315 tokens
SKILL.md length
164 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
MIT

At a glance

Explain a GitHub issue: the background problem and the proposed solution

  • Works in 2 steps: Gather Issue Information → Analyze and Explain
  • Development work in your project
  • SKILL.md covers Step 1: Gather Issue Information and Step 2: Analyze and Explain
  • Calls gh

What it does

Explain Issue is an agent skill from dyoshikawa/rulesync. Explain a GitHub issue: the background problem and the proposed solution

Its SKILL.md is about 320 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

  • “/explain-issue”

Workflow steps

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

  1. Gather Issue Information
  2. Analyze and Explain

What it can do on your machine

Read from SKILL.md and the folder at commit 2c577d0. 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

Explain Issue loads about 315 tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 164 words of instructions outside code blocks.

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

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 2c577d0, republished under its MIT licence (© dyoshikawa). 164 words, ~315 tokens.

Download SKILL.mdSave it as .claude/skills/explain-issue/SKILL.md (or your agent's skills folder).
name
explain-issue
description
Explain a GitHub issue: the background problem and the proposed solution
targets
*

target_issue = the user's request

If target_issue is not provided, ask the user which issue to explain.

Step 1: Gather Issue Information

Run the following in parallel:

  • Get the issue description and metadata: gh issue view <issue_number>
  • Get the issue comments: gh issue view <issue_number> --comments

If the issue references related pull requests, commits, or files that are needed to understand the solution, gather that context as well.

Step 2: Analyze and Explain

Based on the issue content, explain the following two aspects:

  1. Background (Problem/Motivation): What problem, limitation, or user need does this issue describe? Why does it matter?
  2. Proposed Solution: What solution, direction, or next step is suggested in the issue discussion? Summarize the expected approach, scope, and important constraints if they are mentioned.

If the issue does not contain enough information about the solution, explicitly say that the solution is still undecided or unspecified.

Keep the explanation concise and focused. Use the language of the current conversation (follow the user's language).

© 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/explain-issue of dyoshikawa/rulesync.

Open the folder on GitHubat commit 2c577d0

Compare with similar skills

Explain 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.

Explain Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Explain Issue this skilldyoshikawa/rulesync1.5k—~315Automated 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
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated 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

  • 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

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k 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 Explain Issue

What does Explain Issue do?

Explain a GitHub issue: the background problem and the proposed solution. Explain Issue is an agent skill from dyoshikawa/rulesync.

When should I use Explain Issue?

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

How do I install Explain Issue in Claude Code?

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

How do I install Explain Issue in Codex?

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

Can I use Explain 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 explain-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/explain-issue, .gemini/skills/explain-issue, .github/skills/explain-issue and .opencode/skills/explain-issue in your project.

What does Explain Issue need to run?

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

Does Explain 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 Explain 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 Explain Issue use?

Explain 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 Explain Issue use?

About 315 tokens (SKILL.md is roughly 1.3k 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 Explain Issue?

Skills that share tags, products or a category with Explain 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 Explain Issue?

dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,508 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 9, 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.