tuning-labs-oss

Claude Command Center — Git skill for Claude Code

Git community intermediate

Production-tested workspace template with session hooks, structured memory (4 types), multi-domain routing, daily task tracking, and interactive /setup onboarding.

How to install Claude Command Center

This entry records only its repository, not the path inside it, so there is no exact command to give. Open tuning-labs-oss/claude-command-center and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Command Center does

[](https://github.com/tuning-labs-oss/claude-command-center/stargazers) [](https://github.com/tuning-labs-oss/claude-command-center/network/members) [](https://opensource.org/licenses/MIT) [](https://github.com/tuning-labs-oss/claude-command-center/commits/master)

Alternatives in Git

  • Clean Worktrees (Automatic) — Automatically remove all worktrees for branches merged into master 25.5k ★
  • Ccometixline - Claude Code Statusline — by Haleclipse - A high-performance Claude Code statusline tool written in Rust with Git integration, usage tra 2.3k ★
  • Codebase To Course — by Zara Zhang - A Claude Code skill that turns any codebase into a beautiful, interactive single-page HTML cou 2.1k ★

README

Claude Command Center

[](https://github.com/tuning-labs-oss/claude-command-center/stargazers) [](https://github.com/tuning-labs-oss/claude-command-center/network/members) [](https://opensource.org/licenses/MIT) [](https://github.com/tuning-labs-oss/claude-command-center/commits/master)

A production-tested template for organizing Claude Code into a multi-domain workspace with persistent memory, session continuity, daily task tracking, and intelligent onboarding.

**Built by [Tuning Labs](https://tuninglabs.net)** — battle-tested across 30+ agent swarms, 70+ tracked items, and months of daily use building a vertical SaaS platform.

What This Is

A ready-to-use template that transforms Claude Code from a simple CLI into an organized command center for your project. It includes:

  • Interactive setup interview (/setup) that configures everything from your answers
  • Session persistence — never lose context between sessions
  • Daily task tracking — persistent open items list updated every session
  • Multi-domain routing — separate contexts for coding, marketing, financial, support, ops
  • Memory system — structured knowledge base that grows with your project
  • Hook scripts — auto-save state on exit, auto-load on start, pre-commit safety checks
  • Lessons learned — perpetual log that prevents repeating mistakes

Quick Start

# 1. Clone or copy this template into your project
git clone https://github.com/YOUR_USERNAME/claude-command-center.git
cp -r claude-command-center/.claude your-project/.claude
cp claude-command-center/CLAUDE.md your-project/CLAUDE.md

# 2. Start Claude Code in your project
cd your-project
claude

# 3. Run the setup interview
/setup

The setup interview asks about your project, tech stack, preferences, and workflow in 5 stages. It generates all configuration files automatically.

What's Inside

.claude/
  hooks/
    session-start.sh    # Loads prior session state on every start

...