sync-docs
Skill1 starsChanged 5 months agoApache-2.0View on GitHub
Update the published docs.memoturn.ai pages (docs/site) to match product changes since the last sync — env vars, CLI, HTTP API, MCP tools, SDKs, Helm.
22 other projects use a version of this.
Adopted by
Most recently taken up by
- richkuo/rk-skillstheir own version, first seen Nov 8, 2026
- Kangentic/kangentictheir own version, first seen Nov 7, 2026
- TanKaizokuO/claude-skillstheir own version, first seen Oct 20, 2026
- yokeloop/yoketheir own version, first seen Oct 9, 2026
- kube-hetzner/terraform-hcloud-kube-hetznertheir own version, first seen Oct 8, 2026
- ayutaz/piper-plustheir own version, first seen Oct 8, 2026
Used with
Projects with it also use prepare-release, review-pr and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ShopifySkillprepare-release
Prepare the changeset-release/main branch for release by syncing version.ts files and running pnpm install
Also in 4 projects that use this
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 3 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
- MicrosoftSkill
handoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- kube-hetzner/terraform-hcloud-kube-hetzner★ 3.9ksame name
- mysticaltech/terraform-hcloud-kube-hetzner★ 3.9ksame name
- onevcat/Prowl★ 673same name
- ayutaz/piper-plus★ 240same name
- joshzyj/open-scholar-skill★ 177same name
- Kangentic/kangentic★ 140same name
- guess/claude_code★ 96same name
- richkuo/rk-skills★ 50same name
- jiahao-shao1/sjh-skills★ 43same name
- phj128/autoworker★ 18same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 41
Update the mapped pages. Match each page's existing customer-facing voice.
- Very specific: line 45
Update the marker: git rev-parse HEAD > docs/site/.docs-sync.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product changes since last sync
Last synced commit: !cat docs/site/.docs-sync
git log --oneline $(cat docs/site/.docs-sync)..HEAD -- crates/ mcp/ sdk/ deploy/ examples/
git diff --stat $(cat docs/site/.docs-sync)..HEAD -- crates/ mcp/ sdk/ deploy/ examples/Task
Bring the published docs pages in docs/site/src/content/docs/ up to date with the changes
above. If the log is empty, say so and stop.
Page map — which source surfaces feed which pages:
| Changed surface | Pages to check |
MEMOTURN_* env vars (crates/memoturnd/src/main.rs) | configuration.md, security.md |
CLI commands/flags (crates/cli/src/main.rs) | cli.md, quickstart.mdx |
HTTP routes / auth (crates/api) | api-rest.md, security.md, consistency.md, errors.md, docs/api/openapi.yaml (drift test: cargo test -p memoturn-api openapi) |
Error codes / startup refusals (crates/api/src/error.rs, crates/memoturnd) | errors.md, troubleshooting.md |
Assistant / ask (crates/api/src/answer.rs, mcp/src) | ask.md, mcp.md |
PITR / GC / retention (crates/replication, MEMOTURN_PITR_*) | pitr.md, configuration.md |
MCP tools (mcp/src) | mcp.md |
SDKs (sdk/typescript, sdk/python) | sdk-typescript.md, sdk-python.md |
Helm chart / K8s (deploy/helm) | deployment.md, scaling.md, observability.md |
Memory semantics (crates/docstore, esp. memories.rs) | memories.md, recall.md, profiles.md, data-model.md |
Branching/replication (crates/replication) | branching.md, consistency.md, architecture.md |
Process:
- For each commit above, read the actual diff to learn what the surface change was — don't guess from the commit message.
- Update the mapped pages. Match each page's existing customer-facing voice; these pages are
rewritten product prose, not copies of
docs/architecture/. Never name competitors.docs/architecture/anddocs/adr/are background reading, never sources to copy from. - Validate:
cd docs/site && npm run buildmust pass. - Update the marker:
git rev-parse HEAD > docs/site/.docs-sync. - Report: pages changed and why, plus anything needing a human call (pricing, roadmap, positioning claims) — flag those instead of writing them.
Deploying is a separate, user-triggered step (cd docs/site && npm run deploy) — do not deploy.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.