transcript-correction

Corrects Korean lecture transcripts against textbook sources and tracks correction state in a JSON log.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/kmjy98-sketch/khulaw --skill transcript-correction-kmjy98-sketch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: transcript-correction
Source: https://github.com/kmjy98-sketch/khulaw/tree/main/.agent/skills/transcript-correction
Command: npx skills add https://github.com/kmjy98-sketch/khulaw --skill transcript-correction-kmjy98-sketch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Lecture transcripts produced by speech recognition contain misrecognized legal terms, article numbers, and case names, and manually tracking which transcript parts have been corrected across many folders is error-prone. This Skill enforces strict evidence-based correction rules and automates the bookkeeping of correction status. ## Core Features & Use Cases - Evidence-Based Correction: Corrects only clear typos and terminology errors while preserving original wording, requiring a two-line source citation for every change and marking unclear segments as [불명확] instead of deleting them. - Correction State Tracking: Records reviewed versus generated corrections per transcript in transcription_log.json, detects duplicate transcripts by SHA256, and repairs stale paths. - Batch Automation: Lists uncorrected transcripts, generates heuristic corrected drafts from a replacement dictionary, and batch-marks completed corrections with progress and index hooks. - Use Case: After transcribing a civil law lecture into part files, run list_uncorrected.py to see pending parts, correct them against the textbook, then run mark_corrected.py to log completion and update study progress. ## Quick Start Ask the assistant to correct a specific transcript part file against the textbook source and then mark it as corrected using the provided script.

Frequently Asked Questions about transcript-correction

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

FAQPage Schema
How do I correct a lecture transcript part file?▼

Correct the *_partXX.md file against the textbook source, save it as *_corr.md in the same folder, then run mark_corrected.py with the corrected file path. The script updates transcription_log.json and triggers progress and index hooks.

How do I find which transcripts still need correction?▼

Run list_uncorrected.py to print all pending transcripts with their correction state, part counts, and sample files. It reads transcription_log.json and supports --json output and an --output file option.

What corrections are allowed on transcripts?▼

Only clear typos, machine misrecognitions, and terminology errors like article numbers or case names may be fixed, each requiring a two-line source citation. Deleting content, summarizing, rephrasing, or changing sentence structure is prohibited, and unclear audio is marked as [불명확].

Can corrections be generated automatically instead of manually?▼

Yes, generate_corrections.py creates heuristic corrected files using a built-in replacement dictionary and regex rules for common misrecognitions. These are tracked separately as generated files and do not count as reviewed until manually verified.

How are duplicate transcript files handled?▼

Duplicates are detected by SHA256 hash of transcript files, preferring non-_inbox paths with reviewed corrections or split parts as canonical. Duplicate entries are marked with duplicate_of and duplicate_reason fields and excluded from pending correction lists.

What happens if a transcript folder path no longer exists?▼

Entries with missing split directories are marked as stale in the log. The repair_stale_paths.py script can fix stale paths by applying alias replacements, such as renaming a folder segment, when the corrected path exists on disk.