review
Simple and generic code review.
- License 许可
- MIT
- 最近更新
- 2026-10-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- review
- description
- Simple and generic code review.
- argument-hint
- the last commit
- disallowed-tools
- Edit Write NotebookEdit
- disable-model-invocation
- true
03 SKILL.md 正文
Please review $ARGUMENTS Search for and identify any error, bug, inconsistency, or dead code. If no target given: review the uncommitted diff - if the tree is clean, review the current branch compared to main.
Then, report to the user with, for each finding, the following information:
- A short, simple, and easy to understand summary of the issue (don't be technical here),
- The impact of the issue,
- A description of the issue, including context and root causes,
- One or more suggested fix, including potential side effects or limitations.
Your objective is for the reader to gain a good understanding of the findings, whatever his/her expert level.
- Start with high level explanations, then go into finer details.
- Be clear, precise and concise. Don't say anything false (factually or implicitly) for the sake of simplification.
- Add examples when applicable.
Constraints:
- Ground your review in the actual code — read the relevant files, run tests when applicable, do NOT speculate.
- No findings is a valid, good outcome — don't invent issues to have something to report.
- Do NOT change anything unless asked explicitly.
04 同仓库更多 Skills
sharpen-language
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (LANGUAGE.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
security-review
Runs a multi-agent workflow to analyze the security of a project or repository with different lenses. Use when the user wants a thorough multi-angle security review for a feature, refactor, or piece of code, e.g. "review the security of this code base", "perform a security audit of the current application", etc.
release-notes
Generate release notes for a new version. Use when the user asks for a changelog, release notes, or a formatted summary of changes in a repository.
python-tdd
Drive a change through tight RED → GREEN → REFACTOR cycles using pytest. One failing test, then minimal code to pass, then refactor. Use when coding in python and the user asks for "TDD" ("Test Driven Development"), says "test-first", or wants new behavior added behavior-by-behavior rather than upfront.
js-tdd
Test-driven development for JavaScript and TypeScript. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
implement
Simple and generic plan implementation.