skills.rest
bbrowning
bbrowningCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Managing Cross-Repository Configuration

Determine storage locations for configurations, learnings, and skills across Claude Code's three-tier architecture.

2|1|Updated Oct 22, 2025
Search Tags:#development workflow#configuration management#git worktrees#knowledge sharing
One-click install
npx skills add https://github.com/bbrowning/bbrowning-claude-marketplace --skill managing-cross-repository-configuration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Managing Cross-Repository Configuration
Source: https://github.com/bbrowning/bbrowning-claude-marketplace/tree/main/claude-builder/skills/cross-repo-config
Command: npx skills add https://github.com/bbrowning/bbrowning-claude-marketplace --skill managing-cross-repository-configuration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Users struggle to maintain consistent Claude Code configurations, skills, and learnings across diverse projects and repositories without duplication or conflicts. This Skill provides a clear framework for managing configuration effectively, ensuring your AI works consistently everywhere.

Core Features & Use Cases

  • Three-Tier Architecture: Understand where to store personal preferences (global), shareable domain knowledge (plugin skills), and project-specific patterns (project-local) to avoid clutter and ensure relevance.
  • Decision Framework: Learn to quickly identify the appropriate tier for any configuration or learning, ensuring optimal scope and discoverability, saving you time on setup.
  • Git Worktree Integration: Seamlessly manage configurations across multiple git worktrees, preventing divergence and streamlining context-switching, so your environment is always ready.

Quick Start

"I need to decide where to store a new learning about Python coding style. Should it be global, a plugin skill, or project-local?"

Frequently Asked Questions about Managing Cross-Repository Configuration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide where to store Claude Code configuration across multiple repositories?▼

Configuration storage depends on scope: use global ~/.claude/CLAUDE.md for personal preferences applying everywhere, plugin skills in the marketplace for shareable domain knowledge, and project-local .claude/CLAUDE.md for repository-specific patterns. This three-tier architecture prevents duplication and maximizes reusability across your projects.

Can I manage configurations consistently across git worktrees without conflicts?▼

Yes. The three-tier architecture handles git worktree integration seamlessly by isolating global settings, plugin skills, and project-local patterns into separate scopes. Each tier remains independent, preventing divergence and streamlining context-switching between worktrees.

When should I use the /learn command to save a new configuration or learning?▼

Use /learn to save content at the appropriate tier: global for personal preferences, plugin skills for reusable domain knowledge, and project-local for patterns specific to a repository. The decision framework ensures the /learn command routes your content to the correct storage location based on scope and reusability.

What's the difference between global, plugin skill, and project-local configuration storage?▼

Global storage (~/claude/CLAUDE.md) holds personal preferences for all projects; plugin skills live in the marketplace as shareable domain expertise; project-local storage (.claude/CLAUDE.md) captures repository-specific patterns. This separation ensures optimal relevance, discoverability, and avoids configuration clutter.

How do I avoid duplicating configurations across projects?▼

Apply the decision framework to classify each configuration by scope: if it applies everywhere, store globally; if it's domain knowledge others should reuse, create a plugin skill; if it's project-specific, keep it local. This routing prevents duplication and maintains consistency across repositories.

Related Skills

Explore More Software Engineering Skills→
Moonsong-LabsMoonsong-Labs
3

using-git-worktrees

Create and validate isolated Git worktrees for feature development.

Official
Advanced
ronnycodingronnycoding
20

create-claude-plugin

Create Claude Code plugins bundling skills, agents, commands, hooks, and MCP servers.

Community
Intermediate
dyoshikawadyoshikawa
1.3k

git-worktree-runner

Create, list, remove, and navigate git worktrees with configurable defaults.

Community
Intermediate
koya-altkoya-alt

environment-secrets

View, set, delete, and request environment variables and secrets.

Community
Intermediate