Skip to content

Add explain-issue skill#1441

Merged
dyoshikawa merged 3 commits intomainfrom
explain-issue-skill
Apr 4, 2026
Merged

Add explain-issue skill#1441
dyoshikawa merged 3 commits intomainfrom
explain-issue-skill

Conversation

@dyoshikawa
Copy link
Copy Markdown
Owner

@dyoshikawa dyoshikawa commented Apr 4, 2026

Summary

  • add a new explain-issue official skill under .rulesync/skills/
  • guide agents to explain issue background and proposed solutions from issue details and comments
  • handle missing issue arguments and unspecified solutions explicitly

Test plan

  • pnpm cicheck

Copilot AI review requested due to automatic review settings April 4, 2026 14:09
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds a new official Rulesync skill (explain-issue) under .rulesync/skills/ to guide agents in summarizing a GitHub issue’s background and proposed solution, with explicit handling for missing issue input and unspecified solutions.

Changes:

  • Introduce .rulesync/skills/explain-issue/SKILL.md defining the new explain-issue skill.
  • Instruct agents to gather issue body + comments and produce a concise two-part explanation (background + proposed solution).
  • Add explicit guidance for cases where the solution is not decided/recorded in the issue discussion.

Comment on lines +14 to +17
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`
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.
Copilot AI review requested due to automatic review settings April 4, 2026 14:13
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Comment on lines +1 to +6
---
name: explain-issue
description: "Explain a GitHub issue: the background problem and the proposed solution"
targets:
- "*"
---
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.
@dyoshikawa dyoshikawa merged commit ba9ad94 into main Apr 4, 2026
8 checks passed
@dyoshikawa
Copy link
Copy Markdown
Owner Author

@dyoshikawa Thank you!

@dyoshikawa dyoshikawa deleted the explain-issue-skill branch April 4, 2026 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants