Sync docs
Skill Eipi-Tong/agentic-coding-starter-kit/.claude/skills/sync-docs
A reusable agentic coding starter kit (Claude Code) for web projects
npx -y skills add Eipi-Tong/agentic-coding-starter-kit --skill sync-docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Update SPEC.md and docs/DECISIONS.md to reflect recent code changes. Use after completing a feature, or when the user says "sync docs", "update the spec", or "log this decision".
SKILL.md
1.1 KB, as published. Nobody here has run it
Sync Docs Skill
When called after a feature
- Read the most recent git log (
git log --oneline -10) to identify what changed - Open
SPEC.mdand mark completed items[x] - Add a changelog entry:
| YYYY-MM-DD | <short hash> | <what changed> | - Commit:
docs(spec): mark <feature> complete [<hash>]
When called after an architectural decision
Ask the human:
- What was decided?
- Why?
- What does it affect?
Then add an ADR entry to docs/DECISIONS.md:
## ADR-<N>: <Short title>
**Date:** YYYY-MM-DD
**Status:** Accepted
**Context:** <why>
**Decision:** <what>
**Consequences:** <impact>
Commit:
docs(decisions): add ADR-<N> <short title>
Guardrails
- Never rewrite sections the human authored
- Never delete changelog entries
- Never change feature descriptions, only their status markers