菜单
Stage and commit working-tree changes as atomic, signed-off commits whose message length scales with the change. Use when asked to commit, stage, or finalize changes into git — after the user (not the agent) decides a diff is ready.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/OpenVisualCloud/Media-Transport-Library --skill mtl-commit命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Build MTL library, format code, and verify compilation. Use when asked to build, verify changes, check formatting, or prepare code for commit.
Author a new MTL test. Use when adding coverage for a bug fix, new feature, regression, or behavior change. Teaches how to pick the right tier (unit / integration / NoCtx / pytest single-host / pytest dual-host) and how to write a test that will survive review. Does NOT cover running existing tests, debugging an existing test failure, host setup, or build infrastructure — see the linked instructions for those.
| name | mtl-commit |
| description | Stage and commit working-tree changes as atomic, signed-off commits whose message length scales with the change. Use when asked to commit, stage, or finalize changes into git — after the user (not the agent) decides a diff is ready. |
Committing is the user's decision, never an agent's — only run this after being explicitly asked to commit.
git status --short and git diff --stat../format-coding.sh before staging anything. It runs
markdownlint (MD013 line-length among other rules, config at
.github/linters/.markdown-lint.yml)
alongside clang-format/isort/black/shfmt, and now fails the script
on any violation --fix cannot auto-correct — fix those by hand
(rewrap the paragraph; a single \n is a soft break, it doesn't
change rendering), then re-run until it exits clean.git add -p. Never bundle drive-by changes into an unrelated fix.git commit -s
immediately. Do not wait for approval; the user reviews git log
and reverts/amends if needed. Print the staged files and final message
after each commit.-s so a Signed-off-by: trailer is added.git push. Do not use --no-verify. Do not amend
commits that may already be pushed unless explicitly told to.<Type>: <subject>
<body — optional>
<footers — optional>
Feat, Add, Fix, Refactor, Docs, Test,
Perf, Build, Ci, Style. See doc/coding_standard.md.Fix(parser):)
or breaking markers (!). Flag a breaking API/behaviour change with a
BREAKING-CHANGE: footer instead.Fix: Reject zero-length frames in st20_tx_xmit — never Fix bug
or Update stuff.Include a body only when the change is not obvious from the diff.
Refs: #123,
See also: doc/foo.md) instead of summarising.Fix: state the symptom + root cause in one or two lines.Perf: include before/after numbers when measured.Blank line above; one per line; Token: value form.
Signed-off-by: Name <email> — added by -s.Fixes: <12-char SHA> ("<subject>") — recommended for bugfixes;
helps git bisect.Refs: #123 / Closes: #123.BREAKING-CHANGE: <description> — if not flagged with ! in the subject.I, we, the agent, the user,
per the discussion, as requested, Copilot, AI.Fix bug, Update X,
Misc cleanup).Fix needs symptom + root cause.Re-read the drafted message and verify:
If any answer is no, edit before running git commit -s.