Agent skill

Release Docs Sync

by UfoMiao in UfoMiao/zcf

Compares code changes since the last Git tag with the multilingual docs and CLAUDE.md, then updates them or only reports mismatches with --check-only.

MITAuto-check passedDevelopment

Install Release Docs Sync

skills CLI
$ npx skills add UfoMiao/zcf --skill zcf-update-docs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install UfoMiao/zcf zcf-update-docs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/UfoMiao/zcf.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/zcf-update-docs .claude/skills/zcf-update-docs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
zcf-update-docs
GitHub stars
6.1k
Token cost
~4k tokens
SKILL.md length
822 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Compares code changes since the last Git tag with the multilingual docs and CLAUDE.md, then updates them or only reports mismatches with --check-only.

  • Works in 10 steps: Parameter Parsing → Get Changes Since Last Tag → Identify Documentation Update Areas → …
  • Refreshing documentation before cutting a release
  • SKILL.md covers Usage, Parameters, Context and Your Role, plus 3 more sections
  • Calls git

What it does

Built for the ZCF repository, this skill finds every code change since the last Git tag and checks whether the documentation still matches. It covers the docs folder in English, Simplified Chinese and Japanese, plus CLAUDE.md for development-related changes.

A mapping ties source files to doc pages: files under src/commands go to the matching CLI pages such as init, menu, update and uninstall, while installer and config utilities, Codex tooling and the workflows config go to feature pages. The agent decides which pages need edits, updates all three languages so they stay in sync, and with the --check-only flag reports inconsistencies without changing anything.

When your agent uses it

  • Refreshing documentation before cutting a release
  • Checking whether docs drifted from the CLI after code changes
  • Keeping English, Chinese and Japanese pages in sync
  • Updating CLAUDE.md after development workflow changes

Example prompts

  • “Run /zcf-update-docs --check-only and list the pages that are out of date.”
  • “Update the docs for the commands that changed since the last tag.”
  • “Sync the Japanese and Chinese CLI pages with the English ones.”
  • “Does CLAUDE.md still describe the current build setup?”

Requirements

  • A Git repository with at least one release tag
  • The ZCF docs layout with en, zh-CN and ja-JP folders
  • Pre-approved tools (allowed-tools): Read(**), Exec(git, cat, grep, diff)

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Parameter Parsing
  2. Get Changes Since Last Tag
  3. Identify Documentation Update Areas
  4. Check Current Documentation
  5. Verify CLI Commands Consistency
  6. Verify Features Documentation
  7. Generate Update Report
  8. Update Documentation Files
  9. Validation
  10. Summary Report

What it can do on your machine

Read from SKILL.md and the folder at commit 63cb2d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read(**)
    • Exec(git
    • cat
    • grep
    • diff)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Docs Sync loads about 4k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 822 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from UfoMiao/zcf at commit 63cb2d0, republished under its MIT licence (© UfoMiao). 822 words, ~3,958 tokens.

Download SKILL.mdSave it as .claude/skills/zcf-update-docs/SKILL.md (or your agent's skills folder).
name
zcf-update-docs
description
Automatically check code changes since last tag and update documentation in docs/ directory (en, zh-CN, ja-JP) and CLAUDE.md to ensure consistency with actual code implementation
allowed-tools
Read(**), Exec(git, cat, grep, diff)
disable-model-invocation
true

ZCF Update Docs - Documentation Synchronization

Automatically check code changes since last tag and update documentation in docs/ directory (multilingual: en, zh-CN, ja-JP) and CLAUDE.md to ensure consistency with actual code implementation.

Usage

bash
/zcf-update-docs [--check-only]

Parameters

  • --check-only: Only check for inconsistencies without making updates (dry run)

Context

  • Analyze all code changes since the last Git tag
  • Check if documentation needs updates in docs/ directory structure
  • Ensure CLI commands, features, and workflows documentation match actual code
  • Maintain multilingual documentation consistency across en, zh-CN, ja-JP
  • Update CLAUDE.md for development-related changes

Your Role

You are a professional documentation maintainer responsible for:

  1. Analyzing code changes and their impact on documentation
  2. Identifying documentation sections that need updates
  3. Ensuring documentation accuracy and consistency
  4. Maintaining multilingual synchronization

Execution Flow

Parse arguments: $ARGUMENTS

1. Parameter Parsing
bash
CHECK_ONLY=false  # Default to update mode

case "$ARGUMENTS" in
  --check-only)
    CHECK_ONLY=true
    echo "📋 Running in check-only mode (no files will be modified)"
    ;;
  "")
    CHECK_ONLY=false
    echo "✏️ Running in update mode"
    ;;
  *)
    echo "Unknown parameter: $ARGUMENTS"
    echo "Usage: /zcf-update-docs [--check-only]"
    exit 1
    ;;
