How to Install and Configure Claude Code Commands for Development

Install Claude Code commands by running the platform-specific installer script in the scripts/ directory, which sets up the ~/.claude directory, copies wrapper scripts from tools/, and updates your system PATH.

The xbtlin/ai-berkshire repository provides a streamlined command-line interface for interacting with Claude AI through custom development commands. Installing these Claude Code commands enables rapid execution of skills defined in the repository's skills/ directory directly from your terminal.

Installation Steps

The repository includes dedicated installer scripts for Unix-based systems and Windows that automate the entire setup process.

Unix and macOS Installation

Run the bash installer to configure Claude Code commands on Linux or macOS:

# Clone the repository

git clone https://github.com/xbtlin/ai-berkshire.git
cd ai-berkshire

# Execute the Unix installer

./scripts/install-claude-commands.sh

The scripts/install-claude-commands.sh script performs four critical operations: it creates the ~/.claude configuration directory, copies executable wrapper scripts from tools/, adds the directory to your shell's $PATH, and sets appropriate file permissions.

Windows Installation

For Windows environments, use the batch file installer:

REM Clone the repository
git clone https://github.com/xbtlin/ai-berkshire.git
cd ai-berkshire

REM Run the Windows installer
scripts\install-claude-commands.bat

The scripts/install-claude-commands.bat script modifies your user %PATH% environment variable and creates the equivalent configuration directory in your Windows user profile.

How the Installation Works

The installer scripts implement a lightweight architecture with no external dependencies beyond standard shell utilities. When executed, the scripts complete the following actions:

• Directory creation: Establish a ~/.claude directory (or Windows equivalent) to store command wrappers
• File deployment: Copy shell scripts from the tools/ directory into the configuration folder
• PATH modification: Append the Claude directory to your user PATH environment variable, making commands discoverable from any terminal session
• Permission handling: Set executable bits on Unix systems to ensure the wrappers can run directly

The wrappers in tools/ serve as thin dispatchers that invoke specific skill modules defined in skills/*.md files, allowing you to run complex AI workflows with simple commands like claude run <skill>.

Verifying Your Installation

Confirm that Claude Code commands are properly configured by testing the help system:

claude --help

This should display the available commands and usage instructions. To see the specific skills available in your installation:

claude list-skills

This command enumerates the skills defined under the skills/ directory, confirming that the command wrappers can locate and parse the skill definitions.

Configuring and Customizing Commands

Modifying Command Wrappers

To customize the behavior of a specific Claude command, edit the corresponding wrapper script in tools/ and reinstall:

# Edit the wrapper for a specific skill

nano tools/investment-research.sh

# Apply the changes by rerunning the installer

./scripts/install-claude-commands.sh

Because the installer overwrites existing files in ~/.claude, your modifications take effect immediately after reinstallation. Each wrapper script handles argument parsing and environment setup before invoking the underlying skill modules.

Synchronizing Skills After Changes

If you modify skill definitions in the skills/ directory or add new markdown skill files, regenerate the artifacts that Claude Code commands rely on:

python scripts/sync-codex-skills.py

This utility ensures that the command wrappers stay synchronized with the current state of the skills/ directory, updating any generated code or metadata that the claude executable expects.

Summary

• Cross-platform installers: Use scripts/install-claude-commands.sh for Unix/macOS or scripts/install-claude-commands.bat for Windows to automate setup
• PATH integration: The installers modify your system PATH to include ~/.claude, enabling global command access
• Modular architecture: Command wrappers in tools/ dispatch to skill definitions in skills/ for extensible AI workflows
• Customization workflow: Edit wrapper scripts in tools/, then rerun the installer to update your local installation
• Skill synchronization: Run scripts/sync-codex-skills.py after modifying skill files to maintain command compatibility

Frequently Asked Questions

Where are the Claude Code command files stored after installation?

The installer creates and populates a ~/.claude directory (or equivalent Windows user profile location) that contains the wrapper scripts copied from the repository's tools/ folder. This directory is added to your system PATH during installation.

Can I use Claude Code commands without reinstalling after pulling repository updates?

For updates to existing command wrappers in tools/, you must rerun the installer script to copy the latest versions into ~/.claude. However, changes to skill definitions in skills/ only require running scripts/sync-codex-skills.py to regenerate the skill index that commands reference.

What dependencies are required to run the Claude Code installers?

The installers have no external dependencies beyond standard system tools—bash for Unix/macOS or standard Windows batch/PowerShell capabilities. The installation process requires only git to clone the repository and standard file system permissions to create directories and modify your user PATH.

How do I add a completely new Claude command to the system?

Create a new wrapper script in the tools/ directory following the pattern of existing scripts, then rerun the appropriate installer. The script will automatically copy your new wrapper to ~/.claude and make it available as a top-level command, provided it has the correct executable permissions or file extension.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}