pr
Prepare a PR with context — summary, blast radius, review areas
PR
Generate a complete pull request description by analyzing branch changes and calculating blast radius. Saves to .ccs/pulls/.
Steps
1. Identify source and target
- Current branch:
git rev-parse --abbrev-ref HEAD - Target: user-provided or default
main/master - Read
.ccs/branches/<current>.mdif exists (regenerate if stale)
2. Gather change data
git log --oneline <target>..<current>→ commitsgit diff --stat <target>...<current>→ files changed with line countsgit diff --shortstat <target>...<current>→ totalsgit log --format="%h %s" <target>..<current>→ commit messages
3. Analyze impact
- Read
.ccs/file-index.md→ rank changed files - Read
.ccs/project-map.md→ find downstream dependents - Read
.ccs/architecture.md→ module boundaries - Categorize changes: feature, fix, refactor, config, docs
4. Identify review areas
- Must review: S-rank files, 50+ line changes, shared utilities
- Should review: A-rank files, cross-module changes
- Quick check: B/C/D-rank files, config, docs
5. Generate PR document
Create .ccs/pulls/<branch-name>.md: title, summary (2-3 sentences), changes table (file, action, lines, rank, impact), blast radius, commits, review areas, test recommendations.
6. Output PR description
Also output a clean, paste-ready PR description: summary, bullet changes, test plan, blast radius.
7. Log to .ccs/task.md
Append using template at .claude/skills/_ccs/templates/task-template.md: branch → target, commits count, files changed, blast radius, review areas.
Rules
- Read branch ref first — it has most context already
- Use
--statand--shortstatinstead of full diffs - Cap dependency walking at 1 level (direct dependents only)
- For large PRs (50+ files) → summarize top 20 by rank
- Does not create the actual PR on GitHub — outputs description only. Use
gh pr createto submit.
Refs
- Branch refs:
.ccs/branches/ - PR docs:
.ccs/pulls/ - File index:
.ccs/file-index.md - Task template:
.claude/skills/_ccs/templates/task-template.md
10x-Code v2.0.0