📝
WritingTypeScript

Doc Sync

by fancyboi999

Doc Sync is a Writing skill for Claude Code, published by fancyboi999 in open-tag.

183 stars45 forkson fancyboi999/open-tagAdded 2026/09/06+1% in starsRepository updated 2026/08/22
agentic-workflowsagentsai-agentschatopsclaude-codeclaude-tagcodexcollaborationllmlocal-firstloop-engineeringmulti-agentopenai-codexself-hostedslack-alternativetypescriptwebsocket
Install in seconds
Install Doc Sync
Copy Doc Sync into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/fancyboi999/open-tag/tree/main/.agents/skills/doc-sync ~/.claude/skills/doc-sync

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/fancyboi999/open-tag.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
.agents/skills/doc-sync/SKILL.md in fancyboi999/open-tag
Installs to
~/.claude/skills/doc-sync
Collection
The only skill cataloged from this repository
Category
Writing1279 skills

What Doc Sync does

Doc Sync reconciles documentation with code after changes or during audits. Use it to find required doc updates, check for drift, and enforce same-commit doc changes with code.

Doc Sync is cataloged under Writing on DirSkills. Doc Sync comes from a repository tagged agentic-workflows, agents, ai-agents, chatops and claude-code.

Documentation

README

doc-sync — keep docs and code converged

This repo treats doc lag as an unfinished bug (see AGENTS.md § Doc-sync discipline). This skill is the executable procedure; the canonical mapping table (which change owes which doc) lives in AGENTS.md — read it there, do not copy it here.

This file is canonical at .agents/skills/doc-sync/SKILL.md (.claude/skills/doc-sync is a symlink). The skill itself iterates: when a run shows an instruction here is wrong or misleading, fix it in the same pass, with the run's evidence in the commit message.

Mode 1 — per-change sync (run at the end of every change)

  1. Determine the change surface. git diff --stat origin/main...HEAD (or the staged diff for uncommitted work).

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Doc Sync

  • How does Doc Sync compare to other Writing skills?

    Doc Sync ranks #1111 by stars among the 1279 Writing skills in this catalog. The most-starred ones next to it are Article Writing, Social Media Content Calendar and Knowledge Comic Creator. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Doc Sync against them. Open each page to compare what they document and how they install.