New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Docouture Documenting Changes

by InditexTech in InditexTech/weavejs

How to update an existing docouture documentation site when a feature, change, deprecation or fix lands in the repo — figuring out what's affected from a diff/commit/PR, confirming with the user…

Apache-2.0Auto-check passedAgent Workflows

Install Docouture Documenting Changes

skills CLI
$ npx skills add InditexTech/weavejs --skill docouture-documenting-changes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install InditexTech/weavejs docouture-documenting-changes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/InditexTech/weavejs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/docouture-documenting-changes .claude/skills/docouture-documenting-changes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
docouture-documenting-changes
GitHub stars
208
Token cost
~1.3k tokens
SKILL.md length
682 words
Files
2
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

How to update an existing docouture documentation site when a feature, change, deprecation or fix lands in the repo — figuring out what's affected from a diff/commit/PR, confirming with the user…

  • Works in 4 steps: List the file(s) you just touched. → Grep the root AGENTS.md's "Documentation… → Any hit means that row's doc page now… → …
  • A new feature was just added
  • SKILL.md covers Non-negotiable trigger check, The flow, in short and What this skill deliberately…
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Docouture Documenting Changes is an agent skill from InditexTech/weavejs. How to update an existing docouture documentation site when a feature, change, deprecation or fix lands in the repo — figuring out what's affected from a diff/commit/PR, confirming with the user before writing, and keeping AGENTS.md's documentation-state ledger honest. USE WHEN a new feature was just added, something was deprecated or removed, a fix changes documented behaviour, or docs feel out of date relative to the code. EXAMPLES: 'I added a new CLI flag, update the docs', 'this API is now deprecated, reflect…

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `reference/maintenance-loop.md`).

It sits in Agent Workflows, covering Static sites and blogs and Agent instruction files. The repository describes itself as: Weave.js is an open source library to build real-time collaboration applications like whiteboards, diagram editors, etc. on HTML5 Canvas with your own UI. The licence is Apache-2.0.

When your agent uses it

  • A new feature was just added
  • Something was deprecated
  • A fix changes documented behaviour
  • Docs feel out of date relative to the code

Example prompts

  • “I added a new CLI flag, update the docs”
  • “this API is now deprecated, reflect that in the docs”
  • “document this change”
  • “/docouture-documenting-changes”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. List the file(s) you just touched.
  2. Grep the root AGENTS.md's "Documentation state" table for each one, against every
  3. Any hit means that row's doc page now describes stale behaviour and this skill applies
  4. No hit doesn't necessarily mean "skip it" either — the table is hand-maintained and can

What it can do on your machine

Read from SKILL.md and the folder at commit 2bd3672. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Docouture Documenting Changes loads about 1.3k tokens when it runs. Until then it costs about 158 tokens; SKILL.md has 682 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~158
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from InditexTech/weavejs at commit 2bd3672, republished under its Apache-2.0 licence (© InditexTech). 682 words, ~1,333 tokens.

Download SKILL.mdSave it as .claude/skills/docouture-documenting-changes/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
docouture-documenting-changes
description
How to update an existing docouture documentation site when a feature, change, deprecation or fix lands in the repo — figuring out what's affected from a diff/commit/PR, confirming with the user before writing, and keeping AGENTS.md's documentation-state ledger honest. USE WHEN a new feature was just added, something was deprecated or removed, a fix changes documented behaviour, or docs feel out of date relative to the code. EXAMPLES: 'I added a new CLI flag, update the docs', 'this API is now deprecated, reflect that in the docs', 'document this change', 'my docs are stale, what needs updating'.

Documenting changes

This is the re-entry point for a docouture site that already exists (scaffolded and drafted via docouture-getting-started) and needs to stay in sync as the repo evolves. Use this every time something changes, not just once — it's the loop, not a one-shot pass.

If there's no site yet at all, this is the wrong skill — see docouture-getting-started first.

Non-negotiable trigger check

