@su-record/vibe 2.9.2 → 2.9.3

package/skills/devlog/SKILL.md

@@ -7,11 +7,11 @@ priority: 60
 ---
 # Devlog Auto-Generator
 
-Git 커밋 히스토리를 분석하여 개발일지를 자동 생성하고, 설정된 블로그 레포에 포스트로 저장합니다.
+Analyzes git commit history to automatically generate development logs and saves them as posts to the configured blog repository.
 
 ## Config
 
-`.claude/vibe/config.json`의 `devlog` 섹션:
+`devlog` section in `.claude/vibe/config.json`:
 
 ```json
 {
@@ -32,52 +32,52 @@ Git 커밋 히스토리를 분석하여 개발일지를 자동 생성하고, 설
 
 | Key | Required | Default | Description |
 |-----|----------|---------|-------------|
-| `enabled` | Y | `false` | 활성화 여부 |
-| `targetRepo` | Y | — | 블로그 레포 절대 경로 |
-| `targetDir` | N | `"posts"` | 포스트 저장 디렉토리 |
-| `prefix` | N | `"devlog"` | 파일명 프리픽스 (`{prefix}-{NNNN}.md`) |
-| `interval` | N | `10` | 몇 커밋마다 생성할지 |
-| `autoPush` | N | `false` | targetRepo에 자동 commit+push |
-| `lang` | N | `"ko"` | 작성 언어 |
-| `author` | N | git user.name | 작성자 |
+| `enabled` | Y | `false` | Whether to enable |
+| `targetRepo` | Y | — | Absolute path to the blog repository |
+| `targetDir` | N | `"posts"` | Directory to save posts |
+| `prefix` | N | `"devlog"` | Filename prefix (`{prefix}-{NNNN}.md`) |
+| `interval` | N | `10` | How many commits trigger a generation |
+| `autoPush` | N | `false` | Auto commit+push to targetRepo |
+| `lang` | N | `"ko"` | Writing language |
+| `author` | N | git user.name | Author name |
 | `category` | N | `"dev-log"` | frontmatter category |
-| `tags` | N | `[]` | 기본 태그 (프로젝트명 등 자동 추가) |
+| `tags` | N | `[]` | Default tags (project name etc. auto-added) |
 
 ## Trigger Modes
 
 ### 1. Auto (post-commit hook)
 
-`devlog-gen.js` hook이 매 커밋마다 카운터를 확인하고, `interval`에 도달하면 `llm-orchestrate.js`를 통해 개발일지를 생성합니다.
+The `devlog-gen.js` hook checks the counter on every commit, and when it reaches `interval`, generates a devlog via `llm-orchestrate.js`.
 
 ### 2. Manual
 
-사용자가 직접 `/devlog` 또는 `개발일지 작성` 키워드로 트리거. 마지막 개발일지 이후의 커밋을 모아 즉시 생성합니다.
+User manually triggers via `/devlog` or the `개발일지 작성` keyword. Collects commits since the last devlog and generates immediately.
 
 ## Generation Process
 
 ### Step 1: Collect Commits
 
-마지막 개발일지의 날짜 이후 커밋을 수집합니다:
+Collects commits after the date of the last devlog:
 
 ```bash
-# 마지막 devlog 파일에서 날짜 추출
-# targetRepo/targetDir/{prefix}-NNNN.md 의 frontmatter date
+# Extract date from last devlog file
+# frontmatter date of targetRepo/targetDir/{prefix}-NNNN.md
 git log --oneline --after="{last_date}" --reverse
 ```
 
 ### Step 2: Analyze & Group
 
-- 버전 범프 커밋 식별 (X.Y.Z 패턴)
-- feat/fix/refactor/docs 분류
-- 주요 커밋 선별 (의미 있는 변경)
+- Identify version bump commits (X.Y.Z pattern)
+- Classify by feat/fix/refactor/docs
+- Select notable commits (meaningful changes)
 
 ### Step 3: Generate Markdown
 
-다음 frontmatter 포맷으로 생성:
+Generated with the following frontmatter format:
 
 ```markdown
 ---
-title: "{project_name} 개발일지 #{next_number} - {summary_title} ({interval}개 커밋)"
+title: "{project_name} Devlog #{next_number} - {summary_title} ({interval} commits)"
 date: "{today}"
 category: "{category}"
 description: "{one_line_description}"
@@ -88,31 +88,31 @@ lang: "{lang}"
 
 # {title}
 
-**작업 기간**: {start_date} ~ {end_date}
+**Work period**: {start_date} ~ {end_date}
 
-## 이번 기간 작업 내용
+## Work done this period
 
-### {theme} ({interval}개 커밋)
+### {theme} ({interval} commits)
 
 {overview_paragraph}
 
-| 커밋 | 내용 |
-|------|------|
+| Commit | Description |
+|--------|-------------|
 | `{meaningful_commit_message}` | **{highlight}** |
 ...
 
