Approvepath

io.github.CloudCorpRecords由 GitHub 帳號 CloudCorpRecords 發布v0.1.0更新於 Nov 3, 2026

梳理誰必須核准 PR:CODEOWNERS 規則以及實際審查這些檔案的人。

AI 翻譯由 AI 模型根據下方的原文描述翻譯,可能有誤。

原文描述

Map who must approve a PR: CODEOWNERS rules plus who actually reviews these files.

已驗證STDIO僅桌面

概覽

Approvepath 的本機 MCP 服務;無需登入;STDIO。

暫無 AI 概覽:以下資訊來自註冊中心條目和服務本身。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Approvepath,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

approvepath

A CODEOWNERS file says who is supposed to approve a change. Review history says who actually shows up. approvepath puts the two side by side for one pull request: you hand it the CODEOWNERS rules, the files the PR touches, and whatever past review activity you have, and it hands back, per file, the owners the rules assign and the people who have reviewed that exact file before.

Pattern matching follows a pinned subset of CODEOWNERS semantics, so the answer never depends on which CODEOWNERS dialect you had in mind. Any leading / is stripped from both the pattern and the file path before comparing. A pattern ending in / is a directory prefix: it matches every file under that directory. A pattern containing * is a glob that must match the whole path — ** matches any run of characters including /, while a single * matches any run except /. Any other pattern matches a file that equals it exactly, or a file underneath it (the pattern plus / as a prefix), so a bare directory name owns its whole subtree.

When several rules match the same file, the last matching rule in file order wins — the same override rule CODEOWNERS itself uses, and the reason a broad early rule can hand a subtree to a team while a later, narrower rule hands one corner of it back. A file no rule matches is unowned: its owners list is empty and its pattern is null, and it also appears in unowned_files, in input order.

Review history is counted plainly. For each changed file, frequent_reviewers counts, per reviewer, how many supplied review entries by that reviewer list the file exactly — no prefix credit, no directory credit. Reviewers are ranked by count descending, then by name ascending, and only the top three are reported. required_reviewers collects every owner from every winning rule across the PR, deduplicated and sorted, which is the shortest honest answer to "whose approval does this PR actually need?".

Everything is computed locally from the arguments alone: no repository is read, no hosting API is called, and nothing is guessed. Malformed input — a rule with an empty pattern, a changed file that is not a non-empty string, a review entry missing its reviewer — is a validation error naming the offending path, with no partial result.

CLI

bash
npx @reneturcios/approvepath map --input args.jsonnpx @reneturcios/approvepath --version

args.json contains the full arguments object:

json
{  "codeowners": [    { "pattern": "src/", "owners": ["@core"] },    { "pattern": "src/api/", "owners": ["@api-team", "sam"] }  ],  "changed_files": ["src/api/handler.ts", "README.md"],  "reviews": [    { "reviewer": "sam", "files": ["src/api/handler.ts"] },    { "reviewer": "lee", "files": ["src/api/handler.ts"] }  ]}

reviews is optional and defaults to []. The result is printed as JSON:

json
{  "files": [    {      "file": "src/api/handler.ts",      "owners": ["@api-team", "sam"],      "pattern": "src/api/",      "frequent_reviewers": [        { "reviewer": "lee", "reviews": 1 },        { "reviewer": "sam", "reviews": 1 }      ]    },    {      "file": "README.md",      "owners": [],      "pattern": null,      "frequent_reviewers": []    }  ],  "unowned_files": ["README.md"],  "required_reviewers": ["@api-team", "sam"]}

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.

MCP server

bash
npx -y @reneturcios/approvepath mcp

MCP client config:

json
{  "mcpServers": {    "approvepath": {      "command": "npx",      "args": ["-y", "@reneturcios/approvepath", "mcp"]    }  }}

Tools

  • map_approvals — Map the approval path for a pull request.

    • codeowners (array, required, may be empty) — CODEOWNERS rules in file order; each entry is {pattern, owners}, where pattern is a non-empty string and owners is an array of non-empty strings (may be empty)
    • changed_files (array of strings, required, non-empty) — paths of the files the PR changes
    • reviews (array, optional, default []) — past review activity; each entry is {reviewer, files}, where reviewer is a non-empty string and files is an array of strings (may be empty)

    Returns {files, unowned_files, required_reviewers}, where files holds one {file, owners, pattern, frequent_reviewers} entry per changed file, in input order.

Docker

bash
docker run -i ghcr.io/cloudcorprecords/approvepathdocker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/approvepath map --input /w/args.json

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # tsx --test test/*.test.ts (pure local, no network)npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios

來源:README.md,提交 511d783

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.0最新Nov 3, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分