Essential command-line tools and system utilities.
Browser automation with Puppeteer CLI scripts. Use for screenshots, performance analysis, network monitoring, web scraping, form automation, or encountering JavaScript debugging, browser automation errors.
Run test coverage analysis, identify missed and partial lines, and write tests to improve coverage. Use this when the user asks to check coverage, improve coverage, or write tests for uncovered code. This skill detects both completely missed lines and partially covered lines (executed but missing branch coverage) to match Codecov analysis.
Orchestrate Codex CLI for comprehensive code analysis (bugs, security, performance, and quality). Use when deep analysis is requested or when the scope is large; ask for scope if unclear.
Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.
Deploy and manage cloud infrastructure on Cloudflare (Workers, R2, D1, KV, Pages, Durable Objects, Browser Rendering), Docker containers, and Google Cloud Platform (Compute Engine, GKE, Cloud Run, App Engine, Cloud Storage). Use when deploying serverless functions to the edge, configuring edge computing solutions, managing Docker containers and images, setting up CI/CD pipelines, optimizing cloud infrastructure costs, implementing global caching strategies, working with cloud databases, or building cloud-native applications.
Open source contribution best practices with PR validation scripts. Use for pull requests, community contributions, or encountering personal artifacts in PRs, working on main branch, untested submissions, unrelated changes, unfocused PRs.
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, or verify PR readiness. Fetches comments via GitHub CLI, classifies by severity, applies fixes with user confirmation, commits with proper format, replies to threads.
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Handles regular branch commits (development) and merge commits (PR closure). Enforces project-specific conventions from CLAUDE.md.
Search real-world code examples from millions of GitHub repositories using literal patterns. Use when users need to find implementation examples, API usage patterns, or production code snippets. Triggers on "search code for", "find code examples", "how do developers use", "show me real examples of", "grep code".
Control JetBrains IDE programmatically for file operations, code analysis, refactoring, and terminal execution. Use when users want to interact with IntelliJ/WebStorm/PyCharm, run configurations, refactor code, or analyze files. Triggers on "open file in IDE", "run configuration", "refactor", "find files in project", "IDE terminal".
Detect test smells, overmocking, flaky tests, and coverage issues. Analyze test effectiveness, maintainability, and reliability. Use when reviewing tests or improving test quality.
Validate test effectiveness with mutation testing using Stryker (TypeScript/JavaScript) and mutmut (Python). Find weak tests that pass despite code mutations. Use to improve test quality.
Automate Chrome DevTools browser actions like navigation, forms, screenshots, and performance traces. Use when users need browser automation or page inspection. Triggers on "Chrome DevTools", "take a screenshot", "fill out the form", "performance trace", "click on".
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.
Use when implementing hot reloading with Bun (--hot, --watch), HMR, or automatic code reloading during development. Covers watch mode, hot mode, and HTTP server reload.
Use for Bun runtime, bunfig.toml, watch/hot modes, env vars, CLI flags, and module resolution.
Use this when updating the codex submodule or when patch files in codex-patches/ need to be added, regenerated, or repaired.
Use for Bun file I/O: Bun.file, Bun.write, streams, directories, glob patterns, metadata.
Bun package manager commands (install, add, remove, update), workspaces, lockfiles, npm/yarn/pnpm migration. Use for dependency management with Bun.
Accept Spectr change proposals by converting tasks.md to tasks.jsonc without requiring the spectr binary. USE WHEN you're in a sandboxed or restricted execution context and spectr is not available in your path. DO NOT USE WHEN you need a lightweight alternative for task acceptance, but have the spectr binary available. DO NOT USE when you have the spectr binary available.
Contextual grep for codebases. Answers "Where is X?", "Which file has Y?", "Find the code that does Z". Fire multiple in parallel for broad searches. Specify thoroughness, "quick" for basic, "medium" for moderate, "very thorough" for comprehensive analysis. Trigger on "Multiple search angles needed", "Unfamiliar module structure", "Cross-layer pattern discovery"
