Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Build a PR body from its commits, the linked issue, and the repo's PR template.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"prbody": {
"command": "npx",
"args": [
"-y",
"@reneturcios/prbody",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add prbody -- npx -y @reneturcios/prbody mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"prbody": {
"command": "npx",
"args": [
"-y",
"@reneturcios/prbody",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"prbody": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/prbody",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Every repo has a PR template, and every PR author fills it in differently — or pastes over it, or leaves the headings empty. prbody takes the mechanical part out of the author's hands: you hand it the template, the PR's commits, and the issue it closes, and it hands back the body with the template's placeholders filled in, the same way every time.
Four placeholders are pinned, spelled exactly like this:
- .- ( ), where is the first 7 characters of the commit's hash (the whole hash when it is shorter than 7).Closes # when an issue number is supplied, or the empty string when it is not.Every occurrence of each known placeholder is replaced. Any other {{...}} span — anything from {{ to the next }} — is left in the body exactly as written, and its inner name, trimmed of surrounding whitespace, is reported in unfilled_placeholders (distinct, sorted ascending), so a template asking for something prbody does not know about is visible instead of silently dropped. A {{ with no later }} is not a placeholder at all: it is left untouched and unreported. Replacement text is never rescanned, so a {{...}} sequence that arrives inside a title or a commit subject stays literal.
The result also reports commit_count (the number of commits) and closes_issue (true exactly when an issue number was supplied). Malformed input — a missing, empty, or non-string template; commits missing, not an array, or empty; a commit entry that is not an object or whose hash or subject is missing, empty, or non-string; an issue_number that is not an integer of at least 1; or a title that is empty or non-string when present — is a validation error naming the offending path (for example commits[1].subject must be a non-empty string), with no partial result. Unknown extra fields are ignored, including extra fields inside commit entries. The computation is pure and local: no network, no configuration, and no repository is read or touched — prbody only fills the template it is given.
npx @reneturcios/prbody build --input args.json
npx @reneturcios/prbody --version
args.json contains the full arguments object:
{
"template": "## {{title}}\n\n### Commits\n{{commits}}\n\n{{issue_link}}", "commits": [ { "hash": "abc1234def5678", "subject": "Add login form" }, { "hash": "9876fedcba4321", "subject": "Fix redirect loop" } ], "issue_number": 42, "title": "Login rework" }
The result is printed as JSON:
{
"body": "## Login rework\n\n### Commits\n- Add login form (abc1234)\n- Fix redirect loop (9876fed)\n\nCloses #42", "unfilled_placeholders": [], "commit_count": 2, "closes_issue": true }
Exit codes: 0 on success, 1 on a runtime error (including an unreadable or invalid input file, or invalid input), 2 on a usage error.
npx -y @reneturcios/prbody mcp
MCP client config:
{
"mcpServers": { "prbody": { "command": "npx", "args": ["-y", "@reneturcios/prbody", "mcp"] } } }
build_pr_body — Build a pull request body by filling the repo's PR template with the PR title, a summary of its commits, the full commit list, and the closing line for its linked issue.template (string, required, non-empty) — the repo's PR template text, with {{...}} placeholderscommits (array, required, non-empty) — commits of the PR, oldest first; each entry is an object with hash (string, required, non-empty) and subject (string, required, non-empty)issue_number (integer, optional, at least 1) — the linked issue numbertitle (string, optional, non-empty when present) — the pull request titleReturns {body, unfilled_placeholders, commit_count, closes_issue}.
docker run -i ghcr.io/cloudcorprecords/prbody
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/prbody build --input /w/args.json
npm install
npm run build # tsc -> dist/ npm test # tsx --test test/*.test.ts (pure local, no network) npm run dev # run the CLI from source
MIT — Copyright (c) 2026 Rene Turcios