skillshare-update-docs
Update website docs to match recent code changes, cross-validating every flag against source. Use this skill whenever the user asks to: update documentation, sync docs with code, document a new flag or command, fix stale docs, or update the README. This skill covers all website/docs/ categories (commands, reference, understand, how-to, troubleshooting, getting-started) plus the built-in skill description and README. If you just implemented a feature and need to update docs, this is the skill to use. Never manually edit website docs without cross-validating flags against Go source first.
npx skills add runkids/skillshare --skill skillshare-update-docs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Sync website documentation with recent code changes. $ARGUMENTS specifies scope: a command name (e.g., `install`), commit range, or omit to auto-detect from `git diff HEAD~1`. **Scope**: This skill only updates `website/docs/`. It does NOT write Go code (use `implement-feature`) or CHANGELOG (use `changelog`). ## Workflow ### Step 1: Detect Changes ```bash # Auto-detect recently changed code git diff HEAD~1 --stat -- cmd/skillshare/ internal/ # Also check for structural changes that affect concept/reference docs git diff HEAD~1 --stat -- internal/config/targets.yaml internal/audit/rules.yaml ``` Map changed files to affected documentation using this guide: **Command docs** (`website/docs/reference/commands/`): - `cmd/skillshare/<cmd>.go` → `website/docs/reference/commands/<cmd>.md` - Flag changes, new subcommands, output format changes **Concept docs** (`website/docs/understand/`): - `internal/audit/` → `understand/audit-engine.md` - `internal/sync/` → `understand/sync-modes.md`, `understand/source-and-targets.md` - `internal/install/tracked.go` → `understand/tracked-repositories.md` - `internal/config/` → `understand/declarative-manifest.md` - `.skillshare/` project config changes
- Workflow
- Step 1: Detect Changes
- Step 2: Cross-Validate Flags
- Step 3: Update Documentation
- Step 4: Check Built-in Skill
- Step 5: Check README
- Step 6: Build Verification
- Step 7: Report
- Rules
Auto-detect recently changed code git diff HEAD~1 --stat -- cmd/skillshare/ internal/ Also check for structural changes that affect concept/reference docs git diff HEAD~1 --stat -- internal/config/targets.yaml internal/audit/rules.yaml grep -n 'flag\.\|Usage\|Args' cmd/skillshare/<cmd>.go cd website && npm run build
What does the skillshare-update-docs skill do?
Update website docs to match recent code changes, cross-validating every flag against source. Use this skill whenever the user asks to: update documentation, sync docs with code, document a new flag or command, fix stale docs, or update the README. This skill covers all website/docs/ categories (commands, reference, understand, how-to, troubleshooting, getting-started) plus the built-in skill description and README. If you just implemented a feature and need to update docs, this is the skill to use. Never manually edit website docs without cross-validating flags against Go source first.
How do I install it?
Run `npx skills add runkids/skillshare --skill skillshare-update-docs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From runkids/skillshare, a repository with 2,519 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.