esac
2. Get Changes Since Last Tag

Analyze all changes since the last release:

bash
# Get last release tag
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")

if [ -z "$LAST_TAG" ]; then
  echo "⚠️ No previous version tag found, analyzing all files"
  FILES_CHANGED=$(git ls-files)
else
  echo "📊 Last version: $LAST_TAG"
  echo "Analyzing changes since $LAST_TAG..."
  FILES_CHANGED=$(git diff --name-only $LAST_TAG..HEAD)
fi

# Categorize changed files
echo -e "\n📁 Analyzing changed files..."
3. Identify Documentation Update Areas

Based on file changes, determine which documentation files in docs/ need updates:

Code Changes → Documentation Mapping:

  1. CLI Commands (src/commands/*.ts) → docs/{lang}/cli/

    • src/commands/init.ts → cli/init.md - Installation and initialization
    • src/commands/menu.ts → cli/menu.md - Interactive menu system
    • src/commands/update.ts → cli/update.md - Update workflows
    • src/commands/ccr.ts → cli/ccr.md - CCR proxy management
    • src/commands/ccu.ts → cli/ccu.md - Usage analysis
    • src/commands/uninstall.ts → cli/uninstall.md - Uninstallation
    • src/commands/config-switch.ts → cli/config-switch.md - Config switching
    • src/commands/check-updates.ts → cli/check-updates.md - Version check
  2. Features → docs/{lang}/features/

    • src/utils/installer.ts, src/utils/claude-config.ts → features/claude-code.md
    • src/utils/code-tools/codex* → features/codex.md
    • src/config/workflows.ts → features/workflows.md
    • src/config/mcp-services.ts → features/mcp.md
    • src/utils/ccr/ → features/ccr.md
    • src/utils/cometix/ → features/cometix.md
    • src/utils/config.ts → features/multi-config.md
  3. Workflows (src/config/workflows.ts, templates/*/workflow/) → docs/{lang}/workflows/

    • Workflow definitions → workflows/index.md
    • Specific workflow templates → workflows/{workflow-name}.md
  4. Advanced Configuration → docs/{lang}/advanced/

    • src/types/config.ts, src/utils/config.ts → advanced/configuration.md
    • src/config/api-providers.ts → advanced/api-providers.md
    • templates/ → advanced/templates.md
    • src/i18n/ → advanced/i18n.md
  5. Getting Started → docs/{lang}/getting-started/

    • src/commands/init.ts, src/utils/installer.ts → getting-started/installation.md
    • General introduction → getting-started/index.md
  6. Development → docs/{lang}/development/ and CLAUDE.md

    • Architecture changes → development/architecture.md + CLAUDE.md
    • Testing changes → development/testing.md + CLAUDE.md
    • Contributing guidelines → development/contributing.md
    • Package.json scripts → CLAUDE.md
4. Check Current Documentation

Read and analyze current documentation structure:

