pr-split
PR Split Instructions
Intent
Transform a large branch into a sequence of small, high-quality PRs that:
- Each do ONE thing well
- Are easy to review (500-1000 lines ideal)
- Tell a coherent story in sequence
- Pass all quality checks
- Have clear, descriptive commit messages that explain WHY
The goal is reviewer experience, not mechanical splitting. Each PR should be something you'd be proud to send for review.
Help
If the user provides a command option of help:
- Explain how to use this prompt.
More from ag-grid/ag-charts
estimate-jira
Estimate complexity, effort, and risks for JIRA tickets, features, or projects. Generates structured reports with time estimates, dependencies, risk analysis, and known unknowns. Use when user asks to "estimate", "size", or "analyze complexity" of work items.
43batch-lint-cleanup
Analyze ESLint violations and auto-fix specific rules in isolation
23recall
Load branch context and browse project memory for session resumption
22plunker
Create and manage Plunker (plnkr.co) code examples for AG Charts and AG Grid. Use this skill whenever the user mentions plunker, plnkr, or plunk, wants to create a shareable code demo or bug reproduction, needs to fork or modify an existing plunk, or asks for a live code example they can share via URL. This includes creating repros for JIRA tickets, building demos for stakeholders, downloading plunks to inspect them, or making any interactive code example hosted on plnkr.co. Also trigger when users ask for "a shareable example", "a repro", "a demo I can send", or "a live example" — even without explicitly saying "plunker".
22sync-ag-shared
Sync ag-shared subrepo changes across ag-charts, ag-grid, and ag-studio repos
22plan-implementation-review
Review plan execution completeness and identify delivery gaps
22