better-coding-review
在合并前捕获高价值问题，提高代码质量。
结构化地审查代码与 PR，查找错误、安全与可维护性问题的守门人。
用结构化流程做只读代码审查，重点抓 bug、安全漏洞和可维护性问题，输出可复用且可核验的报告而不改动源码。适合在看 diff、PR 或合并前的质量把关时启用，流程先验收规格合规再评估代码质量。发现按 CRITICAL/MAJOR/MINOR/NIT 分级，每条给出文件:行号、问题、为什么以及修复建议，方便落地修复。
▸ 展开 SKILL.md 英文原文
Review code, diffs, and pull requests for bugs, security issues, and maintainability problems before merge — read-only, any language, any repo. MUST be used whenever code is reviewed, a diff or PR is checked, or pre-merge quality is in question — even if the user does not explicitly say review. Two-stage (spec compliance first, then code quality), three-pass, severity-tagged (CRITICAL/MAJOR/MINOR/NIT); every finding reported as file:line + problem + why + fix, verified against source. Reports only, never modifies files. Not for whole-repo health checks — that is the audit skill. Trigger: /better-coding-review
帮我安装这个 skill：https://raw.githubusercontent.com/janschachtschabel/better-coding-skills/main/skills/better-coding-review/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/janschachtschabel/better-coding-skills/main/skills/better-coding-review/SKILL.md"# Better Coding Review Structured, read-only code review designed to counter the failure modes that make reviews inconsistent: ad-hoc every-time checks, findings that vary session to session, unverified nitpicks, and blocking on style a linter should own. **Primary objective:** catch bugs, security issues, and maintainability problems with a repeatable process and a fixed output format — the *same* checks in the *same* order producing the *same* shape of findings, so nothing important is skipped because attention drifted. Two review stages: spec compliance first (does the code do what was asked?), code quality second (is it well-built?). --- ## Activation Begin the first response after