Claude Code Slash Commands · page 3

[advanced] Restrict file edits to a specific directory boundary

[advanced] Activate both careful mode and freeze mode together

[advanced] Query past workflow results — filter by workflow type, date, or provider

[advanced] Switch to Knowledge Work mode (or toggle with off)

[advanced] Execute tasks in loops with conditions, iterative improvements until goals are met

[advanced] Generate an optimized prompt for any task using meta-prompting techniques

Configure AI provider models for Claude Octopus workflows

[advanced] Force multi-provider parallel execution for any task - manual override mode

[Legacy] Redirects to /octo:auto — the smart router

[advanced] Team of Teams - Decompose compound tasks across independent claude instances

Run content analysis pipeline on URL(s) to extract patterns and create anatomy guides

Intelligent plan builder - creates strategic execution plans (doesn't execute). Use /octo:embrace to execute plans.

Score an existing PRD against the 100-point AI-optimization framework

Write an AI-optimized PRD using multi-AI orchestration and 100-point scoring framework

Check provider health before running multi-LLM workflows

Quick execution mode for ad-hoc tasks without full workflow overhead

Deep research with multi-source synthesis and comprehensive analysis

[advanced] Resume a previous agent by ID — continue an interrupted task where it left off

[advanced] Generate engineering retrospectives from git history with trends and team analysis

Enhanced multi-LLM review with inline PR comments — escalation path beyond Claude-native /review

[advanced] Manage scheduled workflow jobs (add via wizard, dashboard, list, remove, enable, disable, logs)

[advanced] Manage the scheduled workflow runner daemon (start/stop/status)

GitHub-aware work monitor - triages issues, PRs, and CI failures

Interactive setup wizard — install providers, configure auth, RTK, token optimization

NLSpec authoring - Structured specification from multi-AI research

[advanced] Two-stage review: spec compliance then code quality

Test-driven development with red-green-refactor discipline

[advanced] Remove freeze mode edit restriction

Implement the plan

Execute comprehensive cryptocurrency research using all crypto agents

Execute lightweight cryptocurrency research using haiku agents

Understand the current state of the git repository

Creates a concise engineering implementation plan based on user requirements and saves it to specs directory

Creates a concise engineering implementation plan based on user requirements and saves it to specs directory

Load context for a new agent session by analyzing codebase structure, documentation and README

Load context for a new agent session by analyzing codebase structure and README

Answer questions about the project structure and documentation without coding

Manage, organize and ships your codebase.

ChatGroup architecture — how conversation data flows from raw JSONL to rendered chat groups. Use when working on UserGroup, AIGroup, SystemGroup, display items, tool linking, chunks, or the rendering hierarchy.

Design system and visual language — theming, CSS variables, Tailwind config, component styling patterns, icon usage, animations, and z-index layers. Use when creating or modifying UI components, working with the dark/light theme, or debugging visual issues.

Explains what "Visible Context" is — the 6 trackable token categories, what falls outside tracking, how it's displayed, and why it matters. Use when someone asks about visible context, token attribution, or context window usage.

Markdown search logic — how in-session and cross-session search works. Use when working on SearchBar, search highlighting, searchHighlightUtils, markdownTextSearch, or SessionSearcher.

Navigation and scroll orchestration — tab navigation, error highlights, search scrolling, auto-scroll coordination, and common bug patterns. Use when working on useTabNavigationController, scroll restore, or navigation requests.

Create a new obsidian-second-brain command via interview - zero markdown editing required

Surface 3-5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes - what is worth working on next

Vault-first source-grounded research via Gemini File Search. One command, no browser. The grounded parallel to /research-deep (which is open-web via Perplexity).

Generate a decision record when the vault structure changes - the vault knows why it knows what it does

Read Google Calendar and write an AI-first snapshot to the vault - today, week, next week, or a custom range

Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions. Re-run to refresh without clobbering your edits

Show or update a kanban board - flags overdue items, updates from conversation

Reconcile the vault against your calendar - flag deadlines and commitments implied by notes that are not on the calendar. Flag only, never adds events

Quick idea capture - zero friction, saves to Ideas/ and mentions in daily note

Red-team your current idea against your own vault history - finds contradictions, past failures, and flawed assumptions

Bridge two unrelated domains using your vault's link graph - forces creative friction to spark new ideas

Create or update today's daily note - pulls calendar events, overdue tasks, and conversation context

Extract decisions from this conversation and log them to the right project notes

Surface unnamed patterns from your recent notes - recurring themes, hidden connections, and conclusions you haven't explicitly stated

Export a clean structured snapshot of the vault that any agent or tool can consume - flat JSON, markdown index, or an OKF (Open Knowledge Format) bundle

Smart vault search - returns results with context, not just filenames

Promote an idea fragment into a full project spec with tasks, board entries, and structure

Run a vault health check - grouped by severity, detects contradictions, concept gaps, stale claims, and structural issues

Ingest a source into the vault - the vault rewrites itself around new knowledge. Every ingest updates entities, rewrites stale claims, synthesizes new concepts, and resolves contradictions.

Scan your vault and generate a _CLAUDE.md operating manual, index.md catalog, and log.md pointer

Review vault learnings, prune stale ones, surface active patterns - the vault's lessons compound or expire

Log this work or dev session to the vault - infers project from context

Generate a meeting note in the vault from a Google Calendar event - pre-fills attendees, time, and link so notes/decisions/action items can be captured

Convene a panel of distinct perspectives on a decision - one independent verdict per lens, then a synthesis. A multi-persona complement to /obsidian-challenge

Create or update a person note from conversation context

Create or update a project note - adds to board and daily note automatically

Live project status from git + local docs - infers all context from vault notes, no config required

Summarize a time period from the vault - today, week, or month

Find and resolve contradictions in the vault - the vault maintains its own truth

Track a recurring obligation (payment, filing, ops) with a cadence and a computed next-due date

Generate a structured weekly or monthly review note from vault history

Save everything worth keeping from this conversation to the vault

Create or move a Google Calendar event - standalone, from a vault task, or via suggested-time slots - and propagate the link back to the task

Automatic synthesis - scans the vault for unnamed patterns and writes synthesis pages without being asked

Add a task to the right kanban board with inferred priority and due date

Generate a visual canvas map of your vault - see the shape of your second brain and how knowledge connects

Load your identity, values, priorities, and current state in one shot - with progressive context levels to avoid burning tokens

Extract metadata, transcript, and summary from a podcast episode, saved as an AI-first note in the vault

Vault-first deep research - scans the vault, fills gaps (Perplexity + Grok when keyed, free key-less sources otherwise), synthesizes a delta, then propagates updates across people/projects/ideas via /obsidian-save

Web research with citations - Perplexity Sonar when an API key is set, free key-less sources (Wikipedia, HackerNews, arXiv, Reddit, and more) otherwise. Deep dossier with summary, facts, timeline, players, contrarian views, open questions

Deep cross-reference of everything the vault knows about one topic - agreements, contradictions, stale claims, and coverage gaps. Pure vault, no network

Scan X for what's trending in a topic - themes, voices, hooks, and post ideas powered by Grok + Live Search

Deep-read an X (Twitter) post via Grok + Live Search - verbatim post, thread, TL;DR, claims, reply sentiment, voices to watch

Extract transcript, metadata, and top comments from a YouTube video - summarized via Grok and saved to vault

Review and process everything captured on the go from the Telegram journal bot - voice, text, images, PDFs, links - waiting in the catchup queue. You pull it when you are back at the laptop; nothing is processed autonomously.

Run autonomous hunt loop on a target — scope check → recon → rank surface → hunt → validate → report with configurable checkpoints. Usage: /autopilot target.com [--paranoid|--normal|--yolo]

Build an exploit chain — given bug A, finds B and C to combine for higher severity and payout. Knows common chain patterns: IDOR→ATO, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth. Usage: /chain

Active vulnerability hunting. Two-track dispatcher — asks Red Team vs WAPT, hands off to hunt-dispatch skill and sibling commands. Usage: /hunt target.com | /hunt *.target.com | /hunt targets.txt [--vuln-class X] [--source-code P] [--chrome]

On-demand intelligence fetch for a target — CVEs, disclosed reports, new features. Wraps learn.py + hunt memory context. Usage: /intel target.com

Inspect or rotate hunt-memory JSONL files (audit.jsonl, patterns.jsonl, journal.jsonl). Caps file size and keeps N rotated backups so memory does not grow unbounded.

Pick up a previous hunt on a target — shows hunt history, untested endpoints, and memory-informed suggestions. Usage: /pickup target.com

Run full recon pipeline on a target — subdomain enum (Chaos API + subfinder), live host discovery (dnsx + httpx), URL crawl (katana + waybackurls + gau), gf pattern classification, nuclei scan. Outputs to recon/<target>/ directory. Usage: /recon target.com

Log current finding or successful pattern to hunt memory. Auto-fills from /validate output if available. Usage: /remember

Write a submission-ready bug bounty report. Generates H1/Bugcrowd/Intigriti/Immunefi format with CVSS 3.1 score, proof of concept, impact statement, and remediation. Run /validate first. Usage: /report

Show ranked attack surface for a target based on recon output + hunt memory. Invokes recon-ranker agent. Usage: /surface target.com

Meme coin and token security scan — checks for rug pull vectors (hidden mint, honeypot, fee manipulation, LP lock bypass, authority retention, bonding curve exploits, fake renounce, sandwich amplification). Runs automated token_scanner.py + manual 8-class audit. Usage: /token-scan <contract_path_or_dir> [--chain solana]

Quick 7-Question Gate triage on a finding before writing a report. Kills N/A submissions before they happen. Faster than /validate — for quick go/no-go decisions. Usage: /triage