[FEATURE] Organization-wide shared CLAUDE.md via GitHub org

[simon-archer]

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

Our team has multiple repos under the same GitHub organization. We want to share company-level context (strategy, conventions, background knowledge) with Claude Code across all repos.

Currently, the options are:

• Duplicate CLAUDE.md in every repo (gets out of sync)
• Each developer manually symlinks ~/.claude/CLAUDE.md to a shared repo (manual setup, easy to forget)
• Enterprise file-based deployment (requires enterprise account + IT infrastructure)

None of these work well for small-to-medium teams using GitHub organizations.

Proposed Solution

Allow Claude Code to pull a shared CLAUDE.md from a GitHub organization level, similar to how .github repos work for default community health files.

For example:

• A your-org/.claude repo containing CLAUDE.md
• Or a file in your-org/.github/CLAUDE.md

Claude Code would automatically fetch this when working in any repo under that org.

Alternative Solutions

• Git submodules (adds complexity)
• Symlinks to a shared local repo (manual per-developer setup)
• Duplicating docs in each repo (maintenance burden)

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

Our company has 3 repos (examples):

• firmware - firmware
• app - Web/Mobile
• additional - additional repo

We want Claude Code to know:

• What our product does
• Our tech stack and how the repos connect
• Company conventions and terminology

Currently, if a dev clones app and asks Claude "how does this connect to the firmware", Claude has no context about the firmware repo or overall product.

Ideal flow:

1. We create organization/.claude-org repo (or similar) with shared context
2. Any dev working in any of our 3 repos automatically gets that context loaded
3. No manual symlinks, no duplicating files, no per-developer setup

Additional Context

This would make it much easier for teams to maintain a single source of truth for company context, coding standards, and conventions across all their repos.