workloglisted

# Record work as a Markdown note (work-docs) Publish a per-issue work record to your **public** `work-docs` repo, so the reasoning behind a change is shareable and linkable from PRs. This complements (does not replace) the internal master DOCX: deep internal analysis stays in the DOCX; a clear, public-safe summary goes here. ## Step 0: Prereqs - The docs repo cloned locally at `${WORK_DOCS_REPO:-$HOME/Devel/work-docs}`, with its `origin` set to your public repo (e.g. `github.com/Srltas/work-docs`). Override the path with `WORK_DOCS_REPO` (the legacy `WORKLOG_DOCS_REPO` also works). Shared with the `note` skill. - Optional: the **jira-fetch** skill, to pull issue context (CBRD only; Hibernate HHH is Atlassian Cloud, not supported by that tool). ## Step 1: Identify the record From `$ARGUMENTS`: an issue key (`<PROJECT>-<N>`, e.g. `CBRD-1234`, `TOOLS-4888`, `APIS-1079`, `CUBRIDQA-123`, `HHH-20527`) or a topic slug, plus an optional short slug. **Write the note in Korean** regardless of the project. The project prefix only decides the folder/file name (see Step 3). ## Step 2: Gather context (optional) For a CUBRID Jira Server issue (CBRD, TOOLS, APIS, CUBRIDQA), pull its summary/description with jira-fetch to seed the note: ```bash bash ~/.claude/skills/jira-fetch/assets/fetch_jira.sh -o /tmp/jira <KEY> ``` (HHH is Atlassian Cloud, which jira-fetch does not support, so write its context from the session instead.) Also use the current session's work (the change, the verif