requesting-code-review
Use when completing a task, finishing a major feature, preparing to merge, or needing an independent implementation review.
- License 许可
- MIT
- 所属仓库
- max-kharena/nous
- 最近更新
- 2026-04-28
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- requesting-code-review
- risk
- medium
- type
- review
- version
- 0.1.0
- description
- Use when completing a task, finishing a major feature, preparing to merge, or needing an independent implementation review.
03 SKILL.md 正文
Requesting Code Review
Core Principle
Review the work product, not the session history. Give the reviewer exact scope, requirements, and diff range.
When Review Is Required
- Before merge or PR.
- After a major feature or risky refactor.
- After each task in subagent-driven development.
- When implementation concerns remain unresolved.
Review Context Template
Provide:
- What was implemented.
- Plan or requirements excerpt.
- Base SHA and head SHA, or explicit file list if git is unavailable.
- Known risks or tradeoffs.
- Verification already run.
Reviewer Focus
- Correctness against plan.
- Missing edge cases.
- Error handling and user-visible failure modes.
- Test coverage and regression risk.
- Maintainability and unnecessary complexity.
Handling Feedback
- Fix Critical issues immediately.
- Fix Important issues before continuing.
- Track Suggestions separately.
- Push back only with evidence.
Output Contract
## Review Scope
## Diff Range
## Requirements
## Verification Already Run
## Reviewer Instructions
04 同仓库更多 Skills
write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when the user wants to create, write, or build a new skill.
verification-before-completion
Use when about to claim work is complete, fixed, passing, ready, merged, shippable, reviewed, or verified.
using-nous
Use when a request needs NOUS command routing or personality-driven planning.
using-git-worktrees
Use when NOUS execution needs isolated implementation branches, phase worktrees, parallel worktrees, or safe branch setup before executing a plan.
ubiquitous-language
Use when the user wants to define domain terms, build a glossary, harden terminology, or extract a DDD-style ubiquitous language. Saves to UBIQUITOUS_LANGUAGE.md.
triage-issue
Use when the user reports a bug and wants it investigated and filed as a durable GitHub issue with a TDD-based fix plan.