[DOCS] CLI reference lacks skill-loading semantics for `--setting-sources user`

Open 💬 5 comments Opened Mar 5, 2026 by coygeek

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/cli-reference

Section/Topic

--setting-sources behavior, especially how it affects dynamically discovered project skills.

Current Documentation

The CLI reference currently says:

--setting-sources | Comma-separated list of setting sources to load (user, project, local)

What's Wrong or Missing?

Changelog v2.1.69 includes a fix for --setting-sources user not blocking dynamically discovered project skills, but the CLI docs do not explain this behavior.

The current description names allowed source values but does not document the practical effect on project-scope skill discovery.

Suggested Improvement

Expand --setting-sources docs with source-isolation semantics, including:

  • What is excluded when only user is selected
  • That dynamically discovered project skills should be blocked in that mode
  • One concrete example command and expected outcome

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/cli-reference | Defines --setting-sources but not skill-loading implications |
| https://code.claude.com/docs/en/skills | Related behavior for project-scope skills should be cross-referenced |

Total scope: 2 pages affected

Source: Changelog v2.1.69

Exact changelog entry:

Fixed --setting-sources user not blocking dynamically discovered project skills

View original on GitHub ↗

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