القائمة
Analyze a large request (PR or MR) and propose how to split it into smaller, reviewable units.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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.
استنادا إلى تصنيف SOC المهني
| name | split-request |
| description | Analyze a large request (PR or MR) and propose how to split it into smaller, reviewable units. |
| allowed-tools | ["Read","Glob","Grep","Bash"] |
git branch --show-current 2>/dev/nullAnalyze a large review and propose how to split it into smaller, reviewable units for easier operator review.
/git:split-request <number> - Analyze review and propose split strategy/git:split-request - Analyze current branch's reviewFetch review details:
!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/checkout-review.sh 2>/dev/null || echo "UNCONFIGURED: run setup-claude.sh to set up platform-commands"
git log main..HEAD --oneline
git diff main --stat
Analyze changes — Categorize each file/change into logical units:
Identify dependencies — Determine which changes depend on others:
Propose split — Present a table to the operator:
| $REVIEW_UNIT | Description | Branch | Target | ~Lines | Dependencies |
|--------------|-------------|--------|--------|--------|--------------|
| 1 | Extract helper methods | refactor/helpers | main | ~50 | None |
| 2 | Add utilities | refactor/utils | main | ~40 | None |
| 3 | Package restructure | refactor/package | main | ~600 | None |
| 4 | New feature + tests | feature/name | $REVIEW_UNIT 3 | ~1000 | $REVIEW_UNIT 3 |
Ask for confirmation:
For stacked reviews (when review B modifies files review A creates):
Empty stubs technique — When restructuring into a new package:
## Proposed Split: 4 $REVIEW_UNITs
### $REVIEW_UNIT 1: OrderProcessor Helper Extraction (~50 lines)
**Branch:** `refactor/order-helpers` off `main` → `main`
- Extract `_validate_order()`, `_record_transaction()` helpers
- Pure refactor, no behavior change
### $REVIEW_UNIT 2: Package Restructure with Stubs (~600 lines)
**Branch:** `refactor/pipeline-package` off `main` → `main`
- Split pipeline.py into package structure
- Add empty stubs for future modules
### $REVIEW_UNIT 3: New Feature Implementation (~1000 lines)
**Branch:** `feature/batch-processing` off `refactor/pipeline-package` → $REVIEW_UNIT 2
- Implement stub files with actual functionality
- Add tests
**Merge order:** $REVIEW_UNITs 1-2 can merge independently. After $REVIEW_UNIT 2 merges, retarget $REVIEW_UNIT 3 to main.
/git:repoint-branch/git:split-request — You have a large review and need help figuring out how to split it. This skill analyzes the diff, categorizes changes, identifies dependencies, and proposes a split strategy./git:repoint-branch — You already know which files to extract. This skill creates a new branch from main with those specific files and optionally opens a review.Typical flow: /git:split-request to plan → /git:repoint-branch to execute each proposed split.
/git:explore-request first if you need to understand the review before splitting