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, 審查, 檢查, 簽入.
The English summary is being prepared. Showing the original description.
AsiaOstrich/universal-dev-skills☆ 43Updated Dec 30, 2025
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Validate at every layer data passes through to make bugs impossible
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Systematically trace bugs backward through call stack to find original trigger
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Create isolated git worktrees with smart directory selection and safety verification
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Each routine does one thing and does it well - extract when routines have multiple responsibilities
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Declare variables in smallest possible scope, initialize close to first use, minimize span and live time
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Name code by what it does in the domain, not how it's implemented or its history
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Flatten nested conditionals with early returns or table-driven methods - keep nesting depth under 3 levels
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Check all external inputs for validity - garbage in, nothing out, never garbage out
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Write comments explaining WHAT and WHY, never temporal context or history
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Try 2-3 different approaches before implementing - don't settle for first design you think of
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Run verification commands and confirm output before claiming success
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
Choose names that fully and accurately describe what the variable represents
The English summary is being prepared. Showing the original description.
obra/clank☆ 42Updated Oct 10, 2025
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.
The English summary is being prepared. Showing the original description.
pjt222/agent-almanac☆ 42Updated Oct 23, 2026
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.
The English summary is being prepared. Showing the original description.
pjt222/agent-almanac☆ 42Updated Oct 23, 2026
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.
The English summary is being prepared. Showing the original description.
pjt222/agent-almanac☆ 42Updated Oct 23, 2026
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.
The English summary is being prepared. Showing the original description.
pjt222/agent-almanac☆ 42Updated Oct 23, 2026