GS

gsd-docs-update

Generates and validates project documentation directly against the source code to prevent drift.

Install

mkdir -p .claude/skills/gsd-docs-update && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15297" && unzip -o skill.zip -d .claude/skills/gsd-docs-update && rm skill.zip

Installs to .claude/skills/gsd-docs-update

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Generate or update project documentation verified against the codebase
70 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Generate project documentation
  • Update existing documentation files
  • Verify documentation accuracy against codebase
  • Handle `--force` flag for regeneration
  • Handle `--verify-only` flag for accuracy checks

How it works

The skill executes a documentation-update workflow, invoking a subagent to explore the codebase and generate or update documentation files based on the provided flags.

Inputs & outputs

You give it
Project codebase, optional flags (--force, --verify-only)
You get back
Updated documentation files or verification report

When to use gsd-docs-update

  • Updating stale README files
  • Generating API reference docs
  • Verifying documentation accuracy

About this skill

<objective> Generate and update up to 9 documentation files for the current project. Each doc type is written by a gsd-doc-writer subagent that explores the codebase directly — no hallucinated paths, phantom endpoints, or stale signatures.

Flag handling rule:

  • The optional flags documented below are available behaviors, not implied active behaviors
  • A flag is active only when its literal token appears in $ARGUMENTS
  • If a documented flag is absent from $ARGUMENTS, treat it as inactive
  • --force: skip preservation prompts, regenerate all docs regardless of existing content or GSD markers
  • --verify-only: check existing docs for accuracy against codebase, no generation (full verification requires Phase 4 verifier)
  • If --force and --verify-only both appear in $ARGUMENTS, --force takes precedence </objective>

<execution_context> @.github/get-shit-done/workflows/docs-update.md </execution_context>

<context> Arguments: $ARGUMENTS

Available optional flags (documentation only — not automatically active):

  • --force — Regenerate all docs. Overwrites hand-written and GSD docs alike. No preservation prompts.
  • --verify-only — Check existing docs for accuracy against the codebase. No files are written. Reports VERIFY marker count. Full codebase fact-checking requires the gsd-doc-verifier agent (Phase 4).

Active flags must be derived from $ARGUMENTS:

  • --force is active only if the literal --force token is present in $ARGUMENTS
  • --verify-only is active only if the literal --verify-only token is present in $ARGUMENTS
  • If neither token appears, run the standard full-phase generation flow
  • Do not infer that a flag is active just because it is documented in this prompt </context>
<process> Execute the docs-update workflow from @.github/get-shit-done/workflows/docs-update.md end-to-end. Preserve all workflow gates (preservation_check, flag handling, wave execution, monorepo dispatch, commit, reporting). </process>

When not to use it

  • When only a full verification by gsd-doc-verifier agent is needed
  • When flags are not explicitly provided in arguments
  • When the user wants to infer flag activity

Limitations

  • Full verification requires the gsd-doc-verifier agent (Phase 4).
  • A flag is active only when its literal token appears in `$ARGUMENTS`.
  • If `--force` and `--verify-only` both appear in `$ARGUMENTS`, `--force` takes precedence.

How it compares

This skill ensures documentation accuracy by directly exploring the codebase, which is more reliable than manual updates that might introduce inconsistencies or stale information.

Compared to similar skills

gsd-docs-update side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gsd-docs-update (this skill)03moNo flagsIntermediate
korean-skill-creator89moReviewBeginner
skill-forge119moReviewIntermediate
svelte-expert119moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

korean-skill-creator

clwmfksek

한글 기반 클로드 스킬 자동 생성 도구. 사용자가 "클로드 스킬을 만들어줘" 또는 "[요구사항] 스킬 만들어줘"라고 요청할 때 사용. Progressive disclosure 원칙을 따르는 한글 문서 구조(SKILL.md + references/)를 자동으로 생성하고, 실전 예시를 포함한 일관성 있는 스킬 템플릿을 제공.

8132

skill-forge

WilliamSaysX

Automated skill creation workshop with intelligent source detection, smart path management, and end-to-end workflow automation. This skill should be used when users want to create a new skill or convert external resources (GitHub repositories, online documentation, or local directories) into a skill. Automatically fetches, organizes, and packages skills with proactive cleanup management.

11115

svelte-expert

Raudbjorn

Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.

11107

build-free-types

paulirish

This skill should be used when the user asks to "set up types without a build step", "use vanilla JS with types", "configure erasable syntax", or mentions "JSDoc type checking". It provides instructions for modern type safety using JSDoc in browsers and native TypeScript execution in Node.js.

95

vscode-ext-commands

github

Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices

23

project-bootstrapper

mhattingpete

Sets up new projects or improves existing projects with development best practices, tooling, documentation, and workflow automation. Use when user wants to start a new project, improve project structure, add development tooling, or establish professional workflows.

12

Search skills

Search the agent skills registry