code-review-and-quality
Skill8 starsChanged 3 days agoMITView on GitHub
Review a PR (pull request), branch or diff outside implement — runs the compliance, silent-failure, test and architecture lanes with full lane accounting.
84 other projects use a version of this.
Adopted by
Most recently taken up by
- zademy/lu-querytheir own version, first seen Nov 16, 2026
- sirius-cc-wu/sirius-skillstheir own version, first seen Nov 16, 2026
- tkbk-online/skillstheir own version, first seen Nov 15, 2026
- slantview/pi-agentstheir own version, first seen Nov 15, 2026
- addyosmani/agent-skillstheir own version, first seen Nov 14, 2026
- thistleknot/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use constraint-driven-development, observability-and-instrumentation and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 15 projects that use this
HK-hubSkillobservability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Also in 34 projects that use this
HK-hubSkilldeprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Also in 34 projects that use this
seikaikyoSkilldoubt-driven-development
對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
Also in 37 projects that use this
seikaikyoSkillinterview-me
需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。
Also in 37 projects that use this
JetBrainsSkillmodern-web-guidance
Search tool for modern web development best practices. MANDATORY: Execute FIRST for all HTML/CSS and clientside JS tasks. Do NOT skip — web APIs evolve rapidly and training weights contain obsolete patterns.
Also in 3 projects that use this
- +1 more from HK-hub
Other versions84 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 84
- addyosmani/agent-skills★ 118ksame name
- sanity-io/sanity★ 6.4ksame name
- ollaya-dev/ollaya★ 1.4ksame name
- SkafteNicki/dtu_mlops★ 806same name
- epam/ai-dial-chat★ 501same name
- shashankswe2020-ux/whoop-mcp★ 181same name
- muratgur/ordinus★ 111same name
- enes-alatas/spool★ 48same name
- vinvcn/addyosmani-agent-skills-zh★ 46same name
- jmxt3/gitscape.ai★ 33same name
74 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- batch-fixSkill
- brainstormingSkill
- code-simplificationSkill
- context-engineeringSkill
- fixSkill
- handoffSkill
- implementSkill
- incremental-implementationSkill
- instructionsSkill
- lessonsSkill
- mtk-doctorSkill
- mtk-setupSkill
- mtkSkill
- planning-and-task-breakdownSkill
- pre-commit-reviewSkill
- prior-work-checkSkill
- promote-lessonSkill
- repo-healthSkill
- research-contextSkill
- security-and-hardeningSkill
- setup-auditSkill
- setup-bootstrapSkill
- setup-refreshSkill
- spec-drift-detectionSkill
- spec-driven-developmentSkill
- subagent-implementationSkill
- tech-stack-dotnetSkill
- tech-stack-pythonSkill
- tech-stack-typescriptSkill
- verification-before-completionSkill
- workflow-artifactsSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 77 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Read .claude/references/implement-review-lanes.md and pick lanes from its Outside implement column: compliance-reviewer always.
“Common” is measured: kept by at least 6 in 10 of the 77 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Code Review And Quality
MTK File Resolution
Resolve MTK skill/reference/script paths per .claude/references/mtk-file-resolution.md unless the router already stated MTK_ROOT=<path> this session; CLAUDE.md, .claude/tech-stack, .claude/rules/, tasks/, docs/, .mtk/ stay project-relative.
Overview
Adversarial review of a PR or diff that did not come through implement (implement Phase 4 reads the reference directly). This skill is read-only except for workflow-artifact recording.
When To Use
- Reviewing a PR, branch, or local diff before merge, outside the implement loop
Workflow
- Get the diff (
gh pr diff <n>orgit diff <base>...HEAD) and the changed-file set; exclude files that were already dirty before the change. - Read
.claude/references/implement-review-lanes.mdand pick lanes from its Outside implement column:compliance-revieweralways;silent-failure-hunterwhen the trigger regex matches;test-reviewerwhen public behavior changed;architecture-revieweron a new slice, boundary, or cross-project call. - Dispatch them per Dispatch rules (inline when the Agent tool is unavailable) following the Review protocol (scripts via
$MTK_ROOT; no workflow artifact here, so skip review-input binding and say the review is unbound), run the Defect-class sweep on every confirmed finding, and apply Lane accounting before aggregating.finding-verifieris implement-only (HIGH/MAX). - Emit the findings table and fenced JSON per
.claude/references/review-finding-schema.md, with the lane roster. Write the push receipt only as the protocol's Receipt step qualifies (its--checkclause is implement-only).
Verification
- Every dispatched lane is accounted for; the verdict is not PASS while any lane abstained or returned nothing
- Findings follow the schema; an empty
findings[]carriesbelow_threshold_rationale
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

