Claude Code user creates /discuss command for read-only conversations

A Claude Code user developed a custom skill called /discuss to address the frustration of repeatedly typing "don't make any changes" during conversations. The 25-line skill creates a read-only mode for discussions about architecture decisions, code exploration, or brainstorming without triggering file modifications.

How it works

The user runs Claude with claude --dangerously-skip-permissions since the skill maintains read-only behavior, then invokes /discuss followed by a question like "why is this widget rebuilding so much." This triggers conversation instead of code diffs.

Skill capabilities and restrictions

The /discuss skill description specifies:

• What it can do: Read files, search code (Glob, Grep), explore codebase, run read-only shell commands (git log, git diff, git blame, flutter analyze, dart test, ls), use web search and web fetch, spawn research subagents (Explore, Plan, general-purpose for research), reason, explain, compare approaches, and give opinions
• What it must not do: Use Edit, Write, or NotebookEdit tools; run shell commands that create, modify, or delete files; create plans, todos, or memory entries unless explicitly requested

User experience

The user notes that Planning mode exists but is "a whole different thing," and toggling permissions is "overkill" for simple conversation needs. The skill keeps responses conversational, matching the user's energy—exploring loosely when they're exploring, or providing deep technical analysis when requested.

The approach addresses a specific workflow gap where users want to "talk through an idea, research a topic, or explore the codebase without making any modifications" but find existing controls either too restrictive or insufficiently granular.