New: 97,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

Docs Update

by jellydn in jellydn/my-ai-tools

Update docs when code changes — reviews commits and syncs user-facing documentation

MITAuto-check passedDevelopment

Install Docs Update

skills CLI
$ npx skills add jellydn/my-ai-tools --skill docs-update -a claude-code

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

GitHub CLI
$ gh skill install jellydn/my-ai-tools docs-update --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/jellydn/my-ai-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/docs-update .claude/skills/docs-update && 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
docs-update
GitHub stars
123
Used in
1 other repo
Token cost
~1.1k tokens
SKILL.md length
513 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

Update docs when code changes — reviews commits and syncs user-facing documentation

  • Works in 5 steps: Identify Significant Code Changes → Analyze Documentation Context → Determine Documentation Updates → …
  • Development work in your project
  • SKILL.md covers Workflow, Multi-Repository Setup, Edge Cases and Key Principles
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Docs Update is an agent skill from jellydn/my-ai-tools. Update docs when code changes — reviews commits and syncs user-facing documentation

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: cline, claude, opencode, amp, codex, gemini, cursor, pi

It sits in Development. The repository describes itself as: Comprehensive configuration management for AI coding tools - Replicate my complete setup for Claude Code, OpenCode, Amp, Li, Codex and Claude Code Switch with custom… The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/docs-update”

Requirements

  • Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify Significant Code Changes
  2. Analyze Documentation Context
  3. Determine Documentation Updates
  4. Generate Documentation Changes
  5. Execute or Report

What it can do on your machine

Read from SKILL.md and the folder at commit 163951e. 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.

  • Compatibility

    cline, claude, opencode, amp, codex, gemini, cursor, pi

    From compatibility in the SKILL.md frontmatter.

Context cost

Docs Update loads about 1.1k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 513 words of instructions outside code blocks.

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

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 jellydn/my-ai-tools at commit 163951e, republished under its MIT licence (© jellydn). 513 words, ~1,128 tokens.

Download SKILL.mdSave it as .claude/skills/docs-update/SKILL.md (or your agent's skills folder).
name
docs-update
description
Update docs when code changes — reviews commits and syncs user-facing documentation
compatibility
cline, claude, opencode, amp, codex, gemini, cursor, pi
license
MIT
hint
Use when updating documentation, reviewing docs, or handling documentation changes after code changes
user-invocable
true
disable-model-invocation
true
metadata.audience
all
metadata.workflow
documentation

Documentation Bot

Automatically review code changes and update user-facing documentation to keep it synchronized with the codebase. Works across documentation platforms (Mintlify, Docusaurus, GitBook, Fumadocs, etc.) and supports both monorepo and multi-repo setups.

Workflow

1. Identify Significant Code Changes

Determine which commits need documentation updates:

  • Find the default branch
  • Get recent commits (default: last 24 hours, or accept user-specified timeframe)
  • Examine each commit's changes to understand what was modified

Filter for significant changes:

  • New features or capabilities
  • API changes (new endpoints, parameters, return values)
  • Breaking changes
  • New configuration options
  • New CLI commands or flags
  • Changes to user-facing behavior

Skip documentation for:

  • Internal refactoring
  • Test-only changes
  • Minor bug fixes
  • Typo corrections in code
  • Performance optimizations without user impact

Be conservative: quality over quantity. When in doubt about significance, skip the update.

2. Analyze Documentation Context

Locate documentation:

  • Check for documentation directory in current repo (monorepo pattern)
  • Look for separate documentation repository in environment

Identify documentation platform: Determine the platform by examining configuration files and directory structure (e.g., Mintlify, Docusaurus, GitBook, Fumadocs, or generic markdown).

Understand documentation style: Read several existing documentation files to identify tone, voice, structure, code example patterns, terminology, and formatting conventions. Check for style guides or contribution documentation.

3. Determine Documentation Updates

Map code changes to documentation needs (new content, modifications, or additions to existing content).

Guidelines:

  • Prioritize user-facing changes over implementation details
  • Match existing documentation verbosity (some docs are comprehensive, others minimal)
  • Preserve existing accurate content—be strictly additive when possible
  • Keep content focused and avoid generic advice
4. Generate Documentation Changes

Match existing style:

  • Use the same tone, voice, and formality level identified in step 2
  • Follow the same heading structure and hierarchy
  • Use consistent terminology
  • Match code block formatting (language tags, highlighting)
  • Follow platform conventions (frontmatter, special syntax, custom components)
Show full SKILL.md (219 more words)Show less
5. Execute or Report

Testing mode (when user asks to "see what would change"):

Output a text summary describing:

  • What changes were detected in commits
  • Which documentation files would be modified
  • What content would be added or changed
  • Rationale for why these updates are needed

Execution mode (when running as automation):

  1. Create a descriptive branch name (e.g., docs/auto-update-YYYYMMDD)

  2. Make documentation changes to appropriate files

  3. Push branch and create PR with description linking to relevant commits:

    • List which code changes triggered which documentation updates
    • Include commit references or URLs from source repository
    • Request review for accuracy and completeness

Multi-Repository Setup

When source code and documentation are in separate repositories, identify changes in the source repo, then switch to the docs repo and follow the workflow above. Reference source commits in the PR description.

Edge Cases

  • If no significant changes found, report that no documentation updates are needed
  • If documentation platform is unclear, default to standard markdown syntax
  • If conflicting with existing content, preserve existing information and note conflicts for human review

Key Principles

  • Conservative: Better to skip than clutter documentation
  • Consistent: Match existing style, tone, and structure exactly
  • Contextual: Consider the full documentation landscape, not just individual files
  • Clear: Explain significance of changes and rationale for updates
  • Practical: Focus on helping users accomplish tasks, not describing implementation

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

Files

Just SKILL.md in skills/docs-update of jellydn/my-ai-tools.

Open the folder on GitHubat commit 163951e

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jellydn/my-ai-tools, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Docs Update 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.

Docs Update compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Docs Update this skilljellydn/my-ai-tools1231 repos~1.1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k24 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 24 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

More from jellydn/my-ai-tools

All 35 skills in this repo

  • Babysit PR

    jellydn/my-ai-tools

    A skill your agent uses when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.

    123 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

  • Visual PR

    jellydn/my-ai-tools

    Posts a concise visual outline as a GitHub pull request comment.

    123 GitHub stars~764 tokensUpdated yesterday
    Auto-check passed

  • Qmd Knowledge

    jellydn/my-ai-tools

    Manage project knowledge with qmd — captures learnings, decisions, and conventions

    123 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Prd

    jellydn/my-ai-tools

    Generate Product Requirements Documents from feature ideas — plans specs and requirements

    123 GitHub starsUsed in 4 repos~1.8k tokens
    Auto-check passed

  • Capability Experiments

    jellydn/my-ai-tools

    Build an interactive report or experiment when the user asks to explore model capabilities.

    123 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • PR Review

    jellydn/my-ai-tools

    Fix PR review comments by implementing requested changes. An agent skill from jellydn/my-ai-tools.

    123 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Docs Update

What does Docs Update do?

Update docs when code changes — reviews commits and syncs user-facing documentation. Docs Update is an agent skill from jellydn/my-ai-tools.

When should I use Docs Update?

Docs Update fits situations like: development work in your project.

How do I install Docs Update in Claude Code?

Run `npx skills add jellydn/my-ai-tools --skill docs-update -a claude-code`. Or copy the skill folder (skills/docs-update in jellydn/my-ai-tools) into .claude/skills/docs-update in your project. Claude Code loads it when a task matches its description.

How do I install Docs Update in Codex?

Run `npx skills add jellydn/my-ai-tools --skill docs-update -a codex`. Or copy the skill folder (skills/docs-update in jellydn/my-ai-tools) into .agents/skills/docs-update in your project. Codex loads it when a task matches its description.

Can I use Docs Update 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 jellydn/my-ai-tools --skill docs-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-update, .gemini/skills/docs-update, .github/skills/docs-update and .opencode/skills/docs-update in your project.

What does Docs Update need to run?

SKILL.md names no scripts, command-line tools or credentials: Docs Update is instructions for the agent only. Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi.

Does Docs Update 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 Docs Update 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 Docs Update use?

Docs Update is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Docs Update use?

About 1.1k tokens (SKILL.md is roughly 4.5k 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 Docs Update?

Skills that share tags, products or a category with Docs Update: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs Update?

jellydn (a GitHub user) maintains it in jellydn/my-ai-tools, which has 123 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 7, 2026.

Source: jellydn/my-ai-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.