Documents & office · Review & audit

sync-docs

/sync-docs

Bring harness-eval's CLAUDE.md files, architecture docs, and manifests back in line with the current code. Use when the user asks to sync or audit docs, or after structural changes.

For whom

Author: whchoi98 ↗
Repository: harness-eval ↗
Licence: MIT
Last repository change: 24.09.2026

Download .zip

Paczka: 1 plik, LICENCJA-REPOZYTORIUM.txt i ZRODLO.txt z adresem źródła · 3 KB · SHA-256 17e687153343eda5…

Connect Claude to the library’s MCP server: https://sokolinski.com/skille/en/mcp (instructions).
Ask Claude: Install skill sync-docs-dc90f3
Claude will show the score, risks and files, then save the skill with your consent.

In your terminal: curl -L https://sokolinski.com/skille/en/pobierz/sync-docs-dc90f3 -o skill.zip && unzip skill.zip -d ~/.claude/skills/
For a single project, extract to .claude/skills/ inside the project directory.
Restart Claude Code and enter /sync-docs.

Assessment and security

90/ 100Class: good

Format25 / 25

Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.

Discoverability25 / 25

Description explains when to use the skill, has a reasonable length and uses third person.

Content25 / 35

At least 150 words and at most 500 lines, headings, step lists, examples or code.

Hygiene15 / 15

No placeholders such as TODO, no Windows paths, with a licence.

Riskno signals detected in the scan

Files in this package: 1
Scripts: 0
HTML comments: 0
URLs in SKILL.md: 0

Deprecation

No signals detected. Repository changed on 24.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Bring harness-eval's CLAUDE.md files, architecture docs, and manifests back in line with the current code. Use when the user asks to sync or audit docs, or after structural changes.

Original author description

Bring harness-eval's CLAUDE.md files, architecture docs, and manifests back in line with the current code. Use when the user asks to sync or audit docs, or after structural changes.

How it works

Actions

Original SKILL.md headings · 39 lines, 333 words

SKILL.md preview

---
name: sync-docs
description: Bring harness-eval's CLAUDE.md files, architecture docs, and manifests back in line with the current code. Use when the user asks to sync or audit docs, or after structural changes.
---

# Sync Docs Skill

Synchronize project documentation with current code state.

## Actions

### 1. Assess
For each CLAUDE.md, list what is wrong or stale: commands that don't run as written against the actual scripts, structure/architecture statements that no longer match, hard-coded facts (test counts, versions, file lists) that disagree with the code, and conventions the code follows that the file doesn't mention. Share this list before editing.

### 2. Root CLAUDE.md
The root CLAUDE.md is a short pointer (Overview, Structure, Installation, Development) that defers to `plugins/harness-eval/CLAUDE.md`; keep it that way. Check that its commands run as written and its structure list matches the tree. Tech Stack, Conventions and Key Commands live in the plugin CLAUDE.md (its headings are asserted by test-plugin-structure.sh).

### 3. Architecture docs
There are two: `docs/architecture.md` (monorepo view) and `plugins/harness-eval/docs/architecture.md` (plugin internals, English and Korean sections). Update whichever the change affects and keep both language sections in sync.

### 4. Module CLAUDE.md Audit
- The module directories are `scripts/`, `skills/`, `hooks/`, `templates/`, `tests/` under `plugins/harness-eval/` (the set `tests/structure/test-plugin-structure.sh` checks). Make sure each has a CLAUDE.md that matches the code; do not create CLAUDE.md in their subdirectories.
- `commands/` and `agents/` are auto-discovered, so a CLAUDE.md there registers a bogus component - their notes live in the plugin-root CLAUDE.md "Module Notes".
- Never create CLAUDE.md under `tests/fixtures/`, and never edit the existing fixture projects (they are frozen test inputs; new coverage goes in a new fixture directory).

### 5. ADR and Runbook Audit
- Check recent commits for undocumented architectural decisions
- Verify runbook coverage against project characteristics
- Flag stale ADRs and outdated runbooks

### 6. Manifest Sync (monorepo)
- `plugins/harness-eval/.claude-plugin/plugin.json` is metadata-only (no
`skills`/`agents`/`commands`/`hooks` path arrays — those are auto-discovered),
so validate the auto-discovered component directories exist instead of checking
path arrays.
- Verify version consistency across all four locations:
`plugins/harness-eval/.claude-plugin/plugin.json` (`version`),
`.claude-plugin/marketplace.json` (`metadata.version` and `plugins[].version`), and
the README version badge (`version-X.Y.Z-green.svg` near the top of `README.md`).

### 7. Report
List each file changed and what was corrected.

Versions

Repository	Score	Licence
This page · whchoi98/harness-eval	90	MIT
richkuo/rk-skills	100	MIT
OutlineDriven/outline-driven-development	100	Apache-2.0
rawbytess/hissab	100	MIT
mysticaltech/terraform-hcloud-kube-hetzner	100	MIT
joaquimscosta/arkhe-claude-plugins	100	MIT
gosuda/dalcom-skills	95	Apache-2.0
moonklabs/aiwf	90	MIT

Database snapshot: 13.11.2026 · package version 17e687153343 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

100sync-docs-site
Bring the user documentation in docs-site/ up to date with Folio's released features, from CHANGELOG.md, the README and the code. Use when the user asks to update, sync or check the docs site, after a release, or when a feature change should be reflected in the user docs.
86update-wiki
Bring the wiki in line with the code and the tree. Use after code changes that add a method, change a result, or contradict a wiki note; when a source or concept is needed by a second branch of the tree; or when the user asks to update the wiki.
100docs
Sync docs with code. Updates README, CLAUDE.md or AGENTS.md, docs/, API docs, changelog, ADRs, env examples and agent memory after a change; a drift-check mode reports mismatches without editing. Use when docs are stale, update the docs, sync README, docs out of date, after…
100skill-doc-sync
Post-ship doc sync across project markdown. Use when: sync docs, update docs, document changes, release notes.
90nth-doc-sync
Use when the user asks to check, audit, or sync documentation after a completed code, architecture, schema, workflow, or API change: finds stale, missing, duplicated, or contradictory docs and keeps each concern in one owning place. Not before the change exists, for changes…
95nacl-tl-reconcile
Emergency documentation-code reconciliation. Brings all docs in sync with current code state. Uses nacl-tl-diagnose report, fixes docs via SA skills, validates result. Use when: massive drift, docs outdated, reconcile needed, bring docs in sync, or the user says "/nacl-tl-reconcile".