Menu
Explain a GitHub issue: the background problem and the proposed solution
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Approve a pull request using gh pr review --approve
Batch-triage open pull requests: list PRs with prs-awaiting-maintainer, review each with review-pr, then post-review-comments when there are merge-blocker findings, or create-scrap-issue for non-blocking findings and merge-pr when there are none. Use when the user wants to review and resolve a batch of PRs in one pass.
Clean up unnecessary local branches and prune stale remote-tracking branches
Clean git worktrees created by git-worktree-runner
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
Analyze the differences between the current branch and origin/main, and summarize the current work progress
| name | explain-issue |
| description | Explain a GitHub issue: the background problem and the proposed solution |
target_issue = $ARGUMENTS
If target_issue is not provided, ask the user which issue to explain.
Run the following in parallel:
gh issue view <issue_number>gh issue view <issue_number> --commentsIf the issue references related pull requests, commits, or files that are needed to understand the solution, gather that context as well.
Based on the issue content, explain the following two aspects:
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).