Automated summary
Updates project documentation in sync with code changes, including README, DECISIONS.md, and ADRs.
Strengths
- Ensures code and documentation stay consistent
- Prevents burying decisions only in chat
- Provides clear rules for what and when to update
Limitations
- Does not rewrite unrelated documentation
- May require human review for tone and clarity
- Focuses on operational docs, not user-facing manuals
When changing public behavior, commands, validation, or making durable decisions that affect the codebase.
For cosmetic or unrelated documentation improvements not tied to recent code changes.
Security analysis
SafeThe skill only provides documentation update guidelines with no executable commands, network activity, or file system modifications beyond editing docs, presenting no security risk.
No concerns found
How this analysis is madeExamples
I added a new CLI command `analyze` that takes a file path and outputs statistics. Update README.md and any relevant docs under docs/ to document this command, including usage example and output format.We decided to switch from using SQLite to PostgreSQL for the data store. Add a new decision record in docs/DECISIONS.md explaining the rationale, date, and what remains out of scope.name: docs-sync description: Use when behavior, setup, validation, public wording, data provenance, or workflow commands change and repository documentation may need to be updated.
Docs Sync
- Check
README.md,docs/DECISIONS.md, relevant docs underdocs/, and any ADRs. - Update docs in the same change as code when public behavior, commands, assumptions, or validation evidence changes.
- Record durable decisions in
docs/DECISIONS.mdor a new ADR; do not bury decisions only in chat. - Keep docs concise and operational: what changed, why, how to run it, and what remains out of scope.
- Avoid rewriting unrelated docs or changing historical decisions except to add a dated superseding note.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/docs-sync-mrwakfra/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/docs-sync-mrwakfra' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/docs-sync-mrwakfra/download' --output '.skill-downloads/docs-sync-mrwakfra/SKILL.md.part' && mv '.skill-downloads/docs-sync-mrwakfra/SKILL.md.part' '.skill-downloads/docs-sync-mrwakfra/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/docs-sync-mrwakfra/SKILL.md' && test -s '.skill-downloads/docs-sync-mrwakfra/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/docs-sync' && cp -R '.skill-downloads/docs-sync-mrwakfra' '.claude/skills/docs-sync'Cursor
test -f '.skill-downloads/docs-sync-mrwakfra/SKILL.md' && test -s '.skill-downloads/docs-sync-mrwakfra/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/docs-sync' && cp -R '.skill-downloads/docs-sync-mrwakfra' '.cursor/skills/docs-sync'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/docs-sync-mrwakfra'openskills read 'docs-sync-mrwakfra'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/docs-sync-mrwakfra/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.