skills.rest
dadafinger
dadafingerCOMMUNITY
Explore all skills by this author →
GitHub

kr-manual-change-tracker

Registers Korean manual changes into a YAML ledger and validates Screen ID coverage against planning PDFs.

Updated May 10, 2026
Search Tags:#documentation#yaml#change tracking#korean#manual#coverage validation#screen id
One-click install
npx skills add https://github.com/dadafinger/dadafinger-skills --skill kr-manual-change-tracker-dadafinger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kr-manual-change-tracker
Source: https://github.com/dadafinger/dadafinger-skills/tree/main/proprium/cursor/skills/kr-manual-change-tracker
Command: npx skills add https://github.com/dadafinger/dadafinger-skills --skill kr-manual-change-tracker-dadafinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Korean-language manual is updated for a new product version, changes are often tracked in handwritten checklists, making it easy to miss screens. This Skill converts those manual checklists into a structured YAML change ledger and cross-checks the planning document PDF to find any Screen IDs that were not registered, ensuring full coverage. ## Core Features & Use Cases - YAML Change Ledger: Registers each manual change from a handwritten checklist or the planning document's Document History into a structured YAML ledger, continuing numbering from the last entry (last_num + 1). - Coverage Validation: Compares registered entries against Screen IDs found in the planning PDF to detect unregistered screens. - Use Case: When releasing a new CONTRABASS version, feed the manual update checklist and the planning PDF to the Skill; it completes the change ledger and reports any Screen IDs missing from the ledger before publication. ## Quick Start Register this version's manual change checklist into the change ledger and verify coverage against the planning PDF.

Frequently Asked Questions about kr-manual-change-tracker

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

FAQPage Schema
How do I track Korean manual changes across product versions?▼

Register each change from the handwritten checklist or the planning document's Document History into a YAML change ledger. Entries continue from the last recorded number, giving you a complete, ordered record of every manual update for the version.

How to verify all screens are covered in a manual update?▼

Compare the registered change ledger against the Screen IDs listed in the planning PDF. Any Screen ID present in the planning document but missing from the ledger is flagged as unregistered, confirming full coverage before release.

What input does the change ledger registration require?▼

It requires a handwritten change checklist or the Document History section of the planning document, plus the planning PDF for coverage checks. New entries are numbered starting from last_num + 1 in the existing YAML ledger.

Why are some Screen IDs missing from the change ledger?▼

Missing Screen IDs usually mean the handwritten checklist omitted changes described in the planning PDF. The coverage check cross-references the PDF against the ledger to surface these gaps so they can be registered before the manual ships.

Related Skills

Explore More Content & Communication Skills→
ronmikailovronmikailov

generate-changelog

Consolidate Git commits, plan files, or manual inputs into a Keep a Changelog formatted changelog.

Community
Advanced
ReadyToGo-EducationReadyToGo-Education
15

pagina-lovable

Publish a local HTML page to Lovable via API and return a public URL.

Official
Intermediate
neverpreparedneverprepared

graphviz-diagrams

Generate Graphviz DOT diagrams and render them to PNG, SVG, or PDF.

Official
Advanced
amplitudeamplitude
28

diff-intake

Reads a PR or branch diff and generates a structured YAML change brief.

Official
Advanced