Menu
Fetch and display comments from the current GitHub pull request. Use when asked to show PR comments, review comments, or check PR feedback.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Reorganize messy git commit history on a feature branch into clean, reviewer-friendly commits. Use when: user says "コミットを整理", "organize commits", "squash commits", "clean up history", "rewrite commits", or wants to prepare a branch for PR review by removing trial-and-error noise. Handles soft reset, logical grouping, and recommitting with clear messages.
Safely rebase the current branch onto the latest origin/main. Stashes uncommitted work, fetches, rebases, and restores.
Reviews changed code for reuse, quality, and efficiency, then fixes issues found. Preserves all functionality.
Create an HTML report to review the current session's changes. Include screenshots when changes affect UI/visuals. Use when the user asks for a review report, session summary as HTML, or visual diff of changes.
Capture screenshots of the current work-in-progress UI via agent-browser against a running local dev server, then open them with google-chrome-stable. For UI changes, capture before/after pairs (and Figma reference shots when a design URL is provided) so visual diffs can be reviewed at a glance.
Create a branch, commit changes, push to remote, and create a pull request. Use when asked to create a PR or pull request.
| name | pr-comments |
| description | Fetch and display comments from the current GitHub pull request. Use when asked to show PR comments, review comments, or check PR feedback. |
| url | claude code |
Fetch and display comments from a GitHub pull request.
gh pr view --json number,headRepository to get the PR number and repository infogh api /repos/{owner}/{repo}/issues/{number}/comments to get PR-level commentsgh api /repos/{owner}/{repo}/pulls/{number}/comments to get review comments. Pay particular attention to the following fields: body, diff_hunk, path, line, etc. If the comment references some code, consider fetching it using eg gh api /repos/{owner}/{repo}/contents/{path}?ref={branch} | jq .content -r | base64 -d## Comments
[For each comment thread:]
- @author file.ts#line:
```diff
[diff_hunk from the API response]
quoted comment text
[any replies indented]
If there are no comments, return "No comments found."
## Rules
1. Only show the actual comments, no explanatory text
2. Include both PR-level and code review comments
3. Preserve the threading/nesting of comment replies
4. Show the file and line number context for code review comments
5. Use jq to parse the JSON responses from the GitHub API