بنقرة واحدة
explore-request
Fetch and analyze a request's (PR or MR) diff and metadata, then enter interactive Q&A mode.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Fetch and analyze a request's (PR or MR) diff and metadata, then enter interactive Q&A mode.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Capture session learnings and save to skills, guidelines, or reference docs under ~/.claude/.
Orchestrate parallel claude -p sessions — bootstrap, launch, monitor, and converge. Works with any skill that produces manifest.json, item directories, and a runner script.
Create a request (pull request or merge request) or update an existing one following project conventions.
Resolve merge or rebase conflicts between branches.
Assess open PRs with unaddressed review comments and generate a parallel addressing script — produces manifest.json and let-it-rip.sh for address-request-comments execution.
Assess open work items and generate a parallel execution script — produces manifest.json and let-it-rip.sh for implement/clarify execution.
| name | explore-request |
| description | Fetch and analyze a request's (PR or MR) diff and metadata, then enter interactive Q&A mode. |
| argument-hint | [request-number] |
| allowed-tools | ["Read","Glob","Grep","Bash"] |
git branch --show-current 2>/dev/nullPull down a review to understand its changes, get context, and ask questions.
/git:explore-request <number> - Explore review by number/git:explore-request <url> - Explore review by URL/git:explore-request - Explore review for current branch (if one exists)Parse review identifier from $ARGUMENTS:
URL_PATTERN), extract review number from URLFetch review metadata (run in parallel):
cat ~/.claude/platform-commands/fetch-review-details.sh 2>/dev/null || echo "UNCONFIGURED: run setup-claude.sh to set up platform-commands"cat ~/.claude/platform-commands/fetch-review-files.sh 2>/dev/null || echo "UNCONFIGURED: run setup-claude.sh to set up platform-commands"cat ~/.claude/platform-commands/fetch-review-commits.sh 2>/dev/null || echo "UNCONFIGURED: run setup-claude.sh to set up platform-commands"Display review summary (store as REVIEW_CONTEXT):
PR #<number>: <title>
Author: <author>
Branch: <source_branch> → <target_branch>
Status: <state>
Created: <created_at>
## Description
<body>
## Files Changed (<count>)
- <file1>
- <file2>
...
## Commits (<count>)
- <sha1>: <message1>
- <sha2>: <message2>
...
Fetch the diff (store as REVIEW_DIFF):
!cat ~/.claude/platform-commands/fetch-review-diff.sh 2>/dev/null || echo "UNCONFIGURED: run setup-claude.sh to set up platform-commands"
If diff is large (>500 lines), summarize by file:
Offer to checkout the review branch (optional): Ask: "Would you like me to checkout this branch locally? (y/n)"
If yes:
!cat ~/.claude/platform-commands/checkout-review.sh 2>/dev/null || echo "UNCONFIGURED: run setup-claude.sh to set up platform-commands"
Enter Q&A mode: Present to the operator:
I now have full context on PR #<number>. You can ask me:
- What does this PR change?
- Why was <file> modified?
- Are there any potential issues?
- How does <function/class> work now?
- What's the testing strategy?
Ask any questions about this review, or say "done" to exit.
Answer questions using REVIEW_CONTEXT and REVIEW_DIFF:
PR #42: Add user authentication
Author: @developer
Branch: feature/auth → main
Status: OPEN
Created: 2024-01-15
## Description
This PR adds JWT-based authentication with:
- Login/logout endpoints
- Token refresh mechanism
- Protected route middleware
## Files Changed (5)
- src/auth/jwt.py
- src/auth/middleware.py
- src/routes/auth.py
- tests/auth/test_jwt.py
- tests/auth/test_middleware.py
## Commits (3)
- abc1234: Add JWT token generation
- def5678: Add auth middleware
- ghi9012: Add tests
---
I now have full context on PR #42. You can ask me:
- What does this PR change?
- Why was <file> modified?
- Are there any potential issues?
- How does <function/class> work now?
- What's the testing strategy?
Ask any questions about this PR, or say "done" to exit.
After exploring a review, you may want to:
| Next Step | Skill |
|---|---|
| Address review comments | /git:address-request-comments |
| Split a large review | /git:split-request |
| Preview/resolve merge conflicts | /git:resolve-conflicts --preview |