skills.rest
sudocarlos
sudocarlosCOMMUNITY
Explore all skills by this author →
GitHub

documentation

Update tailrelay documentation files to reflect current codebase changes.

4|1|Updated Mar 13, 2026
Search Tags:#changelog#versioning#documentation#readme#skill management#docs
One-click install
npx skills add https://github.com/sudocarlos/tailrelay --skill documentation-sudocarlos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/sudocarlos/tailrelay/tree/main/.agents/skills/documentation
Command: npx skills add https://github.com/sudocarlos/tailrelay --skill documentation-sudocarlos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all user-facing and agent-facing documentation for tailrelay is accurate, up-to-date, and consistent across multiple locations.

Core Features & Use Cases

  • Centralized Documentation Management: Manages updates for README.md, CHANGELOG.md, webui/README.md, AGENTS.md, and all SKILL.md files.
  • Version Consistency: Ensures documentation reflects the latest code changes and release versions.
  • Use Case: After releasing a new version of tailrelay with updated features, use this Skill to update the README, CHANGELOG, and relevant SKILL.md files to reflect these changes, ensuring users and agents have accurate information.

Quick Start

Update all tailrelay documentation files to reflect the latest changes.

Frequently Asked Questions about documentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep my project documentation in sync after a new release?▼

To sync project documentation after a release, review all assets including README, CHANGELOG, and SKILL.md files against the current codebase to ensure version consistency and accurate feature tracking.

What is the best way to update a CHANGELOG and README for new features?▼

Updating a CHANGELOG and README requires centralized documentation management that verifies all user-facing and agent-facing text reflects the latest code changes and component versions.

When do I need to update SKILL.md files for versioning changes?▼

Update SKILL.md files when new features are released, component versions change, or outdated review SHAs are identified, ensuring agent-facing documentation remains accurate.

Does centralized documentation management work for both user and agent facing files?▼

Yes, centralized documentation management handles both user and agent facing files by maintaining consistency across standard project docs like README.md and agent specific files like AGENTS.md.

What are the limitations of manually syncing multiple documentation assets?▼

Manually syncing multiple documentation assets often leads to outdated review SHAs, missed CHANGELOG updates, and inconsistent feature descriptions between the codebase and the README.

How do I ensure version consistency across all project documentation?▼

Ensure version consistency across project documentation by performing a thorough review of all text assets against the codebase whenever triggered by new features, version releases, or component version changes.

Related Skills

Explore More Software Engineering Skills→
vincent-kkvincent-kk
1

git-tag-analyzer

Analyze Git tags in a monorepo to locate release-worthy tags and prepare release notes.

Community
Advanced
ThiagoGuislottiThiagoGuislotti
2

docs-release-engineer

Generate repository documentation and release artifacts with semantic versioning and link validation.

Community
Intermediate
DaFumDaFum
1

skill-aligner

Rewrites SKILL.md files to align terminology and metadata with repository conventions.

Community
Advanced
joaquimscostajoaquimscosta
21

generating-changelog

Analyze git commit history to generate formatted changelogs with version bumps.

Community
Advanced