Systematic code review checklist and pre-commit quality gates for PRs. Use when: reviewing pull requests, checking code quality, before committing code. Keywords: review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
This skill provides systematic checklists for code review and pre-commit verification.
| Prefix | Meaning | Action Required |
|---|---|---|
| ❗ BLOCKING | Must fix before merge | 🔴 Required |
| ⚠️ IMPORTANT | Should fix, but not blocking | 🟡 Recommended |
| 💡 SUGGESTION | Nice-to-have improvement | 🟢 Optional |
| ❓ QUESTION | Need clarification | 🔵 Discuss |
| 📝 NOTE | Informational, no action | ⚪ Informational |
For complete standards, see:
❗ BLOCKING: Potential SQL injection vulnerability here.
Please use parameterized queries instead of string concatenation.
⚠️ IMPORTANT: This method is doing too much (120 lines).
Consider extracting validation logic to a separate method.
💡 SUGGESTION: Consider using a Map here instead of an array for O(1) lookup.
❓ QUESTION: Why are we using setTimeout here instead of async/await?
📝 NOTE: This is a clever solution! Nice use of reduce here.
This skill supports project-specific configuration.
CONTRIBUTING.md for "Disabled Skills" section
CONTRIBUTING.md for "Code Review Language" sectionIf no configuration found and context is unclear:
CONTRIBUTING.md:## Code Review Language
This project uses **[chosen option]** for code review comments.
<!-- Options: English | 中文 -->
In project's CONTRIBUTING.md:
## Code Review Language
This project uses **English** for code review comments.
<!-- Options: English | 中文 -->
### Comment Prefixes
BLOCKING, IMPORTANT, SUGGESTION, QUESTION, NOTE
License: CC BY 4.0 | Source: universal-dev-standards
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Prevent AI hallucination and ensure evidence-based responses when analyzing code or making suggestions. Use when: analyzing code, making recommendations, providing options, or when user asks about confidence/certainty. Keywords: certainty, assumption, inference, evidence, source, 確定性, 推測, 假設, 來源, 證據.
The English summary is being prepared. Showing the original description.
Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, 提交, 訊息, feat, fix, refactor.
The English summary is being prepared. Showing the original description.
Guide documentation structure, README content, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup. Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, 文件, 說明文件.
The English summary is being prepared. Showing the original description.
Guide Git branching strategies, branch naming, and merge operations. Use when: creating branches, merging, pull requests, Git workflow questions. Keywords: branch, merge, PR, pull request, GitFlow, GitHub Flow, 分支, 合併, 工作流程.
The English summary is being prepared. Showing the original description.
Semantic versioning and changelog formatting for software releases. Use when: preparing releases, updating version numbers, writing changelogs. Keywords: version, release, changelog, semver, major, minor, patch, 版本, 發布, 變更日誌.
The English summary is being prepared. Showing the original description.
Guide requirement writing, user story creation, and feature specification. Use when: writing requirements, user stories, issues, feature planning. Keywords: requirement, user story, issue, feature, specification, 需求, 功能規劃, 規格.
The English summary is being prepared. Showing the original description.