Menu
List all built-in Claude Code tools
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Show recent Claude Code changes personalized to user's setup. Trigger when user asks about changelog, "what's new", "cc changelog", "claude code updates", "recent changes", or wants to know what changed in Claude Code.
Write ~/.claude/custom-handoff.md to hand off current work to the next session
List all configured hooks
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (GLOSSARY.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Review code changes from the current branch, staged changes, a git ref, or a diff/patch file. Pure git-native — no platform/PR awareness. Trigger when user says "review this", "review diff", "/df:code-review-diff", or provides a git ref or diff path. Read-only — never posts comments.
| name | list:builtin-tools |
| description | List all built-in Claude Code tools |
| disable-model-invocation | true |
Claude Code has a set of built-in tools that are always available, separate from MCP server tools. Users may want to see what built-in tools are available for reference.
Tools denied via permissions.deny in settings are removed from the session entirely — they never appear in the tool list, not even as deferred tools. So the live tool list alone under-reports what the harness ships: a denied tool looks identical to a tool that doesn't exist. Read the settings files to tell the two apart.
permissions.deny array from each settings file that applies, in order: ~/.claude/settings.json, .claude/settings.json, .claude/settings.local.json. Collect bare tool-name entries (e.g. NotebookEdit); ignore scoped ones like Bash(rm -rf /*:*), which gate arguments rather than the tool.mcp__) — both the ones available this session and the ones denied by those settings.For each tool, provide:
— disabled (deny: <settings file>) suffix if it was deniedOrganize by category:
Deferred tools (schemas loaded on demand via ToolSearch) are available — list them normally, not as disabled.
Use compact format with minimal formatting.