docling-upstream-upgrade

Automates the upstream Docling upgrade workflow with validation and baseline recording.

7|1|Updated Feb 21, 2026

Search Tags:#automation #audit #baseline #upgrade #upstream #docling

Ready to run

npx skills add https://github.com/sparkeh9/DoclingDotNet --skill docling-upstream-upgrade

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docling-upstream-upgrade
Source: https://github.com/sparkeh9/DoclingDotNet/tree/main/.agent/skills/docling-upstream-upgrade
Command: npx skills add https://github.com/sparkeh9/DoclingDotNet --skill docling-upstream-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping Docling upstream upgrades reproducible across forks is error-prone and time-consuming. This skill automates the end-to-end upgrade workflow to ensure consistency, auditable records, and quicker integration cycles.

Core Features & Use Cases

One-command workflow to fetch latest upstream changes, port local deltas, and rebase against the target branch.
Validation gates including tests, parity checks, and baseline/log updates to maintain traceability.
Use Case: teams maintaining downstream forks can stay aligned with upstream while preserving local customizations.

Quick Start

Execute the one-command workflow to fetch the latest upstream, port the local delta, validate parity, and record baseline metadata.

Frequently Asked Questions about docling-upstream-upgrade

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

FAQPage Schema

How do I automate upstream Docling upgrades across a downstream fork?▼

Automating upstream Docling upgrades requires a reproducible workflow that fetches upstream deltas, ports local changes, runs parity validation tests, and records baseline metadata. This ensures consistent, auditable integration cycles while preserving customizations.

What is the best way to track upstream deltas when porting local repository changes?▼

Tracking upstream deltas involves refreshing the latest upstream changes, porting your local deltas against the target branch, and updating baseline and progress logs. This creates a traceable, auditable record of repository versions and validation gates.

How do I validate parity after porting local changes to a new upstream baseline?▼

Validating parity after porting local changes requires running integrated validation gates including tests and parity checks against the target branch. This verifies that local customizations remain functionally aligned with the new upstream baseline.

Does this upstream upgrade workflow require manual test runs and baseline logging?▼

Manual test runs and baseline logging are not required. The workflow enforces an automated, end-to-end process that executes validation gates, updates baselines, and records progress logs to maintain traceability across repository versions.

When do I need to record baselines during a repository upgrade?▼

Recording baselines is needed immediately after porting local changes and running validation gates. This step captures the validated state of your repository versions, ensuring an auditable record of the upstream integration cycle.

How do I keep Docling forks aligned with upstream without losing local customizations?▼

Keeping forks aligned requires a one-command workflow to fetch the latest upstream, port local deltas, and rebase against the target branch. Validation gates and baseline logs ensure customizations are preserved while maintaining parity.