skills.rest
malkuthro
malkuthroCOMMUNITY
Explore all skills by this author →
GitHub

docs-sync

Replace version tags or node IDs across documentation, code, and manifest files.

7|2|Updated Sep 28, 2025
Search Tags:#documentation#refactoring#code#version#tag#node ID
One-click install
npx skills add https://github.com/malkuthro/ComfyUI-Koolook --skill docs-sync-malkuthro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-sync
Source: https://github.com/malkuthro/ComfyUI-Koolook/tree/main/.claude/skills/docs-sync
Command: npx skills add https://github.com/malkuthro/ComfyUI-Koolook --skill docs-sync-malkuthro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintain consistency of version tags and node identifiers throughout documentation, source code, and manifests, reducing manual errors during updates.

Core Features & Use Cases

  • Version Bumping: Update all instances of a version string when releasing a new version across docs and code repositories.
  • Identifier Propagation: Rename node IDs consistently in documentation and codebases after API or structural changes.
  • Use Case: When upgrading a fork to a new version, automatically replace all references from v2_3_3 to v2_4_0 in README files, YAML manifests, and documentation pages.

Quick Start

Run the skill with the old and new tags to update all references in your project files.

Frequently Asked Questions about docs-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synchronize version tags across documentation and code files?▼

To synchronize version tags across documentation and code files, this skill finds and replaces specified version strings in targeted file sets. It updates references in READMEs, YAML manifests, and documentation pages to ensure project-wide consistency during version releases.

What is the best way to rename node IDs in documentation and codebases after structural changes?▼

The best way to rename node IDs in documentation and codebases is to use an identifier propagation tool that performs find and replace across targeted files. This ensures consistent renaming throughout manifests and source code without requiring structural changes.

Can I preview version tag updates before modifying my project files?▼

Yes, you can preview version tag updates before modifying your project files. The skill supports a dry-run mode that allows you to safely review all planned content updates and find-and-replace actions before applying them to your documentation and code.

Does updating version strings in manifests require structural changes to the codebase?▼

No, updating version strings in manifests does not require structural changes to the codebase. The process focuses solely on content updates by finding and replacing specified tags and identifiers within the existing targeted file sets.

How do I propagate a new version string like v2_4_0 across my YAML manifests and README files?▼

To propagate a new version string like v2_4_0 across YAML manifests and README files, run the skill with the old and new tags. It will find and replace the specified version tags across your targeted documentation and code files to maintain consistency.

Related Skills

Explore More Software Engineering Skills→
PrimeIntellect-aiPrimeIntellect-ai
113

edit

Replace an exact string in a file when it occurs exactly once.

Official
Basic
webdevcodywebdevcody
22

release

Bump semver versions and generate changelog-backed annotated git tags.

Community
Advanced
fusenginefusengine
22

post-commit

Automate CHANGELOG updates, version bumps, and Git tag generation after commits.

Community
Intermediate
iOfficeAIiOfficeAI
31.8k

docx

Create and edit Word documents with tracked changes and comments.

Official
Advanced