musepi-contributing skillA
musepi-contributing is agent-read markdown (skill) from muselinn/musepi: MusePi 仓库提交规范助手——帮用户按项目模板与 CONTRIBUTING 规范起草/提交 GitHub issue、pull request、commit message 与 changelog，以及跑 release 流程。触发：用户要"提 issue/PR"、"写 PR body"、"提交代码"、"commit 规范"、"发版/release"、或询问仓库贡献流程。.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# MusePi 贡献与提交规范
本 skill 汇总 MusePi 仓库（`MuseLinn/MusePi`）的 issue / PR / commit /
release 模板与硬性规范，供 agent 代表用户起草与执行提交流程。所有内容以仓库
实际文件为准，动手前先读对应模板，不要凭记忆编造。
## 模板位置（先读再写）
| 用途 | 文件 |
|---|---|
| PR 模板 | `.github/PULL_REQUEST_TEMPLATE.md` |
| Bug / Feature / Question issue | `.github/ISSUE_TEMPLATE/{bug_report.yml, feature_request.yml, question.yml, config.yml}` |
| 贡献总规范 | `CONTRIBUTING.md` |
| 变更记录 | `packages/coding-agent/CHANGELOG.musepi.md`（musepi 双语版，启动"新功能"面板 + `/changelog` 数据源；有 `[Unreleased]` 段待填） |
| 发布脚本 | `scripts/release.ts` |
## 硬性规范（违反即被拒/失礼）
1. **PR body 必须包含用户本人写的一句话**（解释改了什么、为什么）——生成的
摘要/粘贴的 agent 记录/纯 checklist 都不满足。提交前向用户要这一句。
2. **PR 三段式 + checklist**：`## What` / `## Why`（关联 issue 用 `fixes #N`）/
`## Testing`；勾选 `bun check` 通过、本地实测、用户可见变更更新 CHANGELOG。
3. **不要为即将自己实现的工作开 issue**——维护者可能并行抢做。
4. **major/跨包改动先讨论**（Discord/issue），不要直接大 PR。
5. **AI 辅助提交四约束**：限范围拒绝无关改动、逐文件 review 并理解行为、
自己跑相关 check 与行为验证、**由用户发布**（agent 不自主任 push/发布）。
6. **Issue 模板字段**：Bug 必填 Description / Steps / Expected / Platform
（含 Windows native）/ **MusePi version**（`musepi --version` 输出，非 omp）/
Bun version；Provider / Area 下拉选最贴近项。
## Commit 与 changelog 惯例
…Read the whole file at its exact version.
How to install
mdr add muselinn/musepi/musepi-contributing@git:20260908.1c958e3mdr add muselinn/musepi/musepi-contributing@sha256:cb4e3a4815a2837bPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_nwaf2q7ntoc6aakh)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4025 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
muselinn/musepi · 17 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nwaf2q7ntoc6aakh GET https://markdownregistry.com/api/v1/resolve?ref=muselinn/musepi/musepi-contributing GET https://markdownregistry.com/api/v1/blob/cb4e3a4815a2837baf0ef2bc4d42e4ce8bb67dc20382ea7e2a14b7213c30c202
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.