菜单
Review code changes for correctness, security, project conventions, and maintainability. Use when reviewing a diff, before commit, or when the user asks for a code review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Short-lived feature branches only — never commit on main; merge then push. TDD + lint + npm run ci as exit criteria before commit on the branch. Do not default to asking the user to open a PR. Use when implementing a feature or non-trivial fix, when the user asks for branch/git workflow, or after substantial edits that should not stay uncommitted.
Creates and edits project documentation for both public and internal audiences. Use when writing or updating README.md, AGENT_HANDOFF (or AGENTS.md), CONTRIBUTING, or internal docs (e.g. PM_PLAN, DEV_GUIDE, TEST_TDD, DESIGN_SYSTEM). Covers structure, tone, and what to include for each doc type.
Manifest V3 Chromium/Edge extension engineering for this repo: ephemeral service workers, chrome.storage rehydration, chrome.alarms, message passing (sendMessage, onMessage + sendResponse), extension context invalidation in content scripts, idle-first-message failures, and overlay/background wiring. Use when editing manifest.json, src/background/, src/content/page-overlay.ts, messaging, or when the user mentions MV3, service worker sleep, idle resume, Extension context invalidated, sendMessage, or runtime.connect.
Change-aware quality pass: diff scope, readability, function size and control flow, comments where non-obvious, and alignment with ESLint tiers in eslint.config.mjs. Use before merge or with handoff when the user wants industry-style maintainability beyond what tests assert.
Shapes extension-wide architecture for this repo: boundaries between background, content scripts, and UI surfaces; composition with existing overlays; storage and messaging contracts; feature flags and permissions rationale. Use when designing a new epic, splitting work across layers, reviewing structural risk, or when the user asks for an extension architect, system design for the extension, or how features should be layered in MV3.
Technical leadership for this repo: turn plans into sequenced work, clarify definition of done, surface risks and dependencies, align tests and CI with scope, and coordinate cross-cutting changes (storage, messaging, UI). Use when the user asks for a tech lead, implementation plan, story breakdown, risk assessment before a large change, or merge ordering across epics.
| name | code-reviewer |
| description | Review code changes for correctness, security, project conventions, and maintainability. Use when reviewing a diff, before commit, or when the user asks for a code review. |
Use this skill when performing a code review: before commit, on a diff, or when the user asks "review this." Focus on actionable feedback with line references and concrete fixes.
main. Session handoffs are local (HANDOFF-*.md gitignored). Update AGENT_HANDOFF only when process/commands change; use techwriter when editing docs.| Area | Check |
|---|---|
| Correctness | Logic correct; null/empty/edge cases handled. |
| Secrets & data | No API keys or secrets in repo; no sensitive data logged. |
| Conventions | Matches DEV_GUIDE; tests present for new behavior. |
| Tests | Project test suite green (or skip documented). |
| Docs | Plan / PM_PLAN updated if contract or scope changed; AGENT_HANDOFF if process changed; local session notes optional. |
| Maintainability | Clear names; functions testable and understandable; npm run lint clean. |
npm run lint / npm run format:check / npm run ci enforce eslint.config.mjs and Prettier — unused bindings, console usage, cyclomatic complexity and function length by folder, plus consistent formatting. Fix violations; avoid blanket eslint-disable unless the exception is justified in the same change..cursor/skills/code-quality-gate/SKILL.md).