Update project documentation after code merges with consistency checks.
npx skills add https://github.com/borkweb/skills --skill document-release-borkweb
Please help me install this Agent Skill. Skill: document-release Source: https://github.com/borkweb/skills/tree/main/skills/gstack/document-release Command: npx skills add https://github.com/borkweb/skills --skill document-release-borkweb
Ensures that documentation reflects post-shipment changes accurately, reducing confusion and ensuring all users have access to the most up-to-date information.
Run the /document-release workflow to update your documentation post-shipment.
High-intent search queries and answers about installing and using this skill.
Automate documentation updates by running a post-shipment workflow that reads, writes, and edits markdown files using file globbing to locate relevant docs, ensuring accuracy and consistency across your project after code is merged.
Maintaining document consistency post-shipment requires automated cross-doc verification that checks various markdown documentation files for accuracy and uniformity immediately following code updates, reducing confusion and keeping information current.
Automated post-shipment documentation updating works by integrating with version control to trigger markdown file edits after code merges, requiring tools for managing version changes and prompting the user for input when required.
Yes, automating markdown editing requires tools for reading, writing, and editing markdown files, a file globbing tool to locate relevant documentation, and a tool for managing version changes to ensure accurate post-shipment updates.
Yes, automated documentation updates are designed for software engineering version control workflows, providing structured feedback for changes and decisions related to documentation updates immediately following code merges.
Avoid automated documentation updates when your project lacks markdown files, version control integration, or the required file globbing and version management tools, as the workflow depends on these components to locate and edit documentation accurately.
SantiagoisperCompare project documentation with code changes and update relevant Markdown files.
burgebjParse Git diff outputs to update Markdown documents after releases.
novatech2210-cmdAutomate truth scoring and verification checks for code and agent outputs.
jey3dayoReview Markdown documentation for clarity, structure, and technical accuracy.
