Self-review discipline for in-conversation use — apply before declaring code complete or before committing. Walks correctness, security, maintainability, and convention checks at the time of writing. For focused review of a large diff in a fresh context, delegate to the code-reviewer agent.
Code Review Rule. Use this rule when you need expert code review for quality, security, and maintainability. This rule should be used proactively after writing logical chunks of code, before merging pull requests, or when explicitly asked to review code. Example: After implementing a new feature in a Go plugin, use this rule to review the code for potential issues. Example: When asked '请对 PR 1234 进行代码评审', 'Code Review fork/feature/x', '将 fork/feature/x 对比 main 进行CR' use this rule to perform a thorough security-focused review.
2.2k4mo agoReviewMountCreate a free account to mount
Self-review security discipline applied while writing — walk the threat model of the change (untrusted input, authz, secrets, crypto, dependencies) before handing it off. Invoke before declaring security-relevant code complete or committing it. The in-conversation companion to the security-reviewer agent; for a focused pass on a large diff in fresh context, delegate to that agent.
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
224mo agoReviewMountCreate a free account to mount
Use Assumption Checkpoint when diagnosing bugs, changing code, reviewing code, explaining unfamiliar code, making implementation decisions, or calling work complete.
Blunt, factual code review. No sugar coating. Finds bugs, security issues, performance problems, and architecture flaws. Use when user says /codereview or asks to review code.
Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes. The reviewer has no shared state with the coding agent and gives a genuine second opinion. Use after audit-code passes, before committing, or when user wants an independent code review.
2742mo agoReviewMountCreate a free account to mount
Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.
3k16mo agoReviewMountCreate a free account to mount
Use when reviewing code that touches the database or persistence layer. Covers index strategy, query count, N+1, transaction scope, migration safety, and connection pooling. Load instead of the general code-review skill for DB-focused reviews.
Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.
2.1k9mo agoReviewMountCreate a free account to mount
Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.
1.7k15mo agoReviewMountCreate a free account to mount
Review uncommitted or branch-local changes for defects, ranked by severity, with a concrete failure scenario behind every finding. Use when asked to review code, review a diff, review my changes, check this before I commit, look over this branch, or do a pre-PR pass. Reviews the change, not the whole repository.
Open Code Review - AI code quality gate for detecting hallucinated packages, stale APIs, context breaks, security anti-patterns, and over-engineering in AI-generated code.
378mo agoReviewMountCreate a free account to mount