code-review SKILL.md skillA
code-review from shumingyang-opencode/mattpocock-skills-zh-tw is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shumingyang-opencode/mattpocock-skills-zh-tw/code-review@git:20260806.5bfe60bPins git:20260806.5bfe60b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shumingyang-opencode/mattpocock-skills-zh-tw
- Path
skills/engineering/code-review/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260806.5bfe60b, committed Aug 6, 2026
- First version recorded
- Jul 1, 2026
- Size
- 6,682 bytes
- Repository stars
- 3
- License
- MIT
沿兩軸審查自某個固定點（commit、分支、標籤或合併基點）以來的變更——規範（軸）（程式碼是否符合此 repo 記錄的編碼規範？）與規格（軸）（程式碼是否符合原始 issue/規格的要求？）。以平行子代理執行兩種審查並排呈現。當使用者想審查分支、PR、進行中的變更，或說「review since X」時使用。.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
對 `HEAD` 與使用者提供的固定點之間的 diff 做雙軸審查： - **規範（軸）**——程式碼是否符合此 repo 記錄的編碼規範？ - **規格（軸）**——程式碼是否忠實實作原始 issue / 規格？ 兩個軸都以**平行子代理**執行，讓它們不污染彼此的上下文，然後本技能匯總它們的發現。 Issue 追蹤器應該已經提供給你——如果 `docs/agents/issue-tracker.md` 缺失，執行 `/setup-matt-pocock-skills`。 ## 流程 ### 1. 釘住固定點 無論使用者說的固定點是什麼——一個 commit SHA、分支名稱、標籤、`main`、`HEAD~5` 等。如果他們沒指定，就問。 把 diff 指令記下來一次：`git diff <fixed-point>...HEAD`（三點，這樣比較對象是合併基點）。也要用 `git log <fixed-point>..HEAD --oneline` 記下 commit 清單。 進一步之前，確認固定點能解析（`git rev-parse <fixed-point>`）而且 diff 非空。壞的 ref 或空的 diff 應該在這裡失敗——而不是在兩個平行子代理內部。 ### 2. 找出規格來源 依此順序尋找原始規格： 1. commit 訊息中的 issue 引用（`#123`、`Closes #45`、GitLab `!67` 等）——透過 `docs/agents/issue-tracker.md` 中的工作流程擷取。 2. 使用者以參數傳入的路徑。 3. `docs/`、`specs/` 或 `.scratch/` 下符合分支名稱或功能的規格檔。 4. 如果什麼都沒找到，問使用者規格在哪。如果他們說沒有，**規格**子代理會跳過並回報「no spec available」。 ### 3. 找出規範來源 repo 中任何記錄程式碼應如何撰寫的東西，例如 `CODING_STANDARDS.md` 或 `CONTRIBUTING.md`。 在 repo 記錄的任何東西之上，規範軸永遠攜帶下面這份**壞味道基線**——一組固定的 Fowler 壞味道（_Refactoring_，第 3 章），即使 repo 什麼都沒記錄也適用。兩條規則綁定它： - **repo 優先。** 記錄在案的 repo 標準永遠勝出；當它背書基線會標記的某個東西時，抑制該壞味道。 - **永遠是判斷。** 每個壞味道都是帶標籤的啟發式（「可能是 Feature Envy」），從來不是硬性違規——而且像這裡的任何標準一樣，跳過任何工具已經強制的東西。 每個壞味道讀成*它是什麼* → *如何修*；把它對上 diff： …
Read the whole file at its exact version.
How to install
mdr add shumingyang-opencode/mattpocock-skills-zh-tw/code-review@sha256:e679b421e4703661The line at the top of this page pins the label git:20260806.5bfe60b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jhloyn6mg6ecerxk)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 1, 2026 and Aug 6, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260806.5bfe60b latest | 2026-08-06 | 5bfe60b | 6,682 B | A | view · diff |
| git:20260803.a2f9333 | 2026-08-03 | a2f9333 | 6,731 B | A | view · diff |
| git:20260701.14c13c5 | 2026-07-01 | 14c13c5 | 6,740 B | A | view |
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 (6682 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
shumingyang-opencode/mattpocock-skills-zh-tw · 3 stars · license MIT · pushed 2026-10-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jhloyn6mg6ecerxk GET https://markdownregistry.com/api/v1/resolve?ref=shumingyang-opencode/mattpocock-skills-zh-tw/code-review GET https://markdownregistry.com/api/v1/blob/e679b421e470366182899a4a0d4ad1de11ba6b20b61f072d4a3cc138d9316f1d
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from shumingyang-opencode/mattpocock-skills-zh-tw
Every file in shumingyang-opencode/mattpocock-skills-zh-tw