[FEATURE] Repo-backed channel level Claude Tag configuration

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

When utilizing Claude Tag in Slack, channel-level behavior guidelines and available custom skills are dictated by the connected codebase repository's CLAUDE.md and .claude/skills/ directory. Without connecting to a specific code repo, there is no way to manage a channel's behavior consistent with IaC practices.

This model introduces severe limitations in real-world workflows:

1. Multi-Repo Channels: A single Slack operation channel often acts as a hub that contributes to or tracks multiple connected codebases. Forcing Claude Tag to rely on a specific feature repo's CLAUDE.md means cross-repo instructions are either unavailable or required to be duplicated across all connected repos.
2. No-Repo Operations: Many channel tasks are conversational, operational, or analytical (e.g., triage, data investigation, skill execution) and shouldn't require a coding repository to be connected just to grant Claude its channel-specific instructions.
3. Instruction modification authorization: With the current options of either Org Admin level Channel Instructions and/or channel member level Channel Instructions, changes to those instructions are either overly restricted to Org Admins or allowed to be changed by any channel member without review respectively. There is no way to enforce review requirements on member level Channel Instruction changes.

Proposed Solution

Support a repo-backed, version-controlled "Control Plane" or "Governance Repository" configuration at the Slack Channel level.

Concretely:

• In the Claude Tag channel console settings, allow admins to designate a single, specific Git repository as the channel's master workspace configuration layer.
• When an execution environment initializes, Claude Tag should pre-load the .claude/ files, custom skills, and CLAUDE.md instructions from this master repo into the environment context ahead of fetching any codebase-specific files.

Alternative Solutions

I've tried setting the Channel Instructions text to first fetch instructions from a specific connected repo, but the results have been unreliable.

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

Example scenario:

I want Claude Tag to follow a specific protocol when investigating bugs and proposing solutions. This protocol should be followed regardless of which codebase (if any) may require a code change as a result.

I define in the Governance Repo's CLAUDE.md the following:

When the JIRA bug bot posts a newly created bug, perform the following steps:

1. Read the contents of the Jira bug and determine whether more information is required. If so, add a comment explaining what is needed.
2. Leverage tool/skill XYX to investigate logs and root cause the issue.
3. Enter Plan Mode and create a draft PR containing only the markdown plan. Provide a link to the plan and request human review.
4. If a human tells you to proceed with the plan: proceed with the implementation, remove the plan file, mark the PR as ready for review, and request human review.

When the JIRA bot posts a new bug, Claude Tag follows these steps regardless of which repo(s) may or may not be affected.

Additional Context

_No response_