explain-issue
Explain a GitHub issue: the background problem and the proposed solution
Best use case
explain-issue is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Explain a GitHub issue: the background problem and the proposed solution
Teams using explain-issue should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/explain-issue/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How explain-issue Compares
| Feature / Agent | explain-issue | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Explain a GitHub issue: the background problem and the proposed solution
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
target_issue = $ARGUMENTS 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).
Related Skills
create-scrap-issue
Create a GitHub issue that consolidates passed content into a single scrap issue with background context and solution details, labeled as maintainer-scrap. Use when the user wants to create a scrap issue, jot down notes as a GitHub issue, or save findings for later.
create-issue
Create a GitHub issue with detailed description, purpose, and appropriate labels
explain-pr
Explain a PR: the background problem and the proposed solution
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
security-scan-diff
Scan for malicious code in git diff between a tag/commit and HEAD
release-dry-run
Dry run for release: summarize changes since last release and suggest version bump.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
git-worktree-runner
Manages git worktrees using git-worktree-runner (gtr). Use when the user needs to create, list, remove, or navigate worktrees with `git gtr` commands, open editors or AI tools in worktrees, manage parallel development branches, or check out GitHub PRs (including from forks) into worktrees.
draft-release
Draft a new release of the project.
review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "/review-pr".
review-and-comments
Review a PR for code quality and security issues, then post review comments on it. Runs review-pr followed by post-review-comments sequentially.