hwpforge-submission-check

HwpForge 제출 전 점검

Checks a .hwpx the user is about to submit and reports what is missing or should not be sent. For a legacy .hwp, convert it first into a new temp dir, never next to the input (d=$(mktemp -d) && hwpforge convert-hwp5 old.hwp -o "$d/old.hwpx" && echo "$d/old.hwpx"), check that .hwpx, and delete $d after the report.

Rules

1. Report only. Never modify, re-save or replace the input. If the user wants fixes, hand off to the main hwpforge skill after the report.
2. Write nothing next to the input. The script writes only into a new temp dir.
3. HwpForge surfaces only. Do not unzip the package or grep its XML; the script runs every check. What it cannot see is listed under 알려진 한계: report it as not checked, do not work around it.
4. The script's last line decides completeness. CHECK COMPLETE (exit 0) or CHECK INCOMPLETE: <steps> (exit 1). On INCOMPLETE the verdict is 점검 불완전 — 확인 필요; name the steps and the error codes from their exit= lines; for cell-coverage, name each skipped table line. A PDF render failure is not in the gate; it only leaves the layout unverified.
5. Plain Korean, no raw JSON. The user gets the report format at the end, nothing else.

Step 1: run the script once

bash ${CLAUDE_SKILL_DIR}/scripts/check.sh /path/to/doc.hwpx

It takes exactly one argument and runs the hwpforge found on PATH; any other argument count stops it with CHECK INCOMPLETE: usage. If hwpforge is not on PATH, ask the user to install it or add it to PATH. Run it through bash with exactly this path; the skill's pre-approval matches only this form. Everything the verdict needs is printed; the temp dir is deleted when the script ends. To read the full outputs (paras.txt, doc.json, plan.json) or keep the rendered doc.pdf for the visual check, run KEEP=1 bash ${CLAUDE_SKILL_DIR}/scripts/check.sh … (this form asks for permission): it prints scratch: DIR (kept), and you delete that dir when done.