编码规范、框架、重构、代码审查（1.8万 个）
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, 審查, 檢查, 簽入.
中文简介正在准备中。当前显示原文说明。
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
中文简介正在准备中。当前显示原文说明。
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
中文简介正在准备中。当前显示原文说明。
Validate at every layer data passes through to make bugs impossible
中文简介正在准备中。当前显示原文说明。
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
中文简介正在准备中。当前显示原文说明。
Systematically trace bugs backward through call stack to find original trigger
中文简介正在准备中。当前显示原文说明。
Create isolated git worktrees with smart directory selection and safety verification
中文简介正在准备中。当前显示原文说明。
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
中文简介正在准备中。当前显示原文说明。
Each routine does one thing and does it well - extract when routines have multiple responsibilities
中文简介正在准备中。当前显示原文说明。
Declare variables in smallest possible scope, initialize close to first use, minimize span and live time
中文简介正在准备中。当前显示原文说明。
Name code by what it does in the domain, not how it's implemented or its history
中文简介正在准备中。当前显示原文说明。
Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels
中文简介正在准备中。当前显示原文说明。
Check all external inputs for validity - garbage in, nothing out, never garbage out
中文简介正在准备中。当前显示原文说明。
Write comments explaining WHAT and WHY, never temporal context or history
中文简介正在准备中。当前显示原文说明。
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
中文简介正在准备中。当前显示原文说明。
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
中文简介正在准备中。当前显示原文说明。
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
中文简介正在准备中。当前显示原文说明。
Try 2-3 different approaches before implementing - don't settle for first design you think of
中文简介正在准备中。当前显示原文说明。
Run verification commands and confirm output before claiming success
中文简介正在准备中。当前显示原文说明。
Choose names that fully and accurately describe what the variable represents
中文简介正在准备中。当前显示原文说明。
Release a new version of an R package including version bumping, NEWS.md updates, git tagging, GitHub release creation, and post-release development version setup. Use when a package is ready for a new patch, minor, or major release, after CRAN acceptance to create the corresponding GitHub release, or when setting up the development version bump immediately after a release.
中文简介正在准备中。当前显示原文说明。
Multi-phase deep codebase review with severity ratings and structured output. Covers architecture, security, code quality, and UX/accessibility in a single coordinated pass. Produces a prioritized findings table suitable for direct conversion to GitHub issues via the create-github-issues skill.
中文简介正在准备中。当前显示原文说明。
Refactor an over-long or poorly structured SKILL.md by extracting examples to references/EXAMPLES.md, splitting compound procedures, and reorganizing sections for progressive disclosure. Use when a skill exceeds the 500-line CI limit, when code blocks dominate the skill body, when a procedure step contains multiple unrelated operations, or after a content update pushed the skill over the line limit.
中文简介正在准备中。当前显示原文说明。
Scaffold a new CLI command using Commander.js with options, action handler, three output modes (human-readable, quiet, JSON), and optional ceremony variant. Covers command naming, option design, shared context patterns, error handling, and integration testing. Use when adding a command to an existing Commander.js CLI, designing a new CLI tool from scratch, or standardizing command structure across a multi-command CLI.
中文简介正在准备中。当前显示原文说明。