bash
# Check if documentation directories exist
DOCS_LANGS=("en" "zh-CN" "ja-JP")
DOCS_CATEGORIES=(
  "getting-started"
  "cli"
  "features"
  "workflows"
  "advanced"
  "best-practices"
  "development"
)

echo "📁 Checking documentation structure..."

for LANG in "${DOCS_LANGS[@]}"; do
  if [ ! -d "docs/$LANG" ]; then
    echo "❌ Warning: docs/$LANG directory not found"
  else
    echo "✅ Found: docs/$LANG/"
    for CATEGORY in "${DOCS_CATEGORIES[@]}"; do
      if [ ! -d "docs/$LANG/$CATEGORY" ]; then
        echo "  ⚠️  Missing category: $CATEGORY"
      else
        echo "  ✅ Category: $CATEGORY"
      fi
    done
  fi
done

# Check CLAUDE.md
if [ ! -f "CLAUDE.md" ]; then
  echo "❌ Warning: CLAUDE.md not found"
else
  echo "✅ Found: CLAUDE.md"
fi
5. Verify CLI Commands Consistency

Compare CLI commands implementation with documentation:

Check Points:

  • Command names, options, and parameters
  • Command descriptions and usage examples
  • Interactive menu options and flow
  • Keyboard shortcuts and navigation
  • Exit and back options
  • Multilingual prompt translations

Code Sources → Documentation Files:

  • src/commands/menu.ts, src/i18n/locales/*/menu.json → docs/{lang}/cli/menu.md
  • src/commands/init.ts, src/i18n/locales/*/cli.json → docs/{lang}/cli/init.md
  • src/commands/update.ts → docs/{lang}/cli/update.md
  • src/commands/ccr.ts → docs/{lang}/cli/ccr.md
  • src/commands/ccu.ts → docs/{lang}/cli/ccu.md
  • src/commands/uninstall.ts → docs/{lang}/cli/uninstall.md
  • src/commands/config-switch.ts → docs/{lang}/cli/config-switch.md
  • src/commands/check-updates.ts → docs/{lang}/cli/check-updates.md
6. Verify Features Documentation

Ensure features documentation matches actual implementation:

Check Points:

  1. Claude Code configuration capabilities
  2. Codex CLI integration and setup
  3. Workflow system and categories
  4. MCP service integration
  5. CCR proxy management
  6. Cometix status line
  7. Multi-config and backup system
  8. API provider presets

Code Sources → Documentation Files:

  • src/utils/installer.ts, src/utils/claude-config.ts → docs/{lang}/features/claude-code.md
  • src/utils/code-tools/codex*.ts, templates/codex/ → docs/{lang}/features/codex.md
  • src/config/workflows.ts → docs/{lang}/features/workflows.md
  • src/config/mcp-services.ts → docs/{lang}/features/mcp.md
  • src/utils/ccr/ → docs/{lang}/features/ccr.md
  • src/utils/cometix/ → docs/{lang}/features/cometix.md
  • src/utils/config.ts → docs/{lang}/features/multi-config.md
7. Generate Update Report

Create a detailed report of findings:

markdown
## Documentation Update Report

### Files Changed Since $LAST_TAG
- [List of relevant changed files categorized by module]

### Documentation Files Requiring Updates

