Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Verification-first approach to code review feedback. Use when receiving review comments during the implement phase. Evaluate suggestions rigorously before implementing - no performative agreement.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Refactors code to improve readability, reduce complexity, and enhance maintainability without altering functionality. Use when the user says "refactor", "simplify this code", "clean up", "reduce complexity", "extract method", "this is too complex", or asks to improve naming/structure without changing behavior. Preserves all public APIs unless explicitly authorized.

Improve the shape of existing code without changing behavior.

Guide safe, incremental refactoring that improves code quality without changing behavior.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Debug and emulate specific code fragments or functions using the Unicorn engine. Activate when the user wants to emulate a function with Unicorn, trace binary execution without running the full program, decrypt or decode data by emulating the algorithm, or bypass environment dependencies (JNI, syscalls, libc) during emulation.

Review and critique a scientific manuscript, identifying critical issues with detailed explanations and recommendations. Produces a structured review with accept/revise/reject recommendation.

Review code against specs, designs, and decision compliance

Use when the user asks to "review this", "review the diff", "review my changes", "review my branch", "review against main", "open a review", or runs /review-diff. Opens the diff in a local browser for MR-style inline commenting — uncommitted changes if there are any, otherwise the committed branch vs its base — then reads the submitted comments back and addresses them.

Deep code/plan review for architecture, subtle bugs, and test quality. Use after sonnet review for thorough analysis.

Pull request review checklist.

Creating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from the main workspace or before executing an implementation plan. Skip for a quick fix on the current branch or when already in the feature's worktree.

Evaluate and maintain knowledge freshness - detect and fix stale knowledge

Use when generating Apex tests, designing test data factories, sanitising sandbox data, or improving Apex test coverage / quality.

This skill should be used when conducting structured multi-perspective debates to stress-test ideas, evaluate tradeoffs, or reach well-reasoned decisions. Provides the Socratic debate framework with 4 subagent roles.

Fix bugs with regression testing and auto-retry. Triggers on fix/debug/broken/error/not-working intent.

Begins a hotfix for a production issue using git-flow. This skill should be used when the user asks to "start a hotfix", "create hotfix branch", "fix a critical bug", "git flow hotfix start", or wants to begin a hotfix.

Root cause investigation methodology for bugs and failures. Use when encountering test failures, unexpected behavior, or errors during research or implement phases. Find the cause before attempting fixes.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

You must use this when conducting PRISMA-standard systematic reviews, protocol development, or Risk of Bias assessment.

Run browser tests on pages affected by current PR or branch

Red-Green-Refactor workflow. Write tests before implementation, maintain 80%+ coverage. Use when implementing logic, fixing bugs, or changing behavior.

Self-continuing loop that fixes a deliberately failing test, reruns it, and exits cleanly when green. Smallest cooking-routines skill — pairs with the cooking Stop hook to keep iterating past natural stops.

Create comprehensive test strategies and test plans for software projects. Use this skill when planning testing for new features, releases, or projects. Activate when: test plan, test strategy, testing approach, QA planning, test coverage, release testing.

Use when multiple causes could explain a bug — test the fewest-assumption hypothesis first; escalate to complex only when evidence forces it. Skip the full procedure when one step resolves it.

When a change has effects past the immediate fix (incentives, scale, feedback loops), ask "and then what?" across horizons before committing — the obvious fix often backfires downstream.

Tilt local development and e2e testing. Triggers on tilt, kind cluster, e2e tests, test/tilt, local dev cluster.

Review new GitHub issues, assess priority and urgency, suggest labels, and recommend assignees

Systematic approach to identifying, fixing, and validating bug fixes. Use when fixing bugs, resolving issues, or addressing errors.

Create comprehensive test plans for features and changes

Academic Vern - Needs more research. Cites sources, considers prior art, wants peer review.

Use after a git worktree has been created and needs its isolated environment activated. Runs the project's setup-env.sh, then verifies the environment with smoke-test.sh before starting development.

Review code changes against accepted ADRs for compliance violations

Smoke test for aliyun-skill-creator. Validate repository path conventions, frontmatter quality, script compilation, and README index refresh workflow.

Review generation strategy — Request a Review, follow-up emails, insert cards, Vine, early reviewer programs

Vine review program strategy — enrollment, product selection, timing, review quality maximization

Analyzes Xcode selective testing effectiveness for a test run, showing which test targets were skipped or ran, and diagnosing regressions in test selection. Can compare two test runs to identify what changed.

Disable the auto permissions review hook for this session. Tool calls return to normal permission prompts. Other terminal sessions are not affected.

Apply the correct branch naming convention before creating a new git branch or worktree. Invoke whenever the user says "create a branch", "new branch", "branch off", "checkout -b", "switch to a new branch", "create a worktree", "new worktree", "worktree for X", or any phrase where a new branch or worktree is about to be created. Also invoke when the user wants to rename or review an existing branch whose name does not follow the convention. Propose the name before executing.

Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".

Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.

Use when creating or rewriting a skill and you want one strong, workflow-conformant version built through failure analysis, review, and refinement instead of a multi-draft tournament.

Turnkey workflow for running tests, lint, and quality automation

Educator morning course health check for Canvas LMS. Shows submission rates, struggling students, grade distribution, and upcoming deadlines. Trigger phrases include "morning check", "course status", "how are my students", or any start-of-day teaching review.

Use when the user asks to review code or a pull request - performs focused review checking for obvious defects only, provides minimal feedback with clear approval/rejection format

Compares a single test case's behavior across two branches, analyzing pass/fail status, duration, flakiness, and failure details. Useful for investigating test regressions introduced by a feature branch.

Reflective pass over your memory files — merge duplicates, fix stale facts, prune the index.

Update context-mode from GitHub and fix hooks/settings. Pulls latest, builds, installs, updates npm global, configures hooks. Trigger: /context-mode:ctx-upgrade

Unified debugging workflow enforcing root cause protocol. Investigate → Understand → Reason → Fix. Use when debugging bugs, errors, or unexpected behavior.

Hypothesis-driven defect isolation — stack-trace forensics, breakpoint strategy, state inspection, and root-cause confirmation via minimal repro. Use when a defect surfaces (test failure, crash, exception, wrong output, intermittent flake) and the cause is not immediately obvious from the change set.

Universal PDCA debugging framework for systematic hypothesis verification. Use when debugging issues that require structured investigation, observing runtime behavior, or verifying fixes through iterative testing.

Invoke IMMEDIATELY via python script to stress-test decisions and reasoning. Do NOT analyze first - the script orchestrates the critique workflow.

Review routing corrections and propose updates to vault CLAUDE.md routing rules.

Deep technical review protocol for Engram pull requests. Trigger: Reviewing any external or internal contribution before merge.

Comprehensive exam preparation strategies and materials. Creates study schedules, review sheets, practice tests, and identifies weak areas. Use when preparing for exams, creating study plans, building review materials, or organizing exam preparation. Triggers - exam prep, test preparation, study schedule, review sheet, practice test, exam study plan.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Triages FiftyOne GitHub issues by categorizing as fixed, won't fix, not reproducible, or still valid. Use when reviewing GitHub issues, triaging bugs, or closing stale issues in the voxel51/fiftyone repository.

Fix all ESLint and TypeScript errors with parallel processing using snipper agents

Fix grammar and spelling errors in one or multiple files while preserving formatting

Fetch PR review comments and implement all requested changes

Review fixed income portfolios by pricing multiple bonds, retrieving reference data, analyzing cashflows, and running scenario analysis. Use when reviewing bond portfolios, computing portfolio duration and DV01, analyzing cashflow waterfalls, stress testing rate scenarios, or assessing portfolio composition.

Generate fixture files for Frappe test data and master data. Use when creating test fixtures, setup data, or master data for new sites.

GitHub deep review: bugs, PRs, best fix, stale-or-real, read code first.

Use this skill when the user mentions "merge request", "MR", "pull request", "code review", "review comments", "list MRs", "show MRs", "my MRs", "resolve discussion", or wants to manage GitLab merge requests.

Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?"

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

Troubleshooting guide for GrepAI. Use this skill to diagnose and fix common issues.

Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.

Manage Julia packages (add, remove, status, update, test, develop)

Run linting and code quality checks on Ruby and ERB files. Use before pushing to origin.

Creates comprehensive load test plans with realistic scenarios, traffic models, k6 scripts, and success criteria. Use for "load testing", "performance testing", "capacity validation", or "stress testing".

Add, fix, or update logging in project code

Daily wisdom review applying Charlie Munger's mental models to your work and thinking. Use when asked to review decisions, analyze thinking patterns, detect biases, apply mental models, do a "Munger review", or run the Munger Observer. Triggers on scheduled daily reviews or manual requests like "run munger observer", "review my thinking", "check for blind spots", or "apply mental models".

Clean up stale worktrees and help stuck PRs across an org's repos

Deprecated compatibility alias for qa-team. Use when existing recipes or agents still invoke outside-in-testing by name. Redirects future work to the qa-team skill for outside-in validation and parity loops.

Review development plans for issues, missing considerations, architectural violations, and alternatives. Includes SOLID compliance, circular dependency detection, and coupling analysis.

Use when asked to "PMF survey", "measure product-market fit", "40% rule", "Sean Ellis test", "Rahul Vohra method", or "how disappointed would you be". Helps quantify product-market fit and systematically improve it. The PMF Survey framework (created by Sean Ellis, popularized by Rahul Vohra at Superhuman) measures how disappointed users would be without your product and turns that data into a roadmap.

Review Rails code with high quality bar. Strict for modifications, pragmatic for new isolated code.

Creates ephemeral preview deployments for each pull request with automatic deployment, unique URLs, and cleanup on PR close. Use for "preview deployments", "PR environments", "ephemeral environments", or "review apps".

Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.

Retrieve and review responses from a Google Form.

Review who attended a Google Meet conference and for how long.

Find Google Tasks that are past due and need attention.

Review-fix iteration loop -- dispatches review agents then review-fixer, iterating up to 5 times with early termination on zero issues