udoc

Update ETNA_TRADER documentation and generate changelog entries from completed tasks.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/tombelial666/test --skill udoc-tombelial666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: udoc
Source: https://github.com/tombelial666/test/tree/main/.cursor/skills/udoc
Command: npx skills add https://github.com/tombelial666/test --skill udoc-tombelial666

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates updating project documentation and generating changelog entries from a completed ETNA_TRADER task implementation.

Core Features & Use Cases

  • Documentation updates: Reconciles code changes with docs across relevant sections (docs/architecture.md, docs/adr/, docs/api/, db/README.md, CLAUDE.md, AGENTS.md, and sync-docs guidelines) based on the completed task.
  • Changelog generation: Produces a changelog entry summarizing the task's feature or fix, API changes, DB schema updates, and related docs.
  • Lifecycle automation: Integrates with a docs-updater agent and a changelog-generator agent following the ETNA_TRADER path conventions.

Quick Start

Provide the task directory path (e.g., tasks/task-2026-03-19-feature-name/) to start updating docs and generate a changelog.

Frequently Asked Questions about udoc

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

FAQPage Schema
How do I update documentation and generate a changelog after completing an ETNA_TRADER task?

To update documentation and generate a changelog for an ETNA_TRADER task, provide the completed task directory path. The skill runs docs-updater and changelog-generator agents to reconcile code changes across architecture, ADR, and API docs. You receive updated documentation files and a summarized changelog entry.

What documentation files are updated when reconciling ETNA_TRADER task changes?

Documentation updates target architecture docs, ADRs, API definitions, DB schemas, CLAUDE.md, and AGENTS.md. The process reconciles implemented code changes across these specific project files to ensure technical documentation stays synchronized with the latest ETNA_TRADER task implementations.

When should I run the changelog generator for an ETNA_TRADER feature implementation?

You should run the changelog generator before PR or after merge when an ETNA_TRADER task is implemented and requires documentation updates. It produces a summarized changelog entry covering the task's feature, API changes, DB schema updates, and related docs.

Can I use this docs-updater for any software project or only ETNA_TRADER tasks?

The docs-updater is specifically designed for ETNA_TRADER task implementations. It follows ETNA_TRADER path conventions and lifecycle automation steps, making it unsuitable for generic software projects outside this specific architecture and task directory structure.

What is the best way to automate architecture docs and DB schema updates for ETNA_TRADER tasks?

The best way to automate architecture docs and DB schema updates is providing the task directory path to trigger the docs-updater agent. It automatically reconciles code changes with docs/architecture.md, db/README.md, and sync-docs guidelines based on the completed ETNA_TRADER task.

Does the changelog generator automatically summarize API changes and DB schema updates?

Yes, the changelog generator automatically produces a changelog entry summarizing the ETNA_TRADER task's feature or fix. It specifically includes API changes, DB schema updates, and related documentation updates extracted from the completed task implementation.