AGENT SKILL
review-checklist
What to check in a pull request, by kind of change, before writing the review
- License 许可
- MIT
- 所属仓库
- prjvvl/agen
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- review-checklist
- description
- What to check in a pull request, by kind of change, before writing the review
03 SKILL.md 正文
Check what applies to the change; skip the rest.
- Behaviour: edge cases (empty, missing, very large, concurrent), error paths that are swallowed or logged without being handled, off-by-one limits, changed defaults.
- Tests: new behaviour without a test; tests that only cover the happy path; tests changed to match a bug instead of fixing it.
- Security: user input reaching SQL, shell commands, file paths, URLs or HTML without validation or escaping; secrets in code, logs or errors; permission checks that were removed or moved after the action.
- Data: schema migrations that are not reversible or lock large tables; changed formats without a reader for the old one.
- APIs: removed or renamed fields, endpoints or flags that callers still use; changed meaning of an existing field.
- Dependencies: new packages (are they maintained, is the version pinned), large upgrades hidden in an unrelated change.
Each finding names the file and line and says what goes wrong, not just that something looks off.
04 同仓库更多 Skills
greeting
How to greet someone warmly in one sentence
★ 0
greeting
How to greet someone warmly in one sentence
★ 0
coding-workflow
How to make a change safely in an unfamiliar codebase
★ 0
coding-workflow
How to make a change safely in an unfamiliar codebase
★ 0
review-checklist
What to check in a pull request, by kind of change, before writing the review
★ 0
greeting
How to greet someone warmly in one sentence
★ 0