菜单
Generates a Merge Request (MR) message based on a specified target branch. Trigger this skill when the user asks to create an MR message or pull request description.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ikr4-m/dotfiles --skill git-create-mr-message命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
A fast, low-friction execution skill that bypasses heavy planning phases to immediately patch linter errors, syntax issues, or stack traces. Triggered by saying "/auto-fix" or pasting an error log. It finds the file, applies the minimal fix, and stops for human review.
Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.
Enforces a strict planning phase before execution. For complex tasks, it triggers a 'grill-me' style Q&A and generates an implementation plan using Ponytail discipline (lazy-senior principles) and YAGNI. For simple tasks, it skips heavy planning.
| name | git-create-mr-message |
| description | Generates a Merge Request (MR) message based on a specified target branch. Trigger this skill when the user asks to create an MR message or pull request description. |
The title of merge request must using The Conventional Commits.
<desc_and_the_summary>
# Changes
<foreach changes>
## <changes_title>
<map of bullet_list_of_changes = {
- **<title>**: <desc> <if changes = breaking>**[BREAKING]**<endif>
}>
<endforeach>
<if have breaking_changes>
# Breaking Changes
<endif>
<if have migration>
# Migration
<bullet_list_of_migration>
<endif>