@su-record/vibe 3.2.64 → 4.0.1

package/skills/vibe.devlog/SKILL.md

@@ -1,147 +0,0 @@
----
-name: vibe.devlog
-invocation: [auto]
-tier: standard
-description: "Use when accumulated git commits must be turned into a devlog post or the configured N-commit publication threshold is reached."
-triggers: [devlog, 개발일지, dev log, devlog 작성, 개발일지 작성]
-priority: 60
----
-# Devlog Auto-Generator
-
-## Done Criteria
-
-- [ ] 처리한 commit 범위가 산출물에 기록되어 있다.
-- [ ] devlog Markdown이 설정된 대상 경로에 존재한다.
-- [ ] 이미 처리한 commit이 중복 포함되지 않았다.
-- [ ] 설정된 frontmatter 필드가 모두 채워져 있다.
-
-Analyzes git commit history to automatically generate development logs and saves them as posts to the configured blog repository.
-
-## Config
-
-`devlog` section in `.vibe/config.json`:
-
-```json
-{
-  "devlog": {
-    "enabled": true,
-    "targetRepo": "/absolute/path/to/blog-repo",
-    "targetDir": "posts",
-    "prefix": "devlog",
-    "interval": 10,
-    "autoPush": false,
-    "lang": "ko",
-    "author": "Su",
-    "category": "dev-log",
-    "tags": []
-  }
-}
-```
-
-| Key | Required | Default | Description |
-|-----|----------|---------|-------------|
-| `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 | `[]` | Default tags (project name etc. auto-added) |
-
-## Trigger Modes
-
-### 1. Auto (lifecycle acceleration)
-
-When lifecycle hooks are available, `devlog-gen.js` may check the counter after
-each commit and invoke `llm-orchestrate.js`. Hooks are acceleration only: before
-declaring the devlog workflow complete, explicitly count commits since the last
-devlog and run the same generation step when the count reaches `interval`.
-
-### 2. Manual
-
-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
-# 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
-
-- Identify version bump commits (X.Y.Z pattern)
-- Classify by feat/fix/refactor/docs
-- Select notable commits (meaningful changes)
-
-### Step 3: Generate Markdown
-
-Generated with the following frontmatter format:
-
-```markdown
----
-title: "{project_name} Devlog #{next_number} - {summary_title} ({interval} commits)"
-date: "{today}"
-category: "{category}"
-description: "{one_line_description}"
-tags: [{project_tags}, {auto_detected_tags}]
-author: "{author}"
-lang: "{lang}"
----
-
-# {title}
-
-**Work period**: {start_date} ~ {end_date}
-
-## Work done this period
-
-### {theme} ({interval} commits)
-
-{overview_paragraph}
-
-| Commit | Description |
-|--------|-------------|
-| `{meaningful_commit_message}` | **{highlight}** |
-...
-
-## Work highlights
-
-{2-3 highlights with code blocks or diagrams}
-
-## Development status
-
-- **Version**: {start_version} → {end_version}
-- **Key changes**: {key_changes}
-
----
-
-**Next devlog**: {prefix}-{next+1} (after next {interval} commits)
-```
-
-### Step 4: Write File
-
-```
-{targetRepo}/{targetDir}/{prefix}-{NNNN}.md
-```
-
-The number is automatically determined as the last existing file number + 1.
-
-### Step 5: (Optional) Auto Push
-
-If `autoPush: true`, read `references/auto-push.md` and require normal external-state confirmation. Calls with `autoPush: false` do not load it.
-
-## Rules
-
-- **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/vibe.devlog/references/auto-push.md

@@ -1,10 +0,0 @@
-# Optional Devlog Auto-Push
-
-Load only when `devlog.autoPush` is `true`. External push still requires confirmation.
-
-```bash
-cd {targetRepo}
-git add {targetDir}/{prefix}-{NNNN}.md
-git commit -m "post: Add {prefix} #{NNNN}"
-git push
-```

package/skills/vibe.docs/SKILL.md

@@ -1,121 +0,0 @@
----
-name: vibe.docs
-description: Use when README, guides, architecture, release notes, agent instructions, diagrams, or codemaps must be generated or synchronized with the actual codebase.
-argument-hint: "readme, guide, arch, release, agent, diagram, or codemaps"
-user-invocable: true
----
-
-# /vibe.docs
-
-Generate or update project documentation by analyzing the actual codebase.
-
-## Usage
-
-```
-/vibe.docs readme     # README.md 생성/갱신
-/vibe.docs guide      # 사용자 가이드 (docs/GUIDE.md)
-/vibe.docs arch       # 아키텍처 문서 + Mermaid 다이어그램 (docs/ARCHITECTURE.md)
-/vibe.docs release    # 릴리즈 노트 (git history 기반)
-/vibe.docs agent      # CLAUDE.md / AGENTS.md 생성·동기화 (agents-md 검증 필수)
-/vibe.docs diagram    # Mermaid 다이어그램 (architecture/ER/flow/seq) → .vibe/diagrams/
-/vibe.docs codemaps   # 코드베이스 구조 자동 문서화 → docs/CODEMAPS/
-```
-
-## Pipeline Position
-
-```
-/vibe.spec    → Design (what to build)
-/vibe.run     → Implement (build it)
-/vibe.trace   → Verify (prove it works)
-/vibe.docs    → Document (explain it)
-```
-
----
-
-Execute the bundled implementation below — subcommand에 따라 해당 섹션 실행
-
-ARGUMENTS: $ARGUMENTS
-
-## Bundled implementation
-
-
-# vibe.docs — Project Documentation Generator
-
-Generate or update project documentation by analyzing the actual codebase.
-
-## Subcommands
-
-## Subcommands (선택된 하나만 로드)
-
-한 번의 호출은 서브커맨드 **하나만** 실행한다. 해당 reference 하나만 읽고 나머지 6개는 읽지 않는다.
-
-| 서브커맨드 | 산출물 | 본문 |
-|---|---|---|
-| `readme` | README.md | `references/readme.md` |
-| `guide` | 사용자 가이드 | `references/guide.md` |
-| `arch` | 아키텍처 문서 | `references/arch.md` |
-| `agent` | CLAUDE.md / AGENTS.md | `references/agent.md` |
-| `release` | 릴리스 노트 / CHANGELOG | `references/release.md` |
-| `diagram` | 다이어그램 | `references/diagram.md` |
-| `codemaps` | 코드맵 | `references/codemaps.md` |
-
-서브커맨드 없이 호출되면 무엇을 생성할지 사용자에게 묻는다 — 전부 생성하지 않는다.
-
-## Pipeline Integration
-
-`/vibe.docs` completes the development pipeline:
-
-```
-/vibe.spec    → Design (what to build)
-/vibe.run     → Implement (build it)
-/vibe.trace   → Verify (prove it works)
-/vibe.docs    → Document (explain it)
-```
-
-### Auto-trigger after `/vibe.trace`
-
-When `/vibe.trace` completes with all scenarios passing, suggest:
-> "All scenarios verified. Run `/vibe.docs readme` to update documentation?"
-
-## Guidelines
-
-### DO
-- Read the actual codebase before generating — never guess
-- Preserve existing documentation that's still accurate
-- Include concrete code examples from the actual project
-- Keep language consistent with project (Korean/English based on CLAUDE.md)
-- For `/vibe.docs release` (changelog mode), follow `references/api-docs-changelog.md` natively — no dedicated agent
-- For API-heavy projects (api-docs mode), follow `references/api-docs-changelog.md` natively
-- For `/vibe.docs arch` and `/vibe.docs diagram` Mermaid generation, follow `references/diagram-spec.md` natively
-- Use the `agents-md` skill for `/vibe.docs agent` — applies equally to CLAUDE.md and AGENTS.md
-
-### DON'T
-- Don't generate placeholder text ("Lorem ipsum", "TODO: fill in")
-- Don't document internal implementation details in user-facing docs
-- Don't create files without reading existing ones first
-- Don't assume features — verify by reading code
-
-## Quality Checklist
-
-Before finalizing any document:
-
-- [ ] All code examples are runnable (copy-paste ready)
-- [ ] Installation steps tested against package.json
-- [ ] Links and paths are valid
-- [ ] No placeholder text remaining
-- [ ] Consistent with project language (Korean/English)
-
-## Done Criteria
-
-- [ ] The requested document exists at its specified path.
-- [ ] Example commands, paths, and identifiers match the repository.
-- [ ] No placeholder or unverified feature claim remains.
-- [ ] Internal links and file paths resolve to real targets.
-- [ ] The document preserves the project's existing language.
-
-## 체인 의존 (reference 안에서 호출되는 스킬)
-
-reference 로 내려간 절차가 다른 스킬을 체인 호출한다. **설치 무결성 검사가 추적할 수 있도록 여기에 선언한다** —
-선언이 없으면 그 스킬이 미설치여도 아무도 잡지 못한다.
-
-- Load skill `vibe.agents-md` — `references/agent.md` 단계에서 호출

package/skills/vibe.docs/references/agent.md

@@ -1,59 +0,0 @@
-# /vibe.docs agent — Agent Instruction Files (CLAUDE.md / AGENTS.md)
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`agent` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs agent` — Agent Instruction Files (CLAUDE.md / AGENTS.md)
-
-**CLI ↔ file mapping:**
-
-| CLI | File | Support |
-|---|---|---|
-| Claude Code | `CLAUDE.md` | 100% (Primary) |
-| Codex | `AGENTS.md` | 100% (Primary) |
-| Antigravity CLI | `GEMINI.md` | 100% |
-
-Cursor is not supported — do not generate or check Cursor-specific context files.
-
-**Source of truth:**
-- **`CLAUDE.md` is the content SSOT.** Always edit it first; `AGENTS.md` is a regenerated derivative.
-- Behavioral block: `skills/vibe.docs/templates/behavioral-principles.md` (4 Karpathy principles, wrapped in `<!-- VIBE-BEHAVIORAL:START/END -->` markers).
-- **번역 규칙이 파일로 존재하면 그 파일이 SSOT다.** 프로젝트 루트에 `scripts/agents-md-rules.json` 이 있으면
-  아래 4·5번 손 치환 목록을 쓰지 않고 `npm run gen:agents-md` 로 생성한다 — 규칙을 두 곳에 적으면
-  그 순간 두 벌이 되고, 어느 쪽이 맞는지 판정할 수단이 사라진다. 검증은 `npm run gen:agents-md:check`.
-  (vibe 저장소 자신이 이 경로다. 규칙 파일이 없는 프로젝트는 4·5번을 그대로 적용한다.)
-
-**Procedure (applies to both creation and modification):**
-
-1. **Detect state** — check which of `CLAUDE.md` / `AGENTS.md` / `GEMINI.md` exist in project root. **`CLAUDE.md` is always the SSOT**; if missing, create it first (never derive from AGENTS.md).
-2. **For `AGENTS.md`**:
-   - **If missing** → create by cloning `CLAUDE.md` + applying CLI substitution (below).
-   - **If exists** → regenerate from current `CLAUDE.md` + substitution, preserving user-specific additions outside the VIBE block.
-3. **For `GEMINI.md`**:
-   - **If missing** → create by cloning `CLAUDE.md` + applying Antigravity substitution.
-   - **If exists** → regenerate from current `CLAUDE.md` + substitution, preserving user-specific additions outside the VIBE block.
-4. **CLI substitution for `AGENTS.md`** (Codex): `Claude Code` → `Codex` · `~/.claude/` → `~/.codex/` · `.claude/` → `.codex/` · `CLAUDE.md` → `AGENTS.md`. `CLAUDE.md` itself gets no substitution.
-5. **CLI substitution for `GEMINI.md`** (Antigravity): `Claude Code` → `Antigravity CLI` · `~/.claude/` → `~/.gemini/` · `.claude/` → `.gemini/` · `CLAUDE.md` → `GEMINI.md`.
-6. **Validate every touched file (whether newly created or modified)** via the `agents-md` skill — see validation block below. **Never write or save without running this step.**
-7. Report per file: created / updated / skipped / validation warnings.
-
-**Idempotent:** Re-running re-syncs the behavioral block and re-applies substitutions without duplication.
-
-**Mandatory validation (every create & every update) — Load skill `vibe.agents-md`:**
-
-- Size target 60–150 lines (Optimal). Warn at 200+, force split/trim at 300+.
-- 4-question check per line (outside `VIBE-BEHAVIORAL` block):
-  - Would the agent make a mistake without this? (No → delete)
-  - Needed every session? (No → move to SPEC/plan)
-  - Can a linter/hook replace it? (Yes → move)
-  - Discoverable from code? (Yes → delete)
-- Lost-in-the-Middle: critical rules at top, frequently-violated rules at bottom.
-- Addy Osmani test: "Can the agent discover this by reading the code?" → Yes = delete.
-- Strip tech-stack name-drops already stated in `package.json`.
-
-Report line ranges to trim per file. Do not auto-delete; surface findings for user approval before finalizing.
-
-**When to run:**
-- After `vibe init` / `vibe update` if `CLAUDE.md` or `AGENTS.md` is missing or out of sync.
-- After upgrading `@su-record/vibe` when the behavioral template changes.
-- Whenever the SSOT file is edited — re-sync `AGENTS.md`.
-- User explicitly asks to refresh agent instructions.

