review-code-l9
Performs an 8-dimension L9-compliant code review on a diff, file, or PR. Use when: reviewing a PR, auditing new code, validating an implementation against spec, checking a diff before merge. Do NOT use when: non-code review tasks (use a different skill). Signals: review code, review PR, code review, diff review, check implementation, audit code, validate against spec, L9 review
- License 许可
- MIT
- 最近更新
- 2026-11-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- review-code-l9
- license
- MIT
- metadata
- { "tags": [ "code-review", "quality", "L9", "governance" ], "author": "Igor Beylin", "version": "1.0.0", "eval-status": "untested", "last-tested": 1781654400000, "model-target": "claude-sonnet-4" }
- description
- Performs an 8-dimension L9-compliant code review on a diff, file, or PR. Use when: reviewing a PR, auditing new code, validating an implementation against spec, checking a diff before merge. Do NOT use when: non-code review tasks (use a different skill). Signals: review code, review PR, code review, diff review, check implementation, audit code, validate against spec, L9 review
- compatibility
- Tested: Claude Code, Claude Sonnet 4+ Kernel alignment: - agent_review_kernel.v1 - sandbox_isolation_kernel.v1
03 SKILL.md 正文
review-code-l9
Overview
8-dimension review covering: correctness, security, observability, test coverage, L9 doctrine compliance, performance, maintainability, and blast radius. Produces a structured findings table and a VERDICT: APPROVE / REQUEST_CHANGES / BLOCK.
When to Use
Signals: diff present, PR link provided, user says "review", "check this code", "validate implementation".
Workflow
- Load
agent_review_kernel.v1Tier 1 andsandbox_isolation_kernel.v1Tier 1 - Parse the diff/code into logical units
- Run 8-dimension review grid
- Classify each finding: BLOCK / REQUEST_CHANGES / SUGGEST / NOTE
- Emit findings table + verdict + top-3 required actions
Output Format
## L9 Code Review: <subject>
| Dimension | Status | Findings |
|-----------|--------|----------|
| Correctness | PASS / FAIL | ... |
| Security | ... | ... |
| Observability | ... | ... |
| Test Coverage | ... | ... |
| L9 Doctrine | ... | ... |
| Performance | ... | ... |
| Maintainability | ... | ... |
| Blast Radius | ... | ... |
**VERDICT: APPROVE / REQUEST_CHANGES / BLOCK**
### Required Actions (if REQUEST_CHANGES or BLOCK)
1. ...
04 同仓库更多 Skills
optimize-kernel
Transforms any l9-ops kernel YAML into a doctrine-compliant three-tier progressive disclosure structure. Use when: auditing an existing kernel, running the optimize-kernel CI step, or onboarding a kernel from another source. Do NOT use when: authoring a brand-new kernel from scratch (use templates/kernel.yaml.template instead). Signals: optimize kernel, audit kernel compliance, apply doctrine, kernel drift, tier structure missing, trigger triad missing, rewrite kernel
generate-skill-md
Scaffolds a production-ready SKILL.md from a natural language description of the skill's purpose. Use when: authoring a new skill from scratch, onboarding an external skill into the l9-ops standard, generating skill structure from a requirements brief. Do NOT use when: modifying an existing skill (edit directly). Do NOT use when the description is too vague to produce a Trigger Triad. Signals: create skill, new skill, scaffold SKILL.md, write SKILL.md, add skill to library, skill template
generate-execution-plan
Creates a versioned, machine-readable YAML execution plan for multi-phase tasks. Use when: task spans 3+ files, multiple sessions, requires staged delivery, or needs a recoverable plan artifact. Do NOT use when: simple single-turn tasks that complete in one response. Signals: execution plan, multi-phase task, project plan, phased delivery, create plan, plan this work, staged execution, PLAN.yaml