Syncdocs — Documentation skill for Claude Code
Agent Skill: sync a repository's docs with its code.
How to install Syncdocs
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open timerise-ai/syncdocs and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Syncdocs does
Agent Skill: sync a repository's docs with its code. Versions, dependencies, commands, structure and feature claims in README.md, CLAUDE.md, AGENTS.md and docs/ re-read from the manifest, lockfile, scripts and files, prose left alone, unverifiable claims flagged
Alternatives in Documentation
- Claude Code PM — by Ran Aroussi - Really comprehensive and feature-packed project-management workflow for Claude Code 7.7k ★
- Question — Answer the user's question by analyzing the project structure and documentation 3.4k ★
- L Docs Init — Initialize documentation for the Lowdefy monorepo - discover structure, create plan 3k ★
README
syncdocs
[](https://agentskills.io) [](https://www.skills.sh) [](https://docs.claude.com/en/docs/claude-code/skills) [](https://developers.openai.com/codex/skills) [](https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/skills.md)
An [Agent Skill](https://agentskills.io) that brings a repository's documentation back in line with its code. It syncs the facts in README.md, CLAUDE.md, AGENTS.md and `docs/` (versions, dependencies, commands, project structure and feature claims) against the repository's own manifests, lockfiles, scripts and files, in a Next.js App Router app or in any other project, and leaves the human-written prose alone.
**Every fact is re-read from the code before it is written, and nothing else is touched.** A version comes from the manifest, a command from the scripts, a tree from `ls`, a feature from the file that implements it. A claim the code can neither confirm nor refute goes to the person in the report, not into an edit.
This skill was written by the engineer who maintains it, from the documentation passes they run on their own repositories. What it carries holds by construction: every value written is one read in the same session from a manifest, lockfile, script or file; a doc keeps its own precision, so a major stays a major; one fact has one value across every doc; no doc is created and the changelog is never edited; and the report separates what changed, what was verified and what needs a decision. [`references/provenance.md`](references/provenance.md) has the record.
Install
One command, via the [skills.sh](https://www.skills.sh) CLI, which installs the
Related Skills
Create Dev Docs
Setup feature branch and development documentation structure
Sync Public Docs
Sync public VitePress documentation (docs/) with code changes — run before release or periodically on feature
J Doc Sync
Post-ship documentation sync — discover and fix stale docs after shipping changes. Use when docs may be out of
Auto Docs
Audits the entire repo for documentation drift — commands, skills, npm scripts, env vars, tech stack, and fold
Bumpv
Agent Skill: cut a Semantic Versioning release in any git repository. Find the version source, decide MAJOR, M
Framework Doctor
Read-only framework health report: inventory vs README claims, dangling cross-refs, unmanaged files in managed
Related Agents
Appsec Dependency Auditor
Use proactively for software supply chain security audits: third-party dependency risk, unpinned versions, dep
Claudemd Maintainer
AUTOMATICALLY invoke after sessions where codebase changes were made (new files, updated dependencies, changed
Mf Scout
motion-forge scout. Fast, read-mostly inventory of a motion project — assets with exact metadata, dependencies