원클릭으로 Manus에서 모든 스킬 실행

시작하기

explain-issue

스타1,251

포크135

업데이트2026년 7월 22일 05:39

Explain a GitHub issue: the background problem and the proposed solution

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

dyoshikawa

dyoshikawa/rulesync

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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:

Background (Problem/Motivation): What problem, limitation, or user need does this issue describe? Why does it matter?
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).

이 저장소의 다른 Skills

같은 저장소

draft-release

dyoshikawa/rulesync

Draft a new release of the project.

2026-07-221.3k

agent-team

dyoshikawa/rulesync

Form an Agent Team of Implementer and Reviewer subagents to tackle the given task, looping implementation and review until the Reviewer reports zero high-or-above findings and no more than three mid findings.

2026-07-221.3k

approve

dyoshikawa/rulesync

Approve a pull request using gh pr review --approve

2026-07-221.3k

babysit-dependabot-pr

dyoshikawa/rulesync

Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed), get every check green, and merge. Use when the user wants to shepherd a Dependabot bump PR to merge.

2026-07-221.3k

batch-all-issues

dyoshikawa/rulesync

Resolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the `goal-pr` skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.

2026-07-221.3k

batch-all-scrap-issues

dyoshikawa/rulesync

Resolve every open maintainer-scrap issue one at a time: fact-check each with web research, close the ones that need no action, and run the `goal-pr` skill to fix, review, and merge the ones that do — repeating until no actionable scrap issues remain.

2026-07-221.3k

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:

Background (Problem/Motivation): What problem, limitation, or user need does this issue describe? Why does it matter?
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).