package/skills/vibe.docs/references/api-docs-changelog.md

@@ -1,34 +0,0 @@
-# docs — API Docs & Changelog Spec
-
-> Loaded by docs SKILL.md for `/vibe.docs release` (changelog mode) and API-heavy projects (api-docs mode) — documentation rules for the two artifacts that go stale fastest: API docs and changelogs.
-
-## API Mode
-
-Walk the route handlers/controllers in the given scope and document each
-endpoint: method + path, auth requirement, parameters (path/query/body with
-types, required vs optional, enum values), success and error responses (all
-status codes actually returned), and a runnable example (curl or fetch). List
-endpoints that exist in code but lack documentation — the gap list is as
-valuable as the docs.
-
-## Changelog Mode
-
-From `git diff` and `git log`, classify changes as breaking / added /
-changed / fixed / performance / internal / dependencies. Recommend the
-semantic version bump with a one-line reason. Every breaking change gets
-migration steps; every fix states old vs new behavior.
-
-## Constraints
-
-Return documentation as text output only — never create or write files; the
-calling command decides where content lands. Descriptions are user-facing:
-what changed for the consumer, not which internal function was refactored
-(pure refactors go under Internal, briefly). Document what the code actually
-does, not what comments claim — when they disagree, flag the discrepancy
-rather than picking one silently.
-
-## Done
-
-- API mode: every endpoint in scope documented or explicitly listed as an undocumented gap
-- Changelog mode: all changes classified, version bump recommended with reason, breaking changes have migration steps
-- Output is paste-ready text; zero files created

