القائمة
Classify PRs and produce a priority-ordered merge plan. Use when the user says "merge order", "which PR first", "merge plan", or has multiple PRs targeting the same branch that need sequencing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate protocol-compliant adapter stubs for Bucket 3 operations requiring external services. Use when the user requests "adapter stub", "dry run", "Bucket 3", "Linear ticket stub", "Kafka stub", or needs a fail-soft fallback for unavailable services.
Refine rough ideas into validated design docs through collaborative dialogue. Use when the user says "brainstorm", "help me design", "explore a feature", "let's think about", or has a vague idea that needs structure before coding.
Add multi-layer validation to fix bugs caused by invalid data. Use when debugging data corruption, invalid input reaching deep execution, "defense in depth", or when a bug needs structural prevention at every layer.
Capture session context for seamless continuity. Use when the user says "handoff", "wrap up", "end session", "pass the baton", "save progress", or needs to preserve working state for the next session.
Adversarial code review that iterates to convergence. Use when the user says "hostile review", "adversarial review", "tear this apart", "find all issues", or needs a thorough skeptical review of code or design.
Convert analysis results or review findings into actionable implementation plans. Use when the user says "turn insights into a plan", "prioritize findings", "action items from review", or has unstructured observations that need to become executable tasks.
| name | merge-planner |
| description | Classify PRs and produce a priority-ordered merge plan. Use when the user says "merge order", "which PR first", "merge plan", or has multiple PRs targeting the same branch that need sequencing. |
Use this skill when multiple PRs target the same branch and you need to decide merge order, or when a PR has complex dependencies that affect merge safety. The goal is to classify PRs and produce a priority-ordered merge plan.
Merging PRs in the wrong order causes unnecessary conflicts, broken CI, and wasted rebase cycles. This skill provides a structured approach to classifying PRs by type, scoring their priority, and determining a safe merge sequence.
gh CLI for fetching PR metadata and CI statusClassify each PR by type. Read the diff summary and labels for each PR. Assign one type:
Score priority across dimensions. For each non-blocked PR, assess these dimensions:
Determine merge order. Sort PRs by: accelerators first (they clear the queue), then normal PRs by priority score descending. For ties, prefer the older PR. List blocked PRs last with their blocking reason.
Check for base branch conflicts. For the top-priority PR, verify it can merge cleanly into the target branch. If conflicts exist, note which files conflict and whether a rebase is needed before merge.
Output the merge plan. Present the ordered list with: PR number, title, type, priority score, and any action required (merge, rebase first, or blocked — fix X).
A merge plan containing: