Menu
Procedure for creating and managing stacked PRs when a task exceeds 200 diff lines. Use this when a task is too large for a single PR.
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
E2E test skill that confirms plugin loading works.
Templates and process for creating devcontainer configurations. Use this when setting up a new project, adding devcontainer support, or creating devcontainers for worktrees.
Procedure for creating a git worktree and devcontainer for a new task. Use this when starting a new development task.
Cross-model code review before every PR. Use this after code is written and before pushing.
Mandatory checklist before starting implementation. Use this before writing code for any non-trivial task.
Production Dockerfile and container runtime security checklist. Use this when building Docker/Podman images or configuring container deployments.
| name | stacked-prs |
| description | Procedure for creating and managing stacked PRs when a task exceeds 200 diff lines. Use this when a task is too large for a single PR. |
When a task will produce more than 200 diff lines, split it into a stack of PRs. Each PR must be fully functional, standalone, and independently reviewable.
Before writing code, define the stack:
Stack for feature/PROJ-123-user-auth:
PR 1: feature/PROJ-123-user-auth-model — User model and migrations
PR 2: feature/PROJ-123-user-auth-api — Auth API endpoints
PR 3: feature/PROJ-123-user-auth-ui — Login/signup UI
Each PR must:
# PR 1: branch from main
git checkout -b feature/PROJ-123-user-auth-model main
# PR 2: branch from PR 1
git checkout -b feature/PROJ-123-user-auth-api feature/PROJ-123-user-auth-model
# PR 3: branch from PR 2
git checkout -b feature/PROJ-123-user-auth-ui feature/PROJ-123-user-auth-api
main.## Stack
- **PR 1** (this): User model and migrations → `main`
- PR 2: Auth API endpoints → `feature/PROJ-123-user-auth-model`
- PR 3: Login/signup UI → `feature/PROJ-123-user-auth-api`
Always bottom-up:
main.main, then merge.main, then merge.If a reviewer requests changes to PR 1: