docs-release-engineer

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

2|1|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill docs-release-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-release-engineer
Source: https://github.com/ThiagoGuislotti/copilot-instructions/tree/main/.codex/skills/docs-release-engineer
Command: npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill docs-release-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes production and maintenance of repository documentation and release artifacts so maintainers avoid inconsistent READMEs, weak PR descriptions, and unstructured changelogs across projects.

Core Features & Use Cases

  • Template-driven authoring: Apply repository instruction packs and prompt templates for README, PR text, changelogs, and instruction docs.
  • Release artifact enforcement: Generate changelog entries with semantic versioning and ISO dates, validate links and cross-references before release.
  • Documentation workflows: Route and load relevant files (.github/AGENTS.md, routing catalogs, prompt accelerators) to produce consistent docs and PR descriptions for releases and contributor guidance.
  • Use Case: When preparing a release, produce a standardized README update, a PR description, and a changelog entry that follow repository conventions and validate references.

Quick Start

Use the docs-release-engineer skill to update the repository README and generate a validated changelog entry for the next release.

Frequently Asked Questions about docs-release-engineer

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

FAQPage Schema
How do I generate a changelog entry with semantic versioning for a GitHub release?

Generate a changelog entry with semantic versioning by applying template-driven authoring to produce release artifacts. The tool enforces semantic version changelog format and ISO date usage, validating links and cross-references before release.

What is the best way to standardize README updates and PR descriptions across repository projects?

Standardize README updates and PR descriptions by routing and loading repository instruction packs and prompt templates. This ensures consistent documentation workflows and PR text generation that follow established repository conventions.

How do I validate links and cross-references in repository documentation before publishing?

Validate links and cross-references in repository documentation through automated release artifact enforcement. The system checks references within README files, PR descriptions, and changelog entries to ensure correctness during versioning and publish cycles.

Can I use .github process files and routing catalogs to maintain contributor guidance docs?

Yes, you can use .github process files like AGENTS.md and routing catalogs to maintain contributor guidance docs. The documentation workflows route and load these relevant files to produce consistent instruction docs and prompt accelerators.

Does this approach work for maintaining prompt templates and instruction docs alongside standard release notes?

Yes, this approach works for maintaining prompt templates and instruction docs alongside standard release notes. It centralizes production of repository documentation, applying template-driven authoring to generate README files, changelogs, and instruction docs simultaneously.

When do I need ISO date formatting and semantic versioning in my changelog generation process?

ISO date formatting and semantic versioning are needed in changelog generation during versioning and publish cycles. The process enforces these standards to prevent unstructured changelogs and maintain consistency across repository release artifacts.