Git Doc Updater
CheckedAutomatically updates project documentation from Git commit messages, ensuring accuracy and saving developer time.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add u9401066/med-paper-assistant --skill git-doc-updater -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
u9401066
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.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a 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 u9401066/med-paper-assistant at 7e1eab0b05.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 7e1eab0b05
- Scanned
- 1 file, 29 lines
About this skill
What it does
The git-doc-updater skill automatically updates documentation files within a Git repository. It can modify existing files or create new ones based on specified patterns and content, streamlining the process of keeping project documentation synchronized with code changes. This ensures that developers and users always have access to accurate and up-to-date information about the codebase.
When to use it
- Automating API reference generation: Automatically update API documentation files (e.g., Markdown or reStructuredText) whenever function signatures change in the code.
- Maintaining user guides: Keep user guide examples consistent with current software versions by updating code snippets within the documentation.
- Synchronizing release notes: Generate and update release notes based on commit messages, ensuring a clear record of changes for users.
- Updating contribution guidelines: Automatically update contribution guidelines when project setup or development processes evolve.
Key capabilities
- Automatic file modification
- File creation
- Pattern-based content generation
- Git repository integration
Example prompts
- "Update the API reference documentation based on changes in
src/api.py." - "Generate release notes for version 1.2.0 from commit messages since tag v1.1.0."
- “Create a new user guide section demonstrating feature X, including code examples.”
Tips & gotchas
The skill requires access to the Git repository and appropriate permissions to modify files. Ensure that the patterns used for content generation are accurate and well-defined to avoid unintended changes to documentation.