Synchronize repository documentation with code changes and version bumps.
npx skills add https://github.com/stas-ka/picoclaw --skill taris-update-doc
Please help me install this Agent Skill. Skill: taris-update-doc Source: https://github.com/stas-ka/picoclaw/tree/main/.github/skills/taris-update-doc Command: npx skills add https://github.com/stas-ka/picoclaw --skill taris-update-doc
Update project documentation after code changes, version bumps, new features, or any structural change to keep all docs in sync with the codebase.
Run the update-doc workflow to synchronize repository documentation with code changes.
High-intent search queries and answers about installing and using this skill.
To automate documentation updates, you synchronize repository docs like README and TODO files with code changes and version bumps. Using a defined scope and file-change hints drives the updates and ensures consistent versioning across the project.
Keeping README and TODO files in sync with new features requires applying a defined scope and file-change hints. This ensures documentation accurately reflects structural changes and feature additions across the repository.
Documentation synchronization for bot-code map references and web UI inventories works by aligning them with BOT_VERSION and new prompts. Applying file-change hints updates cross-links and maintains accurate architectural topics across the repository.
Yes, you can update the Copilot skill registry and web UI route inventory automatically. The workflow applies file-change hints to keep these components aligned with the latest BOT_VERSION and structural codebase modifications.
Yes, providing file-change hints is required to update project documentation effectively. These hints define the scope of changes, driving the synchronization process to ensure accurate versioning and cross-linking across affected repository files.
Limitations of automating repository documentation synchronization include relying on accurate file-change hints and a defined scope. Without proper hints, the workflow cannot effectively drive updates or ensure consistent cross-linking across architectural topics.
accolverAnalyze staged git diffs to generate conventional commit messages with monorepo scopes.
bordenetValidate and verify Markdown links in documentation before publishing.
bomberoxenviosdosruedasAutomate DevOps workflows with Terraform, GitHub Actions, Kubernetes, and Prometheus.
dt418Build documentation platforms with versioned docs, search, navigation, code highlighting, and API reference generation.