-## 작업 하이라이트
+## Work highlights
 
 {2-3 highlights with code blocks or diagrams}
 
-## 개발 현황
+## Development status
 
-- **버전**: {start_version} → {end_version}
-- **핵심**: {key_changes}
+- **Version**: {start_version} → {end_version}
+- **Key changes**: {key_changes}
 
 ---
 
-**다음 개발일지**: {prefix}-{next+1} (다음 {interval}개 커밋 후)
+**Next devlog**: {prefix}-{next+1} (after next {interval} commits)
 ```
 
 ### Step 4: Write File
@@ -121,11 +121,11 @@ lang: "{lang}"
 {targetRepo}/{targetDir}/{prefix}-{NNNN}.md
 ```
 
-번호는 기존 파일에서 마지막 번호 + 1로 자동 결정.
+The number is automatically determined as the last existing file number + 1.
 
 ### Step 5: (Optional) Auto Push
 
-`autoPush: true`이면:
+If `autoPush: true`:
 
 ```bash
 cd {targetRepo}
@@ -136,8 +136,8 @@ git push
 
 ## Rules
 
-- **커밋 메시지 원문 보존** — 커밋 메시지를 그대로 인용, 임의 변경 금지
-- **버전 범프 커밋 포함** — 테이블에는 포함하되 하이라이트에서 제외
-- **하이라이트는 최대 3개** — 가장 영향력 있는 변경만 선별
-- **코드 블록 활용** — Before/After 비교, 아키텍처 다이어그램 권장
-- **숫자 강조** — 줄 수 변화(-N줄), 버전 범위, 파일 수 등
+- **Preserve original commit messages** — Quote commit messages verbatim, no arbitrary changes
+- **Include version bump commits** — Include in the table but exclude from highlights
+- **Maximum 3 highlights** — Select only the most impactful changes
+- **Use code blocks** — Before/After comparisons and architecture diagrams are recommended
+- **Emphasize numbers** — Line count changes (-N lines), version ranges, file counts, etc.

package/skills/event-comms/SKILL.md

@@ -80,21 +80,21 @@ SMS, email, and SNS content generation for community events.
 
 ### Confirmation Email Template (D-3)
 ```
-Subject: [{event_name}] 참가 확정 안내
+Subject: [{event_name}] Attendance Confirmation
 
-{attendee_name}님 안녕하세요.
+Hello {attendee_name},
 
-{event_name} {edition}회 참가가 확정되었습니다.
+Your attendance for {event_name} edition {edition} has been confirmed.
 
-■ 일시: {date} {time}
-■ 장소: {venue_detail}
-■ 프로그램:
+■ Date & Time: {date} {time}
+■ Venue: {venue_detail}
+■ Program:
 {timetable}
 
-■ 실시간 질문: {slido_link}
+■ Live Q&A: {slido_link}
 
-당일 뵙겠습니다.
-감사합니다.
+We look forward to seeing you on the day.
+Thank you.
 
 {community_name}
 ```
@@ -106,7 +106,7 @@ Subject: [{event_name}] 참가 확정 안내
 | Platform | Tone | Length | Style |
 |----------|------|--------|-------|
 | LinkedIn | Professional, formal | 300+ chars | Expert participation encouragement |
-| Threads | Casual, hooking | 150-200 chars | "아직 안 봤어?" style |
+| Threads | Casual, hooking | 150-200 chars | "Haven't seen this yet?" style |
 
 ### Post Types
 
@@ -120,12 +120,12 @@ Subject: [{event_name}] 참가 확정 안내
 ```
 {hook_sentence}
 
-{event_name} {edition}회를 소개합니다.
+Introducing {event_name} edition {edition}.
 
 📅 {date} {time}
 📍 {venue}
 
-이번 주제: {topic}
+This session's topic: {topic}
 
 {speaker_intro}
 
@@ -136,7 +136,7 @@ Subject: [{event_name}] 참가 확정 안내
 ```
 {hook_casual}
 
-{event_name} {edition}회 열린다!
+{event_name} edition {edition} is happening!
 
 {date} {time}
 {venue_short}
@@ -152,6 +152,16 @@ Subject: [{event_name}] 참가 확정 안내
 3. Next event preview
 4. Thank you + community link
 
+## Error Recovery
+
+| Failure | Recovery |
+|---------|----------|
+| Aligo API timeout/error | Retry once after 5s. If still failing, output the SMS text as plain text for manual sending |
+| Aligo auth error | Prompt user to verify API key in `~/.vibe/config.json` |
+| Gmail auth expired | Prompt user to re-authenticate: `! gemini auth login` or refresh OAuth token |
+| Gmail quota exceeded | Save email as `.eml` file for manual sending later |
+| SNS post generation fails | Output post text as markdown for manual copy-paste |
+
 ## API Keys Required
 
 | Key | Service | Required |

package/skills/event-ops/SKILL.md

@@ -64,12 +64,12 @@ Nametags, checklists, operational slides, Slido configuration, image generation,
 Fixed 4 items for all offline events:
 
 ```markdown
