docs-update is agent-read markdown (skill) from jellydn/my-ai-tools: Update docs when code changes — reviews commits and syncs user-facing documentation.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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)
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
A 17 of 17 checks passed. Deterministic, no model, same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (4515 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
jellydn/my-ai-tools · 121 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_stayutdmnkyg62ss
GET https://markdownregistry.com/api/v1/resolve?ref=jellydn/my-ai-tools/docs-update
GET https://markdownregistry.com/api/v1/blob/9d5ab16b11a612dac817c4781593a0e1fc25d654abd096aa83e7cb4ed5cd60bb
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/accountable-engineering/SKILL.md · Use explicit human checkpoints for architecture, security, rollout, or operational decisions.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/blindspot-pass/SKILL.md · Inspect history and architecture for hidden constraints before risky cross-cutting changes.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/capability-experiments/SKILL.md · Build an interactive report or experiment when the user asks to explore model capabilities.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/code-quality-review/SKILL.md · Audit a diff for structural maintainability and unnecessary complexity.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/code-review/SKILL.md · Review a branch, PR, or worktree diff for repository conventions and stated intent.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/codemap/SKILL.md · Create a seven-document architecture map when the user asks to map a codebase.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/commit-atomic/SKILL.md · Group staged changes into atomic commits with commitizen convention
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/context-discovery/SKILL.md · Use MCP tools to trace behavior that spans multiple modules or history sources.
outlinedriven/outline-driven-development · .devin/skills/docs-update/SKILL.md · Use when documentation has drifted from code changes and the user asks to synchronize. Not for ADRs or architectural…
henrigrimm/minnow · src/skills/docs-update/SKILL.md · Update README and documentation/context.md after code changes. Use when docs are stale or user asks to document.
aka-kika/akakika-skills · skills/maintenance/docs-update/SKILL.md · Use when the user needs to update, improve, audit, or maintain documentation in a project. Covers READMEs, changelogs…
