Claude Config
Professional configuration management for [Claude Code](https://claude.com/claude-code) with automatic updates.
Loading actions...
Skill content
Main instructions and any bundled files for this skill.
Claude Config
Professional configuration management for Claude Code with automatic updates.
Quick Start
Install with one command:
sh -c "$(curl -fsSL https://gitlab.com/oldmission/claude-config/-/raw/main/install.sh)"
This installs:
- Global configuration to
~/.claude/(custom commands, settings) - CLI tool to
~/.local/bin/claude-config(for updates and project management) - Optional: Project configuration (you'll be prompted)
Add to PATH if needed:
export PATH="$HOME/.local/bin:$PATH" # Add to ~/.bashrc or ~/.zshrc
Adding Projects
After installation, use claude-config to manage projects:
# Add a project
claude-config register ~/path/to/project
# List registered projects
claude-config list
# Update everything (global + all projects)
claude-config update
What You Get
Custom slash commands (available globally):
/boot- Load project context (design docs + codebase)/design- Interactive design workflow (problem ā solution ā documentation)/review- Comprehensive code review/commit- Smart commit helper with conventional messages/test- Run tests with auto-detected framework/fix- Quick fix workflow for bugs/refactor- Identify code smells and refactor/explain- Quick code explanations/handoff- Create session handoff for continuity/commands- List all available commands
Automatic updates:
- Notifications every 13 days when updates are available
- One command updates global config + all registered projects
- Automatic backups before updates
- Rollback support if needed
Configuration levels:
- Global (
~/.claude/) - Personal preferences for all projects - Project (
CLAUDE.md,.claude/) - Team standards in version control - Local (
CLAUDE.local.md) - Personal overrides (gitignored)
Language standards (selected during project setup):
- Python
- Java
- C++
- JavaScript/TypeScript
- Bash
- Generic (no language-specific rules)
Common Workflows
Start a project:
claude-config register ~/myproject
# Select languages when prompted
# Files are copied to your project
# Commit CLAUDE.md and language standards to version control
Stay up to date:
# You'll see notifications when updates are available:
# š¦ Claude Config update available
# Run 'claude-config update' to upgrade
claude-config update
Design ā implement ā review:
/plan on
/design authentication # Design the feature
# ... implement ...
/test # Run tests
/review latest # Review changes
/commit # Smart commit
/handoff # End session with handoff
Session continuity:
# End of session:
/handoff # Captures todos, decisions, next steps
# Start of next session:
/boot . # Loads DESIGN.md, HANDOFF.md, context
# Continue exactly where you left off
Configuration Levels Explained
Global (~/.claude/)
Personal preferences that apply to all projects.
- Custom slash commands
- Git preferences
- Linter settings
- Located at
~/.claude/CLAUDE.md,~/.claude/settings.json,~/.claude/commands/
Project (CLAUDE.md, .claude/)
Team standards checked into version control.
- Coding standards
- Development workflows
- Language-specific rules (via
*-code-standard.mdfiles) - Testing requirements
- Commit these files so your whole team uses the same standards
Local (CLAUDE.local.md)
Personal overrides NOT shared with team (gitignored).
- Personal coding preferences
- Local environment settings
- Optional - create manually if needed
- See
project/CLAUDE.local.md.examplefor reference
Language Standards
During project setup, select language(s) for your project. Selected standards are copied to your project root:
python-code-standard.md- Python naming, linting (ruff), testing (pytest), virtual environmentsjava-code-standard.md- Java naming, builds (Maven/Gradle), testing (JUnit), JavaDoccpp-code-standard.md- C++ naming, builds (CMake), linting (clang-format/clang-tidy), testing (GTest)javascript-code-standard.md- JS/TS naming, linting (ESLint/Prettier), testing (Jest/Vitest)bash-code-standard.md- Bash naming, linting (shellcheck), compatibility (Bash 3.2+)
Polyglot projects can select multiple languages.
CLI Reference
claude-config update # Update global + all projects
claude-config list # Show registered projects
claude-config register <path> # Add a project
claude-config unregister <path> # Remove a project
claude-config rollback # Restore from backup
claude-config version # Show version
claude-config help # Show help
Repository Structure
~/.claude-config/ # Installed here (like ~/.oh-my-zsh)
āāā install.sh # Installer (used by curl command)
āāā claude-config # CLI tool (symlinked to ~/.local/bin/)
āāā global/ # Global configuration templates
ā āāā CLAUDE.md
ā āāā settings.json
ā āāā commands/ # Slash commands
ā āāā boot.md
ā āāā design.md
ā āāā review.md
ā āāā commit.md
ā āāā test.md
ā āāā fix.md
ā āāā refactor.md
ā āāā explain.md
ā āāā handoff.md
ā āāā commands.md
āāā project/ # Project configuration templates
āāā CLAUDE.md # Language-agnostic standards
āāā .claude/settings.local.json
āāā .gitignore
āāā CLAUDE.local.md.example
āāā languages/ # Language-specific standards
āāā python-code-standard.md
āāā java-code-standard.md
āāā cpp-code-standard.md
āāā javascript-code-standard.md
āāā bash-code-standard.md
Customization
Before installation:
- Clone the repo:
git clone https://gitlab.com/oldmission/claude-config.git - Edit files in
global/andproject/to match your preferences - Run
./install.shfrom the repo directory
After installation:
- Global configs: Edit
~/.claude/files directly - Create custom commands: Add
~/.claude/commands/mycommand.md - Add projects:
claude-config register <path>
Best Practices
- Commit project configs - Check in
CLAUDE.md,*-code-standard.md, and.claude/settings.local.json - Gitignore personal configs - Never commit
CLAUDE.local.md(it's for personal overrides) - Regular updates - Run
claude-config updatewhen notified - Use custom commands - Leverage
/boot,/design,/review,/commit,/handofffor better workflows - Session continuity - Use
/handoffat end of sessions,/boot .at start - Team alignment - Discuss and agree on project-level rules with your team
Git CLI Auto-Detection
Automatically works with both GitHub and GitLab:
- Detects GitHub repos ā uses
ghCLI - Detects GitLab repos ā uses
glabCLI - Natural commands: "create a PR", "list my MRs" (understands both terminologies)
- See global
CLAUDE.mdfor details
Contributing
Contributions welcome! Please ensure:
- Shell scripts pass
shellcheckvalidation - Documentation updated for new features
- Backward compatibility maintained
- Clear merge request descriptions
Adding Language Standards
- Create
project/languages/{language}-code-standard.md - Include naming, linting, testing, documentation standards
- Update
install.shlanguage selection menu - Add commented
@{language}-code-standard.mdtoproject/CLAUDE.md - Update this README
- Submit PR
Support
- Claude Code Docs: https://docs.claude.com/en/docs/claude-code
- Issues: https://gitlab.com/oldmission/claude-config/-/issues
License
MIT License - See LICENSE file for details
Related Skills
Frontend Typescript Linting.mdc
TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...
2. Apply Deepthink Protocol (reason about dependencies
risks