Config Sync — 16 AI Tools, 1 Source

Sync AI coding assistant config files from a single source. Generates CLAUDE.md, AGENTS.md, GEMINI.md, .cursor/rules/, .github/copilot-instructions.md, .wind...

Security Scan

The skill's code and instructions match its stated purpose (reading a canonical .claude source and emitting multiple repo config files); it doesn't request credentials, perform networking, or do unexplained work.

Purpose & Capability

Name/description say it will read a canonical Claude rules source and generate many tool-specific config files. The included Python script only reads files under the given repository path and writes tool config files; all required file accesses and outputs align with that purpose. No unrelated binaries or credentials are requested.

Instruction Scope

SKILL.md instructs running the included Python script against a repo path; the script reads .claude/rules/ or CLAUDE.md and writes multiple config files. This is within scope, but the script will create/overwrite many files across the repo (AGENTS.md, .github/copilot-instructions.md, .kiro/..., .amazonq/..., etc.). Users should expect and review file overwrites; the tool also auto-detects existing tool files and will generate all formats by default if --tools isn't specified.

Install Mechanism

There is no install spec; this is an instruction-only skill with a bundled Python script. No packages are downloaded, no external installers invoked, and no archive extraction is performed.

Credentials

The skill requests no environment variables or credentials. The script does not access network, system credentials, or other repos; it only reads and writes files under the user-specified repository path. The 'Kiro (AWS)' description is just a label for the tool target — the script does not contact AWS or require AWS credentials.

Persistence & Privilege

always is false and the skill does not request persistent platform-wide privileges. However, it writes many files into the target repository when run, which is expected for this utility. If you allow autonomous agent invocation, the agent could run the script and modify repositories — autonomous invocation combined with write-capability increases blast radius but is an expected behavior for this kind of tool.

Assessment

This skill appears to do what it says: read .claude rules and emit many tool-specific config files. Before running it: (1) run with --dry-run to preview output; (2) commit or back up the repository (the script can overwrite many files); (3) inspect the generated headers and a few example outputs to ensure the transformations meet your expectations; (4) if you want to limit changes, use --tools to generate only the formats you need; (5) avoid running it against sensitive system folders — supply an explicit repo path. If you plan to let an agent invoke this autonomously, be aware it could modify repo files without further prompts; consider restricting autonomous execution or auditing runs.

Reads .claude/rules/ (or CLAUDE.md) as canonical source and generates native config files for every major AI coding assistant.

Problem

Each AI coding tool uses a different config file:

• Claude Code → CLAUDE.md + .claude/rules/*.md
• Codex CLI → AGENTS.md
• Gemini CLI → GEMINI.md
• Cursor → .cursor/rules/*.mdc
• GitHub Copilot → .github/copilot-instructions.md
• Windsurf → .windsurf/rules/*.md
• Cline/Roo → .clinerules/*.md
• Aider → CONVENTIONS.md
• Kiro → .kiro/steering/*.md
• Amazon Q → .amazonq/rules/*.md
• Goose → .goosehints
• Trae AI → .trae/rules/*.md
• Zed → .rules
• Amp/OpenCode/Warp → AGENTS.md (shared)

Maintaining 16 files for the same instructions is absurd. Config-sync fixes it.

How It Works

1. Source of truth: .claude/rules/*.md (most expressive format — supports glob patterns, frontmatter conditions, always/attached/triggered modes)
2. Fallback source: CLAUDE.md at repo root if .claude/rules/ doesn't exist
3. Transform: Concatenates all rule files, strips Claude-specific frontmatter, generates each format
4. Output: Only generates configs for tools you select (or all by default)

Usage

Generate all configs

python3 ~/.openclaw/skills/config-sync/scripts/config-sync.py /path/to/repo

Generate specific tools only

python3 ~/.openclaw/skills/config-sync/scripts/config-sync.py /path/to/repo --tools codex,gemini,cursor

Preview without writing

python3 ~/.openclaw/skills/config-sync/scripts/config-sync.py /path/to/repo --dry-run

Init from existing CLAUDE.md

python3 ~/.openclaw/skills/config-sync/scripts/config-sync.py /path/to/repo --init

This creates .claude/rules/ from your existing CLAUDE.md as the canonical source.

Supported Tools

Tool	Output File	Notes
Claude Code	.claude/rules/*.md (source, not generated)	Already the canonical format
Codex CLI	AGENTS.md	Flat markdown, no frontmatter
Gemini CLI	GEMINI.md	Flat markdown
Cursor	.cursor/rules/config-sync.mdc	MDC format with description + globs
GitHub Copilot	.github/copilot-instructions.md	Flat markdown
Windsurf	.windsurf/rules/config-sync.md	Flat markdown
Cline/Roo	.clinerules/config-sync.md	Flat markdown
Aider	CONVENTIONS.md	Flat markdown, concise style
Kiro	.kiro/steering/config-sync.md	Flat markdown
Amazon Q	.amazonq/rules/config-sync.md	Flat markdown
Goose	.goosehints	Line-per-rule, no markdown
Trae AI	.trae/rules/config-sync.md	Flat markdown
Zed	.rules	Flat markdown

Transformation Rules

Stripped from source

• YAML frontmatter (--- blocks) — tool-specific, not portable
• alwaysApply: true/false — Claude Code specific
• Glob patterns in frontmatter — converted to natural language headers

Added to each output

• Header comment: <!-- Generated by config-sync. Edit source at .claude/rules/ -->
• Tool-specific header if needed (e.g., MDC frontmatter for Cursor)

Format adaptations

• Goose (.goosehints): Each rule becomes one line, no markdown
• Cursor (.mdc): Gets MDC frontmatter with description and globs: **
• Aider (CONVENTIONS.md): Condensed to bullet points, no long explanations
• AGENTS.md: Standard markdown, used by Codex/Amp/OpenCode/Warp (4 tools, 1 file)

Workflow

1. Edit .claude/rules/*.md (your canonical source)
2. Run config-sync to generate all other formats
3. Commit all generated files together
4. Repeat when rules change

Auto-detect installed tools

The script checks for:

• .cursor/ directory → Cursor installed
• .github/copilot-instructions.md exists → Copilot in use
• .windsurf/ → Windsurf installed
• .clinerules/ → Cline installed
• .kiro/ → Kiro installed
• .amazonq/ → Amazon Q installed
• .trae/ → Trae installed
• AGENTS.md exists → Codex/Amp/OpenCode in use
• GEMINI.md exists → Gemini CLI in use

If --tools is not specified, generates all formats (belt-and-suspenders approach).

Philosophy

One source of truth. Many outputs. Like a compiler: write once in the richest language, emit to every target.