SteerSpec

Strspc Sync — Git skill for Claude Code

Git community

SteerSpec Sync — synchronize CLAUDE.md, agents, skills and settings across a GitHub org via PRs.

How to install Strspc Sync

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

What Strspc Sync does

SteerSpec Sync — synchronize CLAUDE.md, agents, skills and settings across a GitHub org via PRs. Go.

Alternatives in Git

Epic Sync — Sync epic issue bodies, labels, and local coordination snapshots from GitHub 243.5k ★
Superclaude — by SuperClaude-Org - A versatile configuration framework that enhances Claude Code with specialized commands 21.7k ★
Fullstack Dev Skills — by jeffallan - A comprehensive Claude Code plugin with 65 specialized skills covering full-stack development a 7k ★

README

SteerSpec Sync

Define your AI configuration once. Ship it everywhere, by pull request.

[![CI](https://github.com/SteerSpec/strspc-sync/actions/workflows/ci.yml/badge.svg)](https://github.com/SteerSpec/strspc-sync/actions/workflows/ci.yml) [![Release](https://img.shields.io/github/v/release/SteerSpec/strspc-sync)](https://github.com/SteerSpec/strspc-sync/releases) [![Go](https://img.shields.io/badge/Go-1.26+-00ADD8?logo=go&logoColor=white)](https://go.dev) [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE) [![Marketplace](https://img.shields.io/badge/Marketplace-SteerSpec%20Sync-blue?logo=github)](https://github.com/marketplace/actions/steerspec-sync)

Synchronize AI configuration files (`CLAUDE.md`, `.claude/agents/`, `.claude/skills/`, `.claude/settings.json`) across your GitHub organization. Define templates once in a central repo, then distribute them via pull requests.

How it works

Templates live in one central repo. On every run, `strspc` renders each template for each target repository, hashes the result with BLAKE3, and compares it against the recorded deployment state. Only genuine changes become pull requests — an unchanged render is skipped, so re-running is cheap and quiet.

flowchart LR
    C["Central repo
templates + steerspec-sync.yml"]
    R["Render
mustache · marker · full-replace"]
    D{"Content
changed?"}
    X["Skip"]
    P["Pull request
one per template, per repo"]
    T["Target repos
CLAUDE.md · agents · skills · settings"]
    S["Deployment state
BLAKE3 hashes"]

    C --> R --> D
    D -->|no| X
    D -->|yes| P --> T
    P --> S
    S -.->|compared on next run| D

Nothing is force-pushed and nothing is merged for you: every change lands as a reviewable PR in the target repo, titled `chore(steerspec-sync): update to ` (the type and