Doc misc update
{{ ƔƔƔ }} Update an existing documentation file to reflect recent code changesFrom its SKILL.md
npx -y skills add JasonWarrenUK/goblin-mode --skill doc-misc-updateAssembled 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.
- 5 stars5 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.
SKILL.md
1.6 KB, 259 tokens by cl100k_base, as published. Nobody here has run it
Analyse recent code changes and update the specified documentation file. (For READMEs specifically, use doc-readme — this skill covers everything else: technical overviews, ADRs, guides.)
Steps
-
Resolve the doc from
$ARGUMENTS(a path, or a name to Glob for underdocs/). If nothing was given or nothing matches, ask — do not guess which doc was meant. -
Read the doc to understand its structure and style, then gather what changed in one command:
"$HOME"/.claude/library/scripts/git-doc-history.sh {doc-path} {scope-dir}Pass the code directory the doc describes as the scope (default: the doc's own directory, which is rarely right for docs living under
docs/— pick the source dir it documents). -
Identify specific updates needed: outdated sections, missing coverage of new behaviour, stale examples.
-
Generate updates preserving the existing structure; show a diff; apply on approval.
-
Update any timestamp in the doc's frontmatter.
Notes
- Match the existing documentation style; British spelling.
- Don't remove content unless it is genuinely obsolete.
- If nothing needs updating, say so plainly.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.