Zereight Debt Log

zereight-debt-log

Chat with the user in Korean unless they write in English.

What this is for

During review you sometimes hit something that isn't clearly wrong — a pattern that might be fine, a missing edge case that might not matter, a naming choice you disagree with but can't prove is worse. Blocking on it stalls the PR; ignoring it lets it rot silently. This skill gives it a third option: write it down, don't block, move on.

One entry, one line of reasoning, appended immediately. No sweep, no category checklist, no schema validation gate.

Not this skill

If the user says "기술부채 스캔해줘" (repo-wide scan) → redirect to tech-debt-audit. If they say "이건 나중에 봐도 되는 거라 애매한데 부채로 남겨두자" (this one specific thing, unsure, log it) → this skill.

Trigger phrases

이건 기술부채로, 아리까리하니까 일단 부채로, 블로킹 안 하고 부채로 남겨, debt log this, log as tech debt, /zereight-debt-log

Usage pattern: called after a zereight-review pass finishes, once — with the set of items the user already decided are debt-worthy, not blocking. This skill doesn't re-triage during the review; it just files what it's handed.

Ledger

Default location: <repo-root>/TECH_DEBT.md. Create it with the header below on first write; append below that on every subsequent write. Never rewrite existing entries except to change status.

# Tech Debt Ledger

| ID | Date | Location | Note | Why ambiguous | Status |
| --- | --- | --- | --- | --- | --- |

Entry format — one row per item, IDs sequential DEBT-001, DEBT-002, ... (scan existing rows for the highest ID before assigning the next one; never reuse or renumber):

| DEBT-NNN | <ISO date> | <file>:<line> or (repo-wide) | <one-line what/where> | <one-line why you didn't block on it> | open |

Keep the "why ambiguous" cell honest — this is what separates it from a plain TODO. "Might be intentional, couldn't confirm with author" is a good reason. "Didn't want to deal with it" is not — if that's the real reason, say so to the user and let them decide whether it belongs here at all.

Workflow

Log (default action):

1. Confirm the ledger path — TECH_DEBT.md at repo root unless the user names another file.
2. Read the file if it exists; find the highest existing DEBT- ID.
3. Append one row per item. Multiple items in one turn → multiple rows, not one merged row.
4. Confirm to the user: Logged DEBT-NNN. Not blocking the review on this.

List (부채 목록, list debt, 뭐 남겨놨어): Read the ledger, print open rows grouped loosely by area if there are many. Don't re-triage them — just surface what's there.

Resolve (이거 해결됨, DEBT-003 처리함): Flip status to resolved on that row. Don't delete rows — the ledger is a history, not a todo list that empties out.

Promote to ticket — only on explicit request. This skill does not push to Jira/GitHub/Linear on its own. If asked, hand the row's content to whatever ticketing skill is already in play (e.g. bankx-jira in this repo) and let that skill own the actual API call and consent gate.

Boundaries

• Never silently drop a finding instead of logging it — if you're not going to raise it and not going to log it, say that out loud and let the user veto.
• Never use this to bury something you actually believe is wrong. If you're confident it's a bug, that's a review comment, not debt. This skill is for genuine uncertainty, not for softening a real finding.
• One-shot per log call. Don't batch-triage the whole ledger unless asked.
• Read/write only TECH_DEBT.md (or the user-specified ledger). Never touch source files.

Verification

• Ledger file exists at the confirmed path with the header row.
• New rows have sequential, non-reused DEBT- IDs.
• Each row's "why ambiguous" cell states an actual reason, not "TODO".
• User was told the ID(s) just written and that the item is not blocking.