Before considering ANY code change in this repo done — not just when the user explicitly asks to "update the docs" — check whether it needs this skill:

  1. List the file(s) you just touched.
  2. Grep the root AGENTS.md's "Documentation state" table for each one, against every row's derived from column (globs like antora-extensions/lib/*.js count — check the directory, not just the exact filename).
  3. Any hit means that row's doc page now describes stale behaviour and this skill applies to this change, right now, as part of the same piece of work — not a follow-up, not something to wait to be asked for a second time.
  4. No hit doesn't necessarily mean "skip it" either — the table is hand-maintained and can itself be stale (see reference/maintenance-loop.md); a change to something clearly user-facing (a new CLI flag, a config key, a changed extension behaviour) still warrants a quick check of whether a doc page describes the old behaviour even if nothing in the table points at the file you touched.

This skill decides what changed and whether it needs a docs update; once it knows which page(s) to touch, it hands off to the same skills docouture-getting-started does:

  • docouture-docs-internals — module/page/nav mechanics.
  • docouture-writing-docs-pages — AsciiDoc authoring itself.
  • docouture-authoring-guides — the touched page's content contract: what that section says, in what order, and its quality bar — so an edit to an existing reference or guides page still matches its section's pattern rather than drifting from it.

See reference/maintenance-loop.md for the full mechanism: the AGENTS.md documentation-state ledger, what counts as drift, and when to revisit the home page.

Show full SKILL.md (358 more words)Show less

The flow, in short

  1. Find out what changed. Prefer inspecting the actual change first — a git diff, the commit(s) since the last documented pass, or a PR's description — over asking the user to enumerate it themselves. This is a starting point to propose from, not something to trust blindly: confirm your read of "what changed" with the user before writing anything, since inferred intent can be wrong (a refactor that touches many files is not the same as a new feature, even though both produce a large diff).
  2. Re-scan the repo's surface the same way docouture-getting-started's content-sourcing.md step 3 describes — exports, CLI commands, config keys, API definitions — and diff it against AGENTS.md's ledger. See reference/maintenance-loop.md for exactly what counts as new, stale and current.
  3. Check whether this needs a new page, an edit to an existing one, or a structural change (a whole new module, if this is a monorepo gaining a new publishable artifact — see docouture-getting-started's reference/structure-planning.md for that decision; this skill doesn't re-litigate structure on its own, it flags when structure planning is needed and hands back to that skill for the decision).
  4. Write the update, following whatever page pattern already fits (docouture-docs-internals's reference/page-patterns.md), the content contract for that page's section (docouture-authoring-guides), and the site's existing voice — a code-derived reference page reads differently from a hand-written guide, don't force one to imitate the other.
  5. Update the ledger in AGENTS.md — mark the touched page(s) current again, add a row for anything genuinely new, and never silently regenerate a page marked manual (human-owned) without being asked.
  6. Check nav.adoc for the module(s) touched — a page that exists on disk but isn't listed there builds fine and is simply unreachable; nothing warns about this on its own.

What this skill deliberately doesn't do automatically

It never regenerates a whole site's structure from scratch on every change (that's docouture-getting-started's job, and only ever needed once, or for a genuine restructure), and it never writes past what a diff/commit actually supports without checking with the user first — a hybrid of "look at the change" and "confirm before touching docs," not pure guesswork and not pure Q&A.

© InditexTech, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/docouture-documenting-changes of InditexTech/weavejs.

  • SKILL.md
  • reference/maintenance-loop.md

Open the folder on GitHubat commit 2bd3672

Compare with similar skills

Docouture Documenting Changes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Docouture Documenting Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Docouture Documenting Changes this skillInditexTech/weavejs208—~1.3kAutomated safety check: PassApache-2.0
Eisland Dev Update DocsJNTMTMTM/eIsland320—~1.4kAutomated safety check: PassGPL-3.0
Eisland Dev Update DocsJNTMTMTM/eIsland320—~1.8kAutomated safety check: PassGPL-3.0
Flowfile Docs And WritingEdwardvaneechoud/Flowfile373—~5.4kAutomated safety check: PassMIT
Agent Instructionsmurphytrueman/design-system-ops203—~2.3kAutomated safety check: PassMIT
Review Logging Patternsevloghq/evlog1.9k—~11kAutomated safety check: PassMIT

Similar skills

  • Eisland Dev Update Docs

    JNTMTMTM/eIsland

    Update or create documentation in the eIsland VuePress docs site (web/eisland-web-docs).

    320 GitHub stars~1.4k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Eisland Dev Update Docs

    JNTMTMTM/eIsland

    Update or create documentation in the eIsland VuePress docs site (web/eisland-web-docs).

    320 GitHub stars~1.8k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Flowfile Docs And Writing

    Edwardvaneechoud/Flowfile

    How the Flowfile docs site (MkDocs + Material, the docs/ tree, mkdocs.yml nav) is organized, built by documentation.yml, and deployed to GitHub Pages; the repo-wide comment doctrine for code (and…

    373 GitHub stars~5.4k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Agent Instructions

    murphytrueman/design-system-ops

    Write the AGENTS.md that tells coding agents how to use this design system: where things live, sourced rules, how to check work, what not to do; Claude, Cursor or Copilot pointers on request.

    203 GitHub stars~2.3k tokensUpdated 13 days ago
    Agent WorkflowsAuto-check passed

  • Review Logging Patterns

    evloghq/evlog

    Review code for logging patterns and suggest evlog adoption.

    1.9k GitHub stars~11k tokensUpdated today
    DatabasesAuto-check passed

  • Cursor Usage

    trycompai/comp

    How to write and manage Cursor rules - invoke with @cursor-usage

    2k GitHub stars~1.5k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from InditexTech/weavejs

All 9 skills in this repo

  • Writing Fragments

    InditexTech/weavejs

    Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for…

    208 GitHub starsUsed in 4 repos~828 tokens
    Auto-check: warnings

  • Writing Beats

    InditexTech/weavejs

    Shape an article as a journey of beats, choose-your-own-adventure style.

    208 GitHub starsUsed in 3 repos~705 tokens
    Auto-check passed

  • Docouture Authoring Guides

    InditexTech/weavejs

    What to write on each page of a docouture documentation site: the purpose of every page, the section skeleton it needs, what to say in each section, a copyable AsciiDoc starting point and a quality…

    208 GitHub stars~3.9k tokensUpdated 2 days ago
    Auto-check passed

  • Writing Shape

    InditexTech/weavejs

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format…

    208 GitHub starsUsed in 3 repos~1.1k tokens
    Auto-check passed

  • Docouture Docs Internals

    InditexTech/weavejs

    How a docouture Antora documentation site is put together: the playbook, the docs/antora.yml component descriptor, the four names that must agree, the ROOT+main default layout, promoting…

    208 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check passed

  • Docouture Writing Docs Pages

    InditexTech/weavejs

    How to author AsciiDoc content in a docouture Antora documentation site — the content tree, xref: references, nav.adoc, admonitions, code blocks, and this site's own custom blocks (tabs, cards…

    208 GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Docouture Documenting Changes

What does Docouture Documenting Changes do?

How to update an existing docouture documentation site when a feature, change, deprecation or fix lands in the repo — figuring out what's affected from a diff/commit/PR, confirming with the user…. Docouture Documenting Changes is an agent skill from InditexTech/weavejs.md's documentation-state ledger honest.

When should I use Docouture Documenting Changes?

Docouture Documenting Changes fits situations like: A new feature was just added; something was deprecated; A fix changes documented behaviour; docs feel out of date relative to the code.

How do I install Docouture Documenting Changes in Claude Code?

Run `npx skills add InditexTech/weavejs --skill docouture-documenting-changes -a claude-code`. Or copy the skill folder (.agents/skills/docouture-documenting-changes in InditexTech/weavejs) into .claude/skills/docouture-documenting-changes in your project. Claude Code loads it when a task matches its description.

How do I install Docouture Documenting Changes in Codex?

Run `npx skills add InditexTech/weavejs --skill docouture-documenting-changes -a codex`. Or copy the skill folder (.agents/skills/docouture-documenting-changes in InditexTech/weavejs) into .agents/skills/docouture-documenting-changes in your project. Codex loads it when a task matches its description.

Can I use Docouture Documenting Changes in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add InditexTech/weavejs --skill docouture-documenting-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docouture-documenting-changes, .gemini/skills/docouture-documenting-changes, .github/skills/docouture-documenting-changes and .opencode/skills/docouture-documenting-changes in your project.

What does Docouture Documenting Changes need to run?

SKILL.md names no scripts, command-line tools or credentials: Docouture Documenting Changes is instructions for the agent only.

Does Docouture Documenting Changes access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Docouture Documenting Changes safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Docouture Documenting Changes use?

Docouture Documenting Changes is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Docouture Documenting Changes use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Docouture Documenting Changes?

Skills that share tags, products or a category with Docouture Documenting Changes: Eisland Dev Update Docs (JNTMTMTM/eIsland, 320 stars), Eisland Dev Update Docs (JNTMTMTM/eIsland, 320 stars), Flowfile Docs And Writing (Edwardvaneechoud/Flowfile, 373 stars) and Agent Instructions (murphytrueman/design-system-ops, 203 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docouture Documenting Changes?

InditexTech (a GitHub organization) maintains it in InditexTech/weavejs, which has 208 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 5, 2026.

Source: InditexTech/weavejs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.