Documentation Updater

Name: Documentation Updater
Author: matteocervelli

Listed

matteocervelli·vlatest·writing·MIT

Automatically updates project documentation with code changes and new features, ensuring accuracy and saving time.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add matteocervelli/llms --skill documentation-updater -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

matteocervelli

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 27 Sept 2026

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

Declares what it does: failed
SKILL.md frontmatter is missing description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned matteocervelli/llms at 1e1f2089eb.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 1e1f2089eb
Manifest: .codex/skills/documentation-updater/SKILL.md
Scanned: 13 files, 2,260 lines
Copies in repo: 3 — all of them scanned

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

The documentation-updater skill automatically updates existing technical documentation based on provided changes or new information. It can incorporate edits, add sections, and ensure consistency across documents. This skill aims to streamline the documentation maintenance process, reducing manual effort and potential errors.

When to use it

Updating API references: Keep your API documentation current with code changes.
Adding feature descriptions: Quickly integrate new features into existing user guides.
Correcting outdated information: Ensure accuracy by updating incorrect or obsolete sections in documentation.
Maintaining consistency: Standardize language and formatting across a suite of documents.

Key capabilities

Automatic updates to technical documentation
Incorporates edits and new information
Ensures document consistency
Streamlines documentation maintenance

Example prompts

"Update the 'Authentication' section in the API reference guide with changes from commit SHA abc123def."
"Add a description of the new 'Reporting' feature to the user manual, referencing this design doc: [link]."
“Correct the outdated information about pricing in the ‘Getting Started’ document.”

Tips & gotchas

The skill requires access to the relevant documentation files and potentially commit history. Ensure proper permissions are granted for accurate updates.