claude-code-skills-extract

Use when the user wants a large, mechanical change split into many independent units and executed in parallel with isolated workers and PRs.

Use when the user wants browser automation in an existing Chrome session: click, fill, inspect tabs, capture screenshots, or debug web flows.

Use when code imports Anthropic SDKs or the user asks to build with the Claude API, Agent SDK, tool use, streaming, files, or batches.

Use when onboarding a repository into Claude Code by creating or improving CLAUDE.md, and optionally identifying useful skills, hooks, and verifier setup.

Use when the user wants to update Claude settings, hooks, permissions, MCP server toggles, or other JSON config safely and with scope awareness.

Use when changed code should be reviewed for reuse, code quality, and efficiency, then cleaned up before finalizing.

Use when the user wants the full git workflow: branch creation if needed, commit, push, and PR create or update with a concise summary and test plan.

Use when the user wants a single clean commit created from current changes with safe staging, message drafting, and non-interactive git usage.

Use when the user wants to customize Claude Code keybindings, rebind shortcuts, add chords, or edit `~/.claude/keybindings.json` safely.

Use when the user wants to review auto-memory, promote durable instructions into CLAUDE.md or local memory, and clean up duplicates or conflicts.

Use when the user wants a local review of a GitHub pull request based on its diff, risks, quality, performance, tests, and security implications.

Use when the user wants a prompt or command to run on a recurring interval, such as checking deploys, polling status, or repeating a slash-command.

Use when the user wants to create, inspect, update, or run scheduled remote agents in the cloud rather than local cron jobs.

Use when a code change must be verified by actually running the app, endpoint, or CLI flow instead of relying only on unit tests.

Use when the current branch or PR needs a focused security review that minimizes false positives and only reports concrete, exploit-relevant issues.

Use when diagnosing a failing or confusing Claude Code session by enabling debug logging, tailing recent logs, and explaining warnings or errors.

Use when the user wants to configure Claude Code statusline UI by inspecting shell prompt configuration and updating the relevant settings.

Use when another Claude Code session appears frozen, stuck, or abnormally slow and needs process-level diagnosis and reporting.

Use when a project needs one or more verifier skills for web, CLI, or API runtime checks that the Verify agent can discover automatically.

Use when a successful session or repeatable process should be captured as a reusable skill with steps, arguments, and invocation guidance.