package/skills/vibe.docs/references/arch.md

@@ -1,28 +0,0 @@
-# /vibe.docs arch — Architecture Documentation
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`arch` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs arch` — Architecture Documentation
-
-Generate architecture overview with diagrams:
-
-1. **Module map**: Directory structure → responsibility mapping
-2. **Dependency graph**: Import analysis → Mermaid diagram
-3. **Data flow**: Entry points → processing → output
-4. **Key decisions**: Extract from CLAUDE.md and code comments
-
-Output: `docs/ARCHITECTURE.md`
-
-**Mermaid diagram generation:**
-```
-File-pattern search: src/**/ → module list
-Text search: pattern="^import .+ from" → dependency edges
-Full-file reading: CLAUDE.md → architecture notes
-
-Generate:
-graph TD
-    CLI[CLI Commands] --> Core[Core Logic]
-    Core --> Infra[Infrastructure]
-    Infra --> DB[(Database)]
-    Infra --> API[External APIs]
-```

package/skills/vibe.docs/references/codemaps-output.md

@@ -1,23 +0,0 @@
-# docs — Codemaps: Generated Files & Contents
-
-> Loaded by docs SKILL.md `codemaps` mode — full generated-files tree, per-file contents, and tools used.
-
-**Generated Files:**
-```
-docs/CODEMAPS/
-├── INDEX.md          # Overview of all areas
-├── frontend.md       # Frontend structure
-├── backend.md        # API/backend structure
-├── database.md       # Schema documentation
-└── integrations.md   # External services
-```
-
-**Each file contains:**
-- Module table (name, path, description)
-- Data flow diagram (Mermaid)
-- Dependencies list
-- Related areas
-
-**Tools Used:**
-- ts-morph (TypeScript AST)
-- madge (dependency graph)

package/skills/vibe.docs/references/codemaps.md

@@ -1,17 +0,0 @@
-# /vibe.docs codemaps — Codemaps Generation
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`codemaps` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs codemaps` — Codemaps Generation
-
-Generate auto-documentation from codebase structure directly (native
-capability — no dedicated agent).
-
-**Output Location:** `docs/CODEMAPS/`
-
-> Read `references/codemaps-output.md` for the full generated-files tree, per-file contents, and tools used.
-
-**Example:**
-```
-/vibe.docs codemaps
-```

