Audit markdown documentation against code diffs and update release notes.
npx skills add https://github.com/MFS-code/gstack --skill document-release-mfs-code
Please help me install this Agent Skill. Skill: document-release Source: https://github.com/MFS-code/gstack/tree/main/document-release Command: npx skills add https://github.com/MFS-code/gstack --skill document-release-mfs-code
This Skill prevents documentation from getting out of date after code ships, so users and contributors trust what they read.
Ask your AI agent to run /document-release to update the repo documentation based on what you shipped and fix any stale references.
High-intent search queries and answers about installing and using this skill.
To synchronize repository documentation, run a post-merge diff audit against your current release context. This updates README files and contributor guides to accurately reflect shipped code changes without clobbering your existing CHANGELOG entries.
Updating stale markdown docs after a release requires a diff-driven audit of your project instructions and architecture files. This process checks cross-reference accuracy, ensuring documented commands and paths match your newly shipped code behavior.
Polishing a CHANGELOG without overwriting entries involves applying targeted narrative updates that clean up TODOs and improve wording voice. The process follows safety rules to prevent risky changes while leaving your existing release history intact.
No, you cannot automatically bump a project's VERSION number during a documentation refresh. The process follows strict safety rules for VERSION bump decisions, requiring manual intervention to coordinate version changes and prevent unintended release conflicts.
You should run a post-ship documentation audit immediately after merging code changes to keep contributor onboarding guides accurate. This ensures new contributors trust the documented commands, behaviors, and architecture paths they read.
Jonathan0823Generate release notes and propose semver bumps from merged pull requests.
aydinsenturkkGenerate formatted markdown knowledge files from official and community documentation.
akaszubskiValidate documentation file paths, links, line numbers, and code imports across repositories and branches.
Selfdb-ioGenerate docstrings, README files, API docs, and architecture overviews from source code.
