Skip to main content
affpapa.org
RU EN
skill CX Codex

explain-issue — Claude Code skill: GitHub issue analysis

This skill explains the problem behind a GitHub issue and the solution discussed there. Use it to get oriented in an issue and its comments.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add dyoshikawa/rulesync --skill explain-issue -a claude-code
Open on GitHub

What explain-issue does

The skill fetches an issue’s description and metadata with gh issue view <issue_number>, then retrieves its comments with gh issue view <issue_number> --comments. It uses that material to describe the motivation and proposed direction, including constraints mentioned in the discussion.

When an issue points to related pull requests, commits, or files needed to understand the proposal, the skill gathers that context too. If you haven’t provided an issue number, it asks which issue to explain. It relies on gh to read issues, so that command must work in your environment.

What it helps with

  • explain the problem described in a GitHub issue
  • summarize the motivation and suggested solution
  • include relevant comments and linked pull requests
  • identify constraints mentioned in the discussion

Example prompts for the agent

  • Explain GitHub issue 123, covering the underlying problem and the suggested fix.
  • Review owner/repo#42 and include its comments and related pull requests.
  • Summarize why this issue was opened and what next step the discussion proposes.

How to install explain-issue

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/explain-issue/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/explain-issue/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about explain-issue

How do I install explain-issue in Claude Code?

Run npx skills add dyoshikawa/rulesync --skill explain-issue -a claude-code. The skill file is at ~/.claude/skills/explain-issue/SKILL.md.

What does explain-issue do?

It reads a GitHub issue and its comments, then explains the problem and the suggested approach. It also gathers related pull requests, commits, or files when they help clarify the proposal.

Does explain-issue need access to GitHub issues?

It uses gh issue view <issue_number> to retrieve issue details and comments. Related pull requests, commits, or files are gathered when the issue points to them and they help explain the solution.

Source text

SKILL.md · MIT 
---
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 · dyoshikawa/rulesync

Similar skills

SKILL.md skills catalog →
find-skills vercel-labs Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project. CX Codex +1 4,000,000installs frontend-design official anthropics This skill guides intentional visual design for new interfaces and redesigns. Use it when a generic generated UI is not enough. 1,025,790installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. 1,219,756installs improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. 1,163,035installs design-taste-frontend Leonxlnx This skill directs the design of public pages and work screens, then checks the result in a browser through screenshots. Use it when an interface feels generic or unfinished. CX Codex +1 678,700installs

From the same set21

porting-another-repository Reads a feature in your current repo and the target repo's conventions, then writes a porting plan into tmp/ as files you apply yourself. CX Codex +1 ★ 1,557repo stars goal-release Drives a release end to end: opens the PR, waits for green CI, merges it and updates the Homebrew formula. Handy when a version has to ship in one go. CX Codex +1 ★ 1,557repo stars goal-issues-and-release This skill processes open issues, then starts the release workflow. It makes routine choices on its own while keeping the stated safety checks in place. CX Codex +1 ★ 1,557repo stars git-worktree-runner A skill that teaches the agent to drive git worktrees through the gtr CLI: create, open in an editor, run commands, remove. CX Codex +1 ★ 1,557repo stars draft-issue-to-external-repository Drafts a GitHub issue for a repository you do not own: reads the project's templates and title style, settles scope with you, and saves the body to a file. CX Codex +1 ★ 1,557repo stars create-scrap-issue This skill turns notes and findings into one GitHub issue with context, details, and next steps. Use it when you want to keep project scraps for later. CX Codex +1 ★ 1,557repo stars create-issue A skill that walks through issue creation step by step: gathers context, checks the codebase, drafts English text, and assigns labels. Handy when you want a tidy issue without doing it manually. CX Codex +1 ★ 1,557repo stars clean-branches A skill that walks your local git branches, finds merged and orphaned ones, and deletes them one at a time with a closing report. CX Codex +1 ★ 1,557repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor