Quick inline code review for devloop plan changes or PR diffs

Respond to online reviews. Use when: drafting replies for Google, Yelp, G2, or building review response templates.

Use this skill when running Vitest tests to ensure safe execution. Applies when running tests, executing test suites, or invoking pnpm test, npm test, or vitest commands. Prevents hung processes through timeouts, manages watch mode, and ensures proper cleanup. Essential for automated test runs to avoid runaway processes consuming CPU for hours or days.

Strategic sales leadership guidance for B2B SaaS and enterprise software companies. Covers sales strategy, team building, pipeline management, enterprise selling, discovery calls, demos, proposals, negotiations, and sales operations. Use when building sales teams, designing sales processes, improving win rates, or scaling revenue operations. Use for "sales strategy", "sales process", "pipeline review", "deal strategy", "sales hiring", "quota planning".

Review changes, open PRs, run pre-launch checks, staged rollouts, and rollback. Use when preparing to ship to production or closing out a branch.

Use this skill when planning implementations, reviewing proposals, or evaluating technical approaches. Activates a skeptical senior engineer mindset that pokes reasonable holes in plans before execution. Trigger when user is planning features, designing systems, proposing solutions, or wants a critical review of an approach.

Fix a specific SonarQube issue in code by rule key and location

Use when the user asks how to use the spec-kit plugin, wants advice on spec-driven development, needs help choosing the next spec-kit workflow step, or asks for review of existing .specify specs, plans, tasks, constitution, or project context.

Review implementation plans as a staff software engineer. Use when the user asks for staff engineer feedback, senior engineering review, plan review, architecture review, implementation-plan critique, approval before proceeding, risk review, or feedback on a proposed technical plan.

Use when executing implementation plans. Dispatches independent subagents for individual tasks with code review checkpoints between iterations for rapid, controlled development.

Test-first variant of implement: understand the desired behavior, write a failing test, make it pass, then simplify.

Run tests iteratively fixing code or tests until all pass, then commit

Rigorous TDD methodology enforcing RED-GREEN-REFACTOR discipline. Use when implementing features or fixing bugs during the implement phase. Tests must be written before production code - no exceptions.

Enforces TDD discipline - write tests first, then implement

# test-runner

A test skill for validation testing. Use when testing skill parsing and validation logic.

Maintain and update investment theses for portfolio positions and watchlist names. Track key data points, catalysts, and thesis milestones over time. Use when updating a thesis with new information, reviewing position rationale, or checking if a thesis is still intact. Triggers on "update thesis for [company]", "is my thesis still intact", "thesis check", "add data point to [company]", or "review my positions".

Go project toolchain -- build, test, lint, module management, and debugging.

Add, fix, or update logging in project code

Unified validation dispatcher. Auto-detects validation type from argument or presents selection menu. Routes to test, implement (verify), or hooks-test.

Hygiene pass over active notes, ideas, and projects

Evaluate a vendor — cost analysis, risk assessment, and recommendation

Identify and evaluate publication venues. Considers scope, impact factor, review timeline, acceptance rate, and fit. Produces a ranked shortlist with submission strategy guidance. Updates .papermill/state.md.

Fake code detection — performative implementations, test theater, misleading patterns, red flags

Refactor SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view's layout, handle view models safely, or standardize how dependencies are initialized and passed.

Structured visual QA verdict for screenshot-to-reference comparisons

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

Perform an adversarial review of proposed work. Use ONLY when the user explicitly types /adversarial-review. Never auto-trigger, even if the user mentions reviewing, questioning, or challenging their approach.

Use when unit tests look green but confidence is low and mutation testing is needed to expose weak assertions. AE.LTD workflow for targeted mutation runs and actionable test hardening.

Use when parallel branches are needed for feature work, hotfixes, or review fixes using git worktrees with minimal context switching. AE.LTD workflow for safe creation, usage, and cleanup.

Run mutation testing against an AL project using al-mutate (MSDyn365BC.AL.Mutate). Identifies test gaps by applying AST-based mutations and checking whether the test suite catches them via al-runner. No BC instance required. Produces mutations.json and report.md.

Minimal motion-transfer smoke test for Model Studio AnimateAnyone.

Minimal expressive portrait smoke test for Model Studio EMO.

Minimal lightweight portrait animation smoke test for Model Studio LivePortrait.

Minimal validation for crawl-and-skill workflow readiness.

Minimal matrix test wrapper for aliyun-modelstudio-entry-test.

Minimal deep-research smoke test for Model Studio Qwen Deep Research.

Minimal text generation smoke test for Model Studio Qwen text models.

Minimal multimodal embedding smoke test for Model Studio VL embedding models.

Minimal lip-sync replacement smoke test for Model Studio VideoRetalk.

Minimal digital-human smoke test for Model Studio wan2.2-s2v.

Batch-fix all open bugs in parallel using git worktrees. Fetches bug-type tasks in "idea" status from Transit, creates an isolated worktree per bug, and spawns parallel subagents each running the fix-bug workflow. Use when you want to tackle all open bugs at once, e.g. "fix all open bugs", "bug blitz", "resolve all Transit bugs".

Run TypeScript checks and fix all errors (project)

This skill should be used when the user asks to "update chezmoi", "sync dotfiles", "match live state", "match repo state", "chezmoi re-add", "chezmoi diff fix", "chezmoi apply", or mentions chezmoi source/live discrepancies, divergence between dotfiles repo and filesystem, or wants to reconcile chezmoi state in either direction.

Review protocol code for chain halt risks, non-determinism, and onchain behavior bugs

Remove AI-generated code patterns ("slop") from a branch. Use when asked to clean up AI-generated code, remove slop, fix AI coding style issues, or make AI-written code look human-written. Triggers on phrases like "remove slop", "clean up AI code", "fix AI style", or "make this look human-written".

Comprehensive code review checklist for pull requests

Run a comprehensive code review

Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.

OCaml coding style and refactoring patterns. Use when the user asks to tidy, clean up, refactor, or improve OCaml code, reviewing code quality, enforcing naming conventions, or reducing complexity.

Generates git commit messages following Conventional Commits 1.0.0 specification with semantic types (feat, fix, etc.), optional scope, and breaking change annotations. Use when committing code changes or creating commit messages. Triggers on phrases like 'commit', 'commit and push', 'make a commit', 'git commit', or when commit is part of a compound action (e.g., 'bump version and commit').

Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors.

Context-driven spec-driven development workflow manager. Organizes work into tracks with specs, plans, and changelogs. Provides file resolution, track state management, and workflow enforcement. Invoke with /conductor:setup, /conductor:new-track, /conductor:implement, /conductor:status, /conductor:review, or /conductor:revert.

Guidelines for maintaining external Dart packages, covering versioning, publishing workflows, and pull request management. Use when updating Dart packages, preparing for a release, or managing collaborative changes in a repository.

Use when encountering any bug, error, or unexpected behavior in a fullstack project — enforces root-cause-first debugging discipline before any fix attempts

Use for generic debugging — error analysis, stack trace parsing, issue reproduction, git bisect, code tracing. Different from /sf-debug (Salesforce-specific). Pairs with /investigate skill (read-only diagnosis).

Systematic debugging methodology for diagnosing failures and root cause analysis. Triggers on: 2+ failed fix attempts, 'ultradebug', 'uld', debugging in circles, complex system failures, intermittent bugs.

Check that all code has appropriate documentation and fix gaps

Use when working with error diagnostics smart debug

Execute software engineering plan documents using Eve jobs, dependencies, and review gating.

Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches

Use when given a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches

Lightweight bug fix workflow. 3-tier classification for fast iteration without approval gates.

Fetch PR review comments and implement all requested changes

Improve test coverage by identifying gaps and generating meaningful tests

Analyzes changed files and improves unit test coverage using project-specific testing conventions from .trellis/spec/ unit-test specs. Determines test scope (unit vs integration vs regression), adds or updates tests following existing patterns, and runs validation. Use when code changes need test coverage, after implementing a feature, after fixing a bug, or when test gaps are identified.

Create and sign JSON Web Tokens (JWTs) for testing and development. Use when the user wants to generate, create, build, or sign a JWT — e.g. "create a JWT", "generate a test token", "sign this payload", "make a JWT with these claims", "build an access token". Supports HMAC, RSA, and ECDSA algorithms.

This skill is used when the project wiki needs a health check. Triggers include 'lint the wiki', 'check wiki health', 'run field-guide lint', 'are there stale wiki pages', 'find orphaned pages', 'check for contradictions in the wiki'.

Lint, format, and optionally commit changes

Manage a local Business Central instance for development and testing. Detects host vs container environment automatically. Uses bc-linux run-tests.sh for test execution.

Run autofix maintenance commands to keep code clean and consistent.

Sleep-time memory reflection: review recent conversations and daily notes, extract insights, and consolidate into long-term memory. Use when triggered by cron, heartbeat, or explicit request to reflect on recent activity. Runs as background processing to improve memory quality over time.

Execute build, test, lint, serve, and other tasks in an Nx workspace using single runs, run-many, and affected commands. Use when user says "run tests", "build my app", "lint affected", "serve the project", "run all tasks", or "nx affected". Do NOT use for code generation (use nx-generate) or workspace configuration (use nx-workspace).

Use when the user says "/plan-review", "plan review", or "PRD review" and provides a plan file path that needs critical review and iterative refinement with Codex.

This skill should be used when the user asks about algorithms, data structures, "optimize this function", "fix this bug", "logic error", "performance issue", "time complexity", "memory leak", "race condition", "deadlock", "recursion", "sorting", "searching", or any request involving algorithmic logic, debugging, or computational problem-solving. Surgically precise solutions.

Geometric hull calculator for 2D point sets supporting convex hull, concave hull (concave-hull, alphashape), and minimum bounding rectangle. Use when working with pywayne.cv.geometric_hull_calculator module to compute geometric hulls, visualize results with OpenCV or matplotlib, and generate random test point sets.

Quiz yourself on documents you've recently read to test understanding and retention

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

Find Google Tasks that are past due and need attention.

Code refactoring with AI assistance. Use for modernizing code, converting JavaScript to TypeScript, class to hooks conversions, and systematic renaming.

Unified review skill — auto-detects plan or code, assembles the right panel, runs a bounded review-fix loop with severity gating. Use when a plan or implementation needs review.

Use for SiftCoder-shaped code review of a PR or pending change. Memory-aware (prior decisions, project conventions) and value-add over built-in /review. Use built-in /review for general best-practice; use this for project-context-aware review.

Perform a code review with linting, standards checking, and priority-ranked findings

Systematic code review workflow for evaluating changes against coding standards. Use when reviewing pull requests, commits, diffs, or code changes. Ensures type-safety, maintainability, readability, and adherence to best practices before code is merged.

Generate branch-story sections 4-7 (Outcome, Historical Analysis, Concerns, Successful Development Patterns) from archived tickets and carry-over verdicts. Used by the report workflow when assembling a PR story.

This skill should be used when the user asks to "review a pull request", "code review this PR", "check this PR for bugs", "review PR

Run health checks on the Ruflo installation and fix common issues

End of day wrap-up — captures what got done, what didn't, and plans for tomorrow. Weekly close-out on configurable review day (default Friday).

Propose and apply evidence-based amendments to skills based on observation data. Use when the user says "amend skill", "improve skill", "fix the X skill", "skill needs updating", "update skill based on feedback", or "evolve skill".

How to handle code review feedback — verify before implementing, push back when wrong, never agree blindly

Morning check-in — surfaces goals, summarizes where you left off, captures today's plan, and gives goal-alignment feedback. Weekly review mode on configurable review day (default Friday).

App Store Connect submission checklist and Apple App Review Guidelines reference. Use when preparing iOS apps for review, after rejection, or validating App Store Connect configuration.

Summarize GitHub pull requests awaiting your review with status, age, and priority. Use when triaging your review queue, prioritizing code reviews, or checking what PRs need attention.

Review architecture compliance before execution

Test-driven debugging for failing tests or bugs

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Implements scientific method for debugging with root cause analysis.