Scribe

Update changelogs, READMEs, and OpenAPI specs after architectural changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Ghabs95/agents --skill scribe-ghabs95
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Scribe
Source: https://github.com/Ghabs95/agents/tree/main/wlbl-agents/.agent/skills/scribe
Command: npx skills add https://github.com/Ghabs95/agents --skill scribe-ghabs95

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all project documentation, including changelogs, READMEs, and API specifications, remains accurate, up-to-date, and professionally presented.

Core Features & Use Cases

  • Changelog Maintenance: Automatically updates CHANGELOG.md after major feature releases.
  • Documentation Sync: Keeps README.md files current with architectural changes.
  • API Documentation Generation: Monitors for new endpoints and ensures OpenAPI specs are created.
  • Architecture Diagram Updates: Synchronizes documentation with visual architecture diagrams.
  • Use Case: After a new API endpoint is deployed, the Scribe Skill will automatically update the Swagger/OpenAPI documentation and ensure the relevant README.md reflects this change.

Quick Start

Use the Scribe skill to update the CHANGELOG.md with the latest feature.

Frequently Asked Questions about Scribe

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

FAQPage Schema
How do I automatically update changelog and README files after a new API endpoint release?

To automatically update changelog and README files after a release, you can use documentation maintenance skills to monitor architectural changes and sync new endpoints into your project specs. This ensures your technical writing reflects the latest deployed features accurately.

What is the best way to keep OpenAPI specifications synchronized with architectural changes?

Keeping OpenAPI specifications synchronized with architectural changes requires monitoring for newly deployed endpoints and automatically generating or updating the relevant Swagger documentation. This process ensures API documentation accuracy across multiple projects.

How do I maintain professional technical writing standards across multiple project repositories?

Maintaining professional technical writing standards across multiple repositories requires a consistent process that monitors project updates and enforces clear, concise Standard English. This approach keeps all API docs and changelog entries professionally presented.

Can I use a documentation maintenance skill to sync architecture diagrams with README files?

Yes, you can use a documentation maintenance skill to sync architecture diagrams with README files. It monitors for structural project changes and automatically updates the documentation to ensure visual diagrams and textual references remain accurate.

Does this documentation maintenance approach work without external dependencies or components?

This documentation maintenance approach works without external dependencies or components. It operates independently to monitor project changes and update technical writing outputs like changelogs and API specifications directly.