Agent Skills › HashWarlock/nobody-plans-for-pi › nobody-requests-code-review

nobody-requests-code-review

GitHub

用于在任务完成、功能实现或合并前进行结构化代码审查，确保工作符合需求。包含自检清单、差异检查流程及严重程度分级，支持委托子代理审查，保障代码质量与安全。

skills/nobody-requests-code-review/SKILL.md HashWarlock/nobody-plans-for-pi

Trigger Scenarios

完成任务或实现重大功能后合并代码前验证

Install

npx skills add HashWarlock/nobody-plans-for-pi --skill nobody-requests-code-review -g -y

More Options

Use without installing

npx skills use HashWarlock/nobody-plans-for-pi@nobody-requests-code-review

指定 Agent (Claude Code)

npx skills add HashWarlock/nobody-plans-for-pi --skill nobody-requests-code-review -a claude-code -g -y

安装 repo 全部 skill

npx skills add HashWarlock/nobody-plans-for-pi --all -g -y

预览 repo 内 skill

npx skills add HashWarlock/nobody-plans-for-pi --list

SKILL.md

Frontmatter

{
    "name": "nobody-requests-code-review",
    "description": "Use when completing tasks, implementing major features, or before merging to verify work meets requirements"
}

Requesting Code Review

Overview

Before declaring work complete or merging, run a structured self-review or delegate to the reviewer subagent.

Announce at start: "I'm using the requesting-code-review skill to verify this work."

Pre-Review Checklist

Before requesting review, verify:

All tests pass (run them, don't assume)
No linting errors
Changes match the plan/spec
No debug code, commented-out code, or TODOs left behind
No unrelated changes mixed in
Commit messages are clear and descriptive
Edge cases handled

Self-Review Process

Read the diff — git diff main...HEAD (or appropriate base)
Check each file — Does every change serve the goal?
Look for —
- Hardcoded values that should be config
- Missing error handling
- Security issues (injection, auth bypass, secrets)
- Performance issues (N+1 queries, unbounded loops)
- Missing tests for new code paths
Verify requirements — Re-read spec, check each requirement is met

Delegated Review

Use the reviewer subagent for an independent perspective:

/review <scope of changes>

Or via the subagent tool directly:

Use reviewer agent to review: <description of what changed>

Severity Levels

Level	Action	Example
Critical	Must fix before merge	Security hole, data loss, crash
Warning	Should fix	Missing validation, poor error message
Suggestion	Consider	Better naming, minor refactor