timerise-ai

Syncdocs — Documentation skill for Claude Code

Documentation community

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

[![Agent Skills](https://img.shields.io/badge/Agent_Skills-open_format-059669)](https://agentskills.io) [![skills.sh](https://img.shields.io/badge/skills.sh-npx_skills_add-059669)](https://www.skills.sh) [![Claude Code](https://img.shields.io/badge/Claude_Code-compatible-059669)](https://docs.claude.com/en/docs/claude-code/skills) [![Codex CLI](https://img.shields.io/badge/Codex_CLI-compatible-059669)](https://developers.openai.com/codex/skills) [![Gemini CLI](https://img.shields.io/badge/Gemini_CLI-compatible-059669)](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