package/skills/vibe.docs/references/diagram-spec.md

@@ -1,34 +0,0 @@
-# docs — Diagram Generation Spec
-
-> Loaded by docs SKILL.md `diagram` mode — Mermaid diagram generation rules (architecture, ERD, flowcharts, sequence).
-
-Produce a Mermaid diagram that reflects the actual code, not a generic
-picture. Ground it in sources first: folder structure and imports for
-architecture; `models/`, `migrations/`, `schema.*`, ORM definitions for ERDs;
-the real branch/return structure of the code for flowcharts.
-
-## Output Conventions
-
-- Architecture → `graph TB` with layers top-to-bottom (client → API → data);
-  label edges with the interaction (`HTTP`, `Query`, `Cache`)
-- ERD → `erDiagram` with cardinality (`||--o{`), PK/FK/UK markers, and the
-  fields that matter for understanding relationships (not every column)
-- Flows → `flowchart TD` with decision diamonds carrying their conditions on
-  the edge labels
-- One diagram per concern — split rather than cram; keep each diagram readable
-  at ~20 nodes or fewer
-- Save to `.vibe/diagrams/{type}-{YYYY-MM-DD}.md` and note render options
-  (GitHub/GitLab render Mermaid natively; otherwise https://mermaid.live/)
-
-## Constraints
-
-Accuracy over completeness: omit elements you couldn't verify in the code
-rather than inventing plausible boxes; if a relationship is inferred rather
-than read, mark it. Valid Mermaid syntax is non-negotiable — quote labels
-containing special characters.
-
-## Done
-
-- Diagram matches verifiable code structure (each node traceable to a file/table/function)
-- Mermaid syntax is valid and renders
-- Saved to `.vibe/diagrams/` with a one-paragraph summary of what it shows

package/skills/vibe.docs/references/diagram.md

@@ -1,24 +0,0 @@
-# /vibe.docs diagram — Diagram Generation
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`diagram` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs diagram` — Diagram Generation
-
-Generate Mermaid diagrams for architecture, ERD, flowchart, or sequence
-visualization directly (native capability — no dedicated agent). Ground the
-diagram in sources first: folder structure and imports for architecture;
-`models/`, `migrations/`, `schema.*`, ORM definitions for ERDs; the real
-branch/return structure of the code for flowcharts.
-
-**Options:**
-- `/vibe.docs diagram` (default): Architecture overview
-- `/vibe.docs diagram --er`: Entity-Relationship Diagram
-- `/vibe.docs diagram --flow`: Flowchart
-- `/vibe.docs diagram --seq`: Sequence Diagram
-
-> Read `references/diagram-spec.md` for the full output conventions (Mermaid syntax per diagram type, save location, accuracy constraints).
-
-**Example:**
-```
-/vibe.docs diagram --er
-```

package/skills/vibe.docs/references/guide.md

@@ -1,23 +0,0 @@
-# /vibe.docs guide — User Guide
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`guide` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs guide` — User Guide
-
-Generate a step-by-step user guide:
-
-1. **Installation**: Detect package manager, prerequisites
-2. **Configuration**: Find all config files, document each option
-3. **Usage**: Extract CLI commands or API usage patterns
-4. **FAQ**: Common issues from error handling patterns
-5. **Troubleshooting**: Known edge cases from test files
-
-Output: `docs/GUIDE.md`
-
-**Analysis approach:**
-```
-Full-file reading: package.json → bin, scripts, peerDependencies
-File-pattern search: src/cli/commands/*.ts → CLI command list
-Text search: pattern="throw new|Error\(" → common error scenarios
-Text search: pattern="(process\.env|config)\.\w+" → configuration options
-```

package/skills/vibe.docs/references/readme.md

@@ -1,45 +0,0 @@
-# /vibe.docs readme — README Generation
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`readme` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs readme` — README Generation
-
-Analyze the codebase and generate a complete README.md:
-
-1. **Detect project nature**: Read package.json, CLAUDE.md, existing README
-2. **Extract key info**: Tech stack, installation, usage, API surface
-3. **Generate sections**:
-
-```markdown
-# Project Name
-> One-line description from package.json
-
-## What is this?
-[2-3 sentences explaining the problem and solution]
-
-## Quick Start
-[Installation + minimal usage example]
-
-## Features
-[Auto-detected from codebase — exported functions, CLI commands, API endpoints]
-
-## Architecture
-[High-level module diagram if 5+ source directories]
-
-## Configuration
-[Detected config files and their purposes]
-
-## Development
-[Build, test, lint commands from package.json scripts]
-
-## License
-```
-
-**Analysis approach:**
-```
-Full-file reading: package.json → name, description, scripts, dependencies
-File-pattern search: src/**/*.ts → module structure
-Text search: pattern="export (function|class|const)" → public API surface
-Text search: pattern="(app|router)\.(get|post|put|delete)" → API endpoints
-Full-file reading: CLAUDE.md → project conventions
-```

package/skills/vibe.docs/references/release.md

@@ -1,31 +0,0 @@
-# /vibe.docs release — Release Notes
-
-> vibe.docs SKILL.md 의 서브커맨드 표에서 **`release` 가 선택됐을 때만** 로드한다.
-
-### `/vibe.docs release` — Release Notes
-
-Generate release notes from git history:
-
-1. **Collect**: `git log` since last tag
-2. **Classify**: feat/fix/refactor/docs/chore from commit messages
-3. **Group**: By category with breaking changes highlighted
-4. **Format**: Semantic versioning suggestion
-
-Output: `RELEASE_NOTES.md` or append to `CHANGELOG.md`
-
-**Output format:**
-```markdown
-## [x.y.z] - YYYY-MM-DD
-
-### Breaking Changes
-- ...
-
-### Features
-- feat: description (#PR)
-
-### Bug Fixes
-- fix: description (#PR)
-
-### Other
-- refactor/docs/chore items
-```