weekly-reportlisted

# Weekly-report lines from JIRA issues Compress each issue into **one line** for the weekly-report spreadsheet: one line per cell, in the order the keys were given. Draft only, nothing is posted anywhere. ## Step 0: Prereq The **jira-fetch** skill installed at `~/.claude/skills/jira-fetch/` (this skill calls its helper). Its constraints apply: only publicly readable projects (CBRD, TOOLS, APIS, ...) can be read; internal-only projects such as CUBRIDQA fail with `HTTP 401`. ## Step 1: Parse the keys From `$ARGUMENTS`, take every `PROJECT-NUMBER`. Accept commas or spaces, a pasted issue URL, and lower case (`apis-1111` -> `APIS-1111`). Drop duplicates and **keep the order given**: the report rows should match what the user typed. ## Step 2: Fetch all of them in one call ```bash bash ~/.claude/skills/jira-fetch/assets/fetch_jira.sh APIS-1111 TOOLS-4324 ... ``` The helper takes many keys at once, so call it **once** for the whole list. It writes `./jira/<KEY>.md` (title as `# heading`, then the description). Skip any key whose `.md` already exists: do not re-fetch. A key that cannot be read is simply reported as missing, and the rest still succeed. ## Step 3: Write one line per issue Read each `<KEY>.md` and compress it. **The line answers "what is this issue", not "what did I do" or "what is its status".** ``` APIS-1088 JDBC 구버전 PROTOCOL 호환성 코드 제거 TOOLS-4888 CMT 단위 테스트 라이브러리 Java 8 지원 버전으로 업그레이드 ``` Rules: - **Form**: `<KEY> <요약>`, key first, one space, then the sum