[FEATURE] /init should warn before scanning if no exclude rules are present

Resolved 💬 3 comments Opened Mar 6, 2026 by zckernel Closed Mar 10, 2026

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

During /init are using too much unnecessary tokens for newbies.

Proposed Solution

Before running /init, Claude Code should check whether CLAUDE.md exists and contains exploration rules. If
not, it should prompt the engineer:
"No file exclusion rules found. Large directories like node_modules/ may be scanned, consuming many
tokens. Add exclusions to CLAUDE.md first, or proceed anyway?"

This would prevent unexpected token burn and build trust that the tool is working in the user's interest.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