unit-testlisted

# unit-test — multi-angle unit testing after code changes The active host designs, runs, and documents unit tests for freshly changed code. Use the runtime identity supplied by the current session; never infer it from skill paths. Host-local only: never call the counterpart, crosscheck scripts, or another LLM. Respond in the language the user writes in — Korean request, Korean output; English request, English output. The report follows that same language. This rule document stays English regardless. ## 0. Invocation — explicit requests only - Use this skill only when the user explicitly asks for unit testing or its report. - Ordinary code modification does not trigger this skill. Do not offer unit tests merely because code changed. - A direct request to run unit tests IS the approval for local unit testing; do not ask again. - Approval covers local unit testing only. Never access an external DB, network, service, or runtime from this skill. Route those checks to a separate verification step with its own explicit permission. ## 1. Scope — what to test - `git diff HEAD` (or the session's edit list) → enumerate changed functions/methods. - Classify each check as `UNIT`, `STATIC`, `BUILD`, `INTEGRATION`, `RUNTIME`, or `PERFORMANCE`. This skill executes only local `UNIT`, plus the smallest useful `STATIC` or `BUILD` gate. List the other classes as uncovered; do not run them here. - Prefer pure-logic units and isolated local fixtures first. - Skip generated files, comm