-## D-1 체크리스트
+## D-1 Checklist
 
-- [ ] 생수/간식/식사 주문
-- [ ] 이름표 출력
-- [ ] 행사 운영 슬라이드
-- [ ] 스크린/카메라/삼각대 준비
+- [ ] Order water/snacks/meals
+- [ ] Print nametags
+- [ ] Prepare event operational slides
+- [ ] Set up screen/camera/tripod
 ```
 
 ## Operational Slides
@@ -96,30 +96,30 @@ N+2. Thank you + community links
 
 **MDC (3 speakers)**
 ```
-19:00-19:10  오프닝 + 네트워킹
-19:10-19:35  세션 1: {speaker1_name} — {topic1}
-19:35-20:00  세션 2: {speaker2_name} — {topic2}
-20:00-20:25  세션 3: {speaker3_name} — {topic3}
+19:00-19:10  Opening + Networking
+19:10-19:35  Session 1: {speaker1_name} — {topic1}
+19:35-20:00  Session 2: {speaker2_name} — {topic2}
+20:00-20:25  Session 3: {speaker3_name} — {topic3}
 20:25-20:40  Q&A + Slido
-20:40-21:00  네트워킹
+20:40-21:00  Networking
 ```
 
 **Webinar (1-2 speakers)**
 ```
-19:30-19:35  오프닝
-19:35-20:30  세션: {speaker_name} — {topic}
+19:30-19:35  Opening
+19:35-20:30  Session: {speaker_name} — {topic}
 20:30-20:50  Q&A
-20:50-21:00  마무리
+20:50-21:00  Closing
 ```
 
 **DWK (1-3 speakers + discussion)**
 ```
-14:00-14:10  오프닝 + 아이스브레이커
-14:10-14:40  세션 1: {speaker1_name} — {topic1}
-14:40-15:10  세션 2: {speaker2_name} — {topic2}
-15:10-15:30  쉬는 시간
-15:30-16:00  토론 세션
-16:00-16:30  네트워킹
+14:00-14:10  Opening + Icebreaker
+14:10-14:40  Session 1: {speaker1_name} — {topic1}
+14:40-15:10  Session 2: {speaker2_name} — {topic2}
+15:10-15:30  Break
+15:30-16:00  Discussion session
+16:00-16:30  Networking
 ```
 
 ## Slido Configuration
@@ -196,3 +196,12 @@ Free — no settlement needed
 - DM draft (short, 5-line version) + email draft (formal)
 - Auto-reference existing contact history (for re-outreach)
 - Business card image + LinkedIn URL → `data/speakers/{name}.json` accumulation
+
+## Error Recovery
+
+| Failure | Recovery |
+|---------|----------|
+| Gemini image API unavailable | Skip image generation, use text-only placeholder slide with community colors |
+| Gemini image quality too low | Retry with simplified prompt (remove detail, keep core subject) |
+| PPTX generation error | Output slide content as markdown with speaker notes for manual assembly |
+| Nametag HTML render issue | Simplify to basic table layout, remove custom fonts |

package/skills/event-planning/SKILL.md

@@ -88,12 +88,24 @@ When user says "MDC 준비해줘" or similar:
 }
 ```
 
+## State Management
+
+**Location**: `.claude/vibe/.event_state.json` (project-local, gitignored)
+
+### Error Recovery
+
+| Failure | Recovery |
+|---------|----------|
+| State file missing | Regenerate from scratch by re-reading event config and completed artifacts |
+| State file corrupted (invalid JSON) | Delete corrupted file, regenerate from current directory state |
+| State phase mismatch | Trust directory artifacts over state file — scan for completed outputs and infer current phase |
+
 ## Community Tone Guide
 
 | | MDC | Webinar | DWK |
 |---|---|---|---|
 | Tone | Professional, practical, formal | Friendly, casual, emoji-ok | Warm, inclusive, "together" |
-| Example | "실무에서 바로 적용" | "퇴근 후 편하게" | "데이터를 좋아하는 여성들" |
+| Example | "Apply directly in your work" | "Relax after work" | "Women who love data" |
 | Brand color | #ff6b35 (orange) | #a78bfa (purple) | #34d399 (mint) |
 
 ## Community Brand Names

package/skills/priority-todos/SKILL.md

@@ -34,7 +34,7 @@ priority: 60
 ## Workflow
 
 ```
-/vibe.review → Creates P1/P2/P3 todo files + updates index.md
+vibe.review (skill) → Creates P1/P2/P3 todo files + updates index.md
      ↓
 Fix P1 first (blocks merge)
      ↓