菜单
Writes high-quality pull request descriptions. Use when creating a PR, summarizing branch changes, or when the user asks for a PR description.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Runs a fresh diagnostic pass on one MonÉlu project axis - inspects the current code (not old reports), writes a dated report to notes/dispatch/, updates the diagnostic roadmap, and files new findings as labeled Linear issues after deduping against the open backlog. No code changes. Use as /diagnose <axis> or /diagnose next to pick the stalest axis.
Resolves a Linear (MonElu) issue end-to-end - reads the MON issue, branches on its gitBranchName, implements, verifies, opens a PR, updates Linear, watches CI, runs pr-review and applies the fixes. Stops before merge. Use as /solve-mon <MON-id> (e.g. /solve-mon MON-75) or /solve-mon next to auto-pick the top unblocked non-epic backlog issue (WIP-limited to 3 open PRs). Replaces the retired solve-axis skill.
Decomposes a large Linear (MonElu) issue into ordered, solve-mon-sized sub-issues - explores the codebase to ground the plan, drafts sub-issues with Scope and Acceptance criteria, flags architectural decisions for the ADR first, and creates them in Linear under the parent. Use as /plan-epic <MON-id>, e.g. /plan-epic MON-91.
Reviews a branch or pull request like a careful reviewer before or during code review. Use when the user asks for a PR review, review readiness check, or wants feedback before merging.
Reviews a branch or pull request like a careful reviewer before or during code review. Use when the user asks for a PR review, review readiness check, or wants feedback before merging.
PO assistant for MonÉlu — keeps Linear in sync with git state, auto-detects what issue is being worked on from the current branch/diff, and drafts well-structured backlog issues from free-text descriptions. Three modes: sync (default), detect, fill.
| name | pr-description |
| description | Writes high-quality pull request descriptions. Use when creating a PR, summarizing branch changes, or when the user asks for a PR description. |
This skill writes the PR description body only. For the full PR creation workflow (opening, updating, saving to notes/prs/), use the pr-create skill instead.
When writing a PR description:
Identify the correct base branch before diffing.
master.Review the change set before writing.
git diff <base>...HEAD to inspect all branch changes.git diff --stat <base>...HEAD for a concise summary.Check whether documentation needs updating.
README.md only if user-facing behavior, setup, usage, configuration, or examples changed.CLAUDE.md only if workflow instructions, repo conventions, or agent guidance changed.Use this structure:
One or two sentences explaining what this PR changes.
Brief context on the problem, goal, or motivation behind the change.
None if there are no breaking changesKeep the description concise but useful.
If the branch changes are unclear or mixed, first infer the main objective of the PR and organize the description around that objective.