explain-issue
Explain a GitHub issue: the background problem and the proposed solution
Profile →npx skills add dyoshikawa/rulesync --skill explain-issue --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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).
- Step 1: Gather Issue Information
- Step 2: Analyze and Explain
What does the explain-issue skill do?
Explain a GitHub issue: the background problem and the proposed solution
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill explain-issue --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.