Agent Skills
› pydantic/monty
› review-general
review-general
GitHub用于在合并前对分支或PR进行通用代码审查,检查Bug、CPython差异、沙箱逃逸、资源限制、性能回归及注释规范,并生成简洁的缺陷报告。
Trigger Scenarios
需要对新分支或PR进行合并前审查
用户请求检查代码中的逻辑错误、安全漏洞或性能问题
Install
npx skills add pydantic/monty --skill review-general -g -y
SKILL.md
Frontmatter
{
"name": "review-general",
"description": "Review the current branch against its merge base for bugs, CPython divergence, sandbox escapes, resource-limit escapes, performance regressions, verbose comments and missing .\/limitations\/ updates. Use for a general pre-merge review of a branch or PR."
}
General branch review
git diff --stat origin/main...HEAD # scope first
git diff origin/main...HEAD
Read the changed files in full — a hunk is rarely enough to judge correctness. Look for:
- Bugs — logic errors,
DropWithContextvalues not released on every exit path (the fix isdefer_drop!/DropGuard, not moredrop_withcalls), borrow/aliasing mistakes, unhandled error paths. - CPython divergence — different results, exception types or messages, missing
attributes. Check anything you're unsure of with
python-playground. - Sandbox escapes — sandboxed code reaching the host filesystem, environment, network or subprocesses.
- Resource-limit escapes — allocations not charged to the tracker (an unbounded or
amplifying
Stringbuild withoutStringBuilder), unbounded loops, recursion without a depth guard. - Performance — regressions the branch introduces, and improvements you spot.
- Verbose comments — docstrings and comments should be concise as per
CLAUDE.md. - Cleanups — duplication, misplaced logic, functions grown too complex.
./limitations/— a new divergence with no entry is a finding.
Report
Concise, most severe first. Per finding: file:line, what's wrong, the concrete failure
it causes. Don't pad with what the branch got right.
Report only, unless the user asks for fixes.
Version History
- 026b383 Current 2026-08-20 09:39