#### docs/en/ (English Documentation)
- [ ] getting-started/installation.md - Installation and setup
- [ ] cli/*.md - CLI command documentation
- [ ] features/*.md - Feature descriptions
- [ ] workflows/*.md - Workflow guides
- [ ] advanced/*.md - Advanced configuration
- [ ] development/*.md - Development documentation

#### docs/zh-CN/ (Chinese Documentation)
- [ ] getting-started/installation.md - 安装和设置
- [ ] cli/*.md - CLI 命令文档
- [ ] features/*.md - 功能说明
- [ ] workflows/*.md - 工作流指南
- [ ] advanced/*.md - 高级配置
- [ ] development/*.md - 开发文档

#### docs/ja-JP/ (Japanese Documentation)
- [ ] getting-started/installation.md - インストールとセットアップ
- [ ] cli/*.md - CLI コマンドドキュメント
- [ ] features/*.md - 機能説明
- [ ] workflows/*.md - ワークフローガイド
- [ ] advanced/*.md - 高度な設定
- [ ] development/*.md - 開発ドキュメント

#### CLAUDE.md (Root Development Documentation)
- [ ] Development commands (package.json scripts)
- [ ] Architecture and module structure
- [ ] Testing guidelines and coverage
- [ ] Workflow system implementation
- [ ] Code standards and conventions

### Specific Inconsistencies Found
[Detailed list of mismatches between code and documentation, organized by file]
8. Update Documentation Files

If not in check-only mode, update the documentation:

bash
if [ "$CHECK_ONLY" = false ]; then
  echo "📝 Updating documentation files in docs/ directory..."
  
  # Update docs/en/ (English Documentation)
  # - CLI commands: Update docs/en/cli/*.md based on src/commands/*.ts
  # - Features: Update docs/en/features/*.md based on feature implementations
  # - Workflows: Update docs/en/workflows/*.md based on src/config/workflows.ts
  # - Getting Started: Update docs/en/getting-started/*.md based on installation flow
  # - Advanced: Update docs/en/advanced/*.md based on configuration and templates
  # - Development: Update docs/en/development/*.md based on architecture changes
  # - Use translations from src/i18n/locales/en/*.json
  
  # Update docs/zh-CN/ (Chinese Documentation)
  # - Maintain same structure and sections as English version
  # - Use proper Chinese translations from src/i18n/locales/zh-CN/*.json
  # - Update all corresponding CLI, features, workflows, etc.
  # - Ensure technical terms and examples are properly localized
  
  # Update docs/ja-JP/ (Japanese Documentation)
  # - Maintain same structure and sections as English version
  # - Use proper Japanese translations (maintain consistency with project style)
  # - Update all corresponding CLI, features, workflows, etc.
  # - Ensure proper Japanese formatting and terminology
  
  # Update CLAUDE.md (Root Development Documentation)
  # - Update development commands if package.json scripts changed
  # - Update architecture section if new modules added
  # - Update testing section if test structure changed
  # - Update workflow system if src/config/workflows.ts changed
  # - Update module index if directory structure changed
  # - Maintain English-only for development documentation
  
  # Update SUMMARY.md for each language
  # - Ensure table of contents matches actual file structure
  # - Update links if files were added/removed/renamed
  # - Maintain consistent ordering across all languages
  
  echo "✅ Documentation files updated in docs/ directory"
else
  echo "ℹ️ Check-only mode: No files were modified"
fi
9. Validation

Perform final validation checks:

bash
echo -e "\n🔍 Performing validation checks..."

# Check for broken internal links in all language versions
echo "Checking internal links in docs/en/, docs/zh-CN/, docs/ja-JP/..."

# Verify SUMMARY.md matches actual file structure
echo "Validating SUMMARY.md table of contents..."

# Ensure structure consistency across languages
echo "Checking structural consistency across en, zh-CN, ja-JP..."

# Verify code examples still work
echo "Verifying code examples and command syntax..."

# Validate markdown formatting
echo "Validating markdown format..."

# Check translation completeness
echo "Checking multilingual translation completeness..."

# Verify CLI command documentation matches implementation
echo "Verifying CLI command documentation accuracy..."

# Validate feature documentation completeness
echo "Checking feature documentation coverage..."

echo "✅ Validation complete"
10. Summary Report

Generate final summary:

bash
echo -e "\n📊 Documentation Update Summary"
echo "================================"
echo "Files analyzed: [count]"
echo "Documentation files updated: [list]"
echo "Sections modified: [count]"
echo ""
echo "Key updates:"
echo "- [List major updates]"
echo ""
if [ "$CHECK_ONLY" = true ]; then
  echo "📋 This was a check-only run. To apply updates, run without --check-only"
else
  echo "✅ Documentation has been synchronized with code"
  echo "📝 Please review the changes before committing"
fi

Documentation Structure Reference

Show full SKILL.md (371 more words)Show less
docs/{lang}/ Directory Structure (en, zh-CN, ja-JP)

Each language directory contains the following categories:

  1. getting-started/ - Installation and quick start

    • index.md - Quick start guide
    • installation.md - Installation guide (Must match src/commands/init.ts)
  2. cli/ - CLI command documentation

    • index.md - Commands overview
    • init.md, update.md, menu.md, etc. (Must match src/commands/*.ts)
  3. features/ - Feature descriptions

    • index.md - Features overview
    • claude-code.md, codex.md, workflows.md, etc. (Must match implementations)
  4. workflows/ - Workflow guides

    • index.md - Workflow overview
    • Specific workflow documentation (Must match src/config/workflows.ts)
  5. advanced/ - Advanced configuration

    • configuration.md, api-providers.md, templates.md, etc.
  6. best-practices/ - Best practices and tips

    • Usage tips and optimization strategies
  7. development/ - Development documentation

    • architecture.md, contributing.md, testing.md
  8. SUMMARY.md - Table of contents for each language

CLAUDE.md Structure (Root Development Documentation)
  1. Project Overview
  2. Architecture Overview (Must match actual module structure)
  3. Module Index (Must match src/ directory structure)
  4. CLI Usage
  5. Running and Development (Must match package.json scripts)
  6. Development Guidelines
  7. Testing Strategy
  8. AI Team Configuration

Important Notes

⚠️ Critical Requirements:

  • ALWAYS ensure CLI command documentation matches actual implementation in src/commands/
  • ALWAYS verify feature descriptions match actual code behavior
  • ALWAYS maintain structural consistency across all language versions (en, zh-CN, ja-JP)
  • ALWAYS update SUMMARY.md when file structure changes
  • NEVER remove existing content without verification
  • NEVER break markdown formatting or internal links
  • NEVER create inconsistency between language versions

📌 Best Practices:

  • Use actual i18n translations from src/i18n/locales/{lang}/*.json
  • Preserve existing formatting and style conventions
  • Update code examples to reflect current implementation
  • Include new features and commands added since last tag
  • Remove or mark deprecated features that no longer exist
  • Maintain parallel structure across en, zh-CN, ja-JP directories
  • Keep CLAUDE.md focused on development-specific information

🔍 Validation Checklist:

  • CLI command docs match src/commands/*.ts implementation
  • Feature docs match actual feature implementations
  • Workflow docs match src/config/workflows.ts definitions
  • Installation guide matches src/commands/init.ts flow
  • Configuration docs match types in src/types/*.ts
  • MCP service docs match src/config/mcp-services.ts
  • Structure consistency across en, zh-CN, ja-JP directories
  • SUMMARY.md matches actual file structure for each language
  • All internal links are valid and not broken
  • Code examples and command syntax are correct
  • Translations use proper i18n strings from codebase
  • Markdown formatting is valid in all files
  • Codex integration documentation is comprehensive
  • CCR, Cometix, CCusage features are accurately documented
  • API provider presets documentation is up-to-date
  • CLAUDE.md reflects current architecture and development practices

Now starting documentation update process...

© UfoMiao, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/zcf-update-docs of UfoMiao/zcf.

Open the folder on GitHubat commit 63cb2d0

Compare with similar skills

Release Docs Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Docs Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Docs Sync this skillUfoMiao/zcf6.1k—~4kAutomated safety check: PassMIT
CommitLennartHennigs/Button2565—~562Automated safety check: PassMIT
CommitLennartHennigs/ESPRotary188—~590Automated safety check: PassMIT
Sync Docsayutaz/piper-plus230—~1.4kAutomated safety check: PassMIT
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
NeMo Curator Docs MaintenanceNVIDIA-NeMo/Curator1.8k—~4.3kAutomated safety check: PassApache-2.0

Similar skills

  • Commit

    LennartHennigs/Button2

    Stage and commit current changes for Button2 — checks for needed CHANGELOG/README/CLAUDE.md updates, creates a branch if on master, writes a commit message, and commits

    565 GitHub stars~562 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Commit

    LennartHennigs/ESPRotary

    Stage and commit current changes for ESPRotary — checks for needed CHANGELOG/README/CLAUDE.md updates, creates a branch if on master, writes a commit message, and commits

    188 GitHub stars~590 tokensUpdated 2 mo ago
    DevelopmentAuto-check passed
  • Sync Docs

    ayutaz/piper-plus

    コミット前にエージェントチームで全ドキュメント (CLAUDE.md / README / CHANGELOG / docs/) を監査し、コード変更に応じて自動更新します。大規模変更時の documentation drift を予防。

    230 GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check passed
  • Adds, updates, moves and removes pages on the NeMo Curator Fern documentation site, keeping navigation entries, links and redirects in step.

    1.8k GitHub stars~4.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Maintain DDNS VitePress documentation with bilingual parity, correct navigation and links, safe executable-doc changes, and build verification.

    4.7k GitHub stars~324 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from UfoMiao/zcf

  • Onboards a corporate sponsor to ZCF by listing it in the three READMEs, and optionally registers its API preset and places ad cards in docs.

    6.1k GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Analyzes the current branch's changes since it diverged from base and opens a pull request through the GitHub CLI with an auto-generated, standardized description.

    6.1k GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Release Docs Sync

What does Release Docs Sync do?

Compares code changes since the last Git tag with the multilingual docs and CLAUDE.md, then updates them or only reports mismatches with --check-only. Built for the ZCF repository, this skill finds every code change since the last Git tag and checks whether the documentation still matches.md for development-related changes.

When should I use Release Docs Sync?

Release Docs Sync fits situations like: refreshing documentation before cutting a release; checking whether docs drifted from the CLI after code changes; keeping English, Chinese and Japanese pages in sync; updating CLAUDE.md after development workflow changes.

How do I install Release Docs Sync in Claude Code?

Run `npx skills add UfoMiao/zcf --skill zcf-update-docs -a claude-code`. Or copy the skill folder (.claude/skills/zcf-update-docs in UfoMiao/zcf) into .claude/skills/zcf-update-docs in your project. Claude Code loads it when a task matches its description.

How do I install Release Docs Sync in Codex?

Run `npx skills add UfoMiao/zcf --skill zcf-update-docs -a codex`. Or copy the skill folder (.claude/skills/zcf-update-docs in UfoMiao/zcf) into .agents/skills/zcf-update-docs in your project. Codex loads it when a task matches its description.

Can I use Release Docs Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add UfoMiao/zcf --skill zcf-update-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/zcf-update-docs, .gemini/skills/zcf-update-docs, .github/skills/zcf-update-docs and .opencode/skills/zcf-update-docs in your project.

What does Release Docs Sync need to run?

Going by SKILL.md and its folder, Release Docs Sync needs the command-line tools its instructions call (git). Our summary lists: A Git repository with at least one release tag; The ZCF docs layout with en, zh-CN and ja-JP folders. Its frontmatter pre-approves these tools: Read(**), Exec(git, cat, grep, diff).

Does Release Docs Sync access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release Docs Sync safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Docs Sync use?

Release Docs Sync is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Docs Sync use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Docs Sync?

Skills that share tags, products or a category with Release Docs Sync: Commit (LennartHennigs/Button2, 565 stars), Commit (LennartHennigs/ESPRotary, 188 stars), Sync Docs (ayutaz/piper-plus, 230 stars) and Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Docs Sync?

UfoMiao (a GitHub organization) maintains it in UfoMiao/zcf, which has 6,079 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on August 31, 2026.

Source: UfoMiao/zcf on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.