medcore-doc-roll

Convert MedCore commit findings into structured TODO.md and CHANGELOG.md updates.

2|3|Updated Apr 13, 2026

Search Tags:#changelog #documentation #deduplication #git history #idempotent automation #architectural findings #E2E coverage

Ready to run

npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-doc-roll

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: medcore-doc-roll
Source: https://github.com/Globussoft-Technologies/medcore/tree/main/.claude/skills/medcore-doc-roll
Command: npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-doc-roll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents architectural and operational findings discovered in recent MedCore commit batches from getting lost in git history instead of being persisted into the canonical docs.

Core Features & Use Cases

Rolls forward docs from recent commits into TODO.md and CHANGELOG.md so the next wave and future readers share the same up-to-date context.
Dedupl*icates and tracks findings by ensuring architectural follow-ups live in the single-source-of-truth “Open architectural follow-ups” table, moving items to “Closed” when they’re resolved.
Keeps E2E/test coverage signals aligned by updating route/spec coverage backlogs when commit bodies indicate new closures.

Quick Start

Run medcore-doc-roll after each medcore-fanout wave completes to consolidate the latest commit findings into TODO.md and CHANGELOG.md without duplicating existing entries.

Frequently Asked Questions about medcore-doc-roll

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

FAQPage Schema

How do I update changelog and TODO.md from architectural findings in git commit history?▼

To update changelog and TODO.md from git history, you roll forward architectural and operational findings embedded in recent commit bodies into structured documentation entries. This process consolidates commit batches into a single docs update, preventing context loss between development waves.

What is documentation roll forward for post-fanout checkpoints?▼

Documentation roll forward is the process of converting architectural findings from recent commit batches into structured TODO.md and CHANGELOG.md updates. It ensures operational discoveries are persisted into canonical docs after fanout waves complete rather than getting lost in commit history.

How do I deduplicate architectural follow-ups in a TODO.md table?▼

You deduplicate architectural follow-ups by using TODO.md as the canonical table source and applying idempotent automation. This ensures each finding appears once in the open follow-ups table and moves items to closed when resolved, preventing duplicate entries across commit batches.

Can I update route and spec coverage backlogs from commit messages?▼

Yes, you can update E2E test coverage backlogs by extracting route and spec closure signals from commit bodies. The documentation roll forward aligns coverage backlogs when commit messages indicate new test closures, keeping tracking tables current.

What's the best way to consolidate ad-hoc commit batches into a single docs commit?▼

The best way to consolidate ad-hoc commit batches is to run an idempotent roll forward across three or more commits. It categorizes findings, deduplicates against existing TODO.md entries, and outputs a single consolidated docs commit update rather than scattered documentation changes.