[FEATURE] add command to bypass/ignore .claude/ configurations for a specific session or prompt

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Currently, when working in a repository with custom .claude/ skills, hooks, and configurations, Claude Code automatically applies these settings globally across the active session. However, there are times when I need to run a quick test, execute a clean prompt, or debug an issue without the overhead or interference of our pre-configured repository scripts and custom behaviors.

Proposed Solution

I would love to see a native command or flag introduced to temporarily bypass these configurations.
Some potential implementations could include:
• /ignore-claude-config or /bypass-config: A session command that toggles off the local .claude/ configurations for the remainder of the session or until toggled back on.
• A prompt-level flag: Allowing a syntax like claude --no-config "my prompt here" directly from the terminal to run a single, isolated execution.
• /fresh or /vanilla: A quick command to instantly clear context and ignore local repository skills for that specific interaction.

Alternative Solutions

Right now, the only workaround is manually renaming or moving the .claude/ directory before running a prompt, and then restoring it afterward. This is tedious, disrupts source control, and risks accidentally committing a broken repository state.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Example scenario:

1. I'm working on a project that uses heavy custom .claude/ configurations, including pre-command hooks, automated test-running scripts, and highly specialized local skills.
2. I need to debug a broken custom script, or quickly ask Claude a generic question without triggering the overhead and execution of our repository's automated hooks.
3. With this feature, I could run a single command like /ignore-config (or use a temporary flag) to cleanly execute a vanilla prompt without Claude loading the local configurations.
4. This would save me time because I wouldn't have to constantly rename or move the .claude/ directory out of the repository just to run a quick test, preventing workflow disruption and accidental git commits of a broken local setup.

Additional Context

This would significantly improve developer workflows for debugging custom hooks, testing raw Claude behavior versus enhanced repository skills, and executing quick tasks that don't require the project's heavy custom configurations.