Skip to content

Add explain-issue skill #1441

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dyoshikawa merged 3 commits into from
Apr 4, 2026
Merged

Add explain-issue skill #1441

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d3ba736
add explain-issue skill
claude Apr 4, 2026
2b405dd
document Japanese response preference
claude Apr 4, 2026
cde83e3
Revert "document Japanese response preference"
claude Apr 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions .rulesync/skills/explain-issue/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
---
name: explain-issue
description: "Explain a GitHub issue: the background problem and the proposed solution"
targets:
- "*"
---
Comment on lines +1 to +6
Copy link

Copilot AI Apr 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR description mentions documenting a maintainer preference for Japanese responses in .github/copilot-instructions.md, but that change doesn’t appear to be included in this PR. Either add the corresponding update to .github/copilot-instructions.md or adjust the PR description to match the actual changes.

Copilot uses AI. Check for mistakes.

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`
Comment on lines +14 to +17
Copy link

Copilot AI Apr 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gh issue view <issue_number> --comments already outputs the issue body/metadata along with comments, so running both gh issue view <issue_number> and gh issue view <issue_number> --comments is redundant and doubles the GitHub API/CLI work. Consider collapsing this into a single gh issue view invocation (or using --json/--jq if you need specific fields) to keep the skill faster and simpler.

Suggested change
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`
Run the following command:
- Get the issue description, metadata, and comments: `gh issue view <issue_number> --comments`

Copilot uses AI. Check for mistakes.

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).
Loading