Gsd Docs Update Skill for Claude

by coco-research

Generate or update project documentation verified against the codebase

565 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

196

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/coco-research/coco --skill gsd-docs-update

The instruction itself

as written by the author

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>

@$HOME/.claude/get-shit-done/workflows/docs-update.md

</execution_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>

Execute the docs-update workflow from @$HOME/.claude/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>

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take coco-research/gsd-docs-update from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.