@nclamvn/vibecode-cli 1.7.0 → 1.8.1

package/docs-site/blog/2019-05-29-long-blog-post.md

@@ -1,44 +0,0 @@
----
-slug: long-blog-post
-title: Long Blog Post
-authors: yangshun
-tags: [hello, docusaurus]
----
-
-This is the summary of a very long blog post,
-
-Use a `<!--` `truncate` `-->` comment to limit blog post size in the list view.
-
-<!-- truncate -->
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet

package/docs-site/blog/2021-08-01-mdx-blog-post.mdx

@@ -1,24 +0,0 @@
----
-slug: mdx-blog-post
-title: MDX Blog Post
-authors: [slorber]
-tags: [docusaurus]
----
-
-Blog posts support [Docusaurus Markdown features](https://docusaurus.io/docs/markdown-features), such as [MDX](https://mdxjs.com/).
-
-:::tip
-
-Use the power of React to create interactive blog posts.
-
-:::
-
-{/* truncate */}
-
-For example, use JSX to create an interactive button:
-
-```js
-<button onClick={() => alert('button clicked!')}>Click me!</button>
-```
-
-<button onClick={() => alert('button clicked!')}>Click me!</button>

package/docs-site/blog/2021-08-26-welcome/index.md

@@ -1,29 +0,0 @@
----
-slug: welcome
-title: Welcome
-authors: [slorber, yangshun]
-tags: [facebook, hello, docusaurus]
----
-
-[Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog).
-
-Here are a few tips you might find useful.
-
-<!-- truncate -->
-
-Simply add Markdown files (or folders) to the `blog` directory.
-
-Regular blog authors can be added to `authors.yml`.
-
-The blog post date can be extracted from filenames, such as:
-
-- `2019-05-30-welcome.md`
-- `2019-05-30-welcome/index.md`
-
-A blog post folder can be convenient to co-locate blog post images:
-
-![Docusaurus Plushie](./docusaurus-plushie-banner.jpeg)
-
-The blog supports tags as well!
-
-**And if you don't want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config.

package/docs-site/blog/authors.yml

@@ -1,25 +0,0 @@
-yangshun:
-  name: Yangshun Tay
-  title: Ex-Meta Staff Engineer, Co-founder GreatFrontEnd
-  url: https://linkedin.com/in/yangshun
-  image_url: https://github.com/yangshun.png
-  page: true
-  socials:
-    x: yangshunz
-    linkedin: yangshun
-    github: yangshun
-    newsletter: https://www.greatfrontend.com
-
-slorber:
-  name: Sébastien Lorber
-  title: Docusaurus maintainer
-  url: https://sebastienlorber.com
-  image_url: https://github.com/slorber.png
-  page:
-    # customize the url of the author page at /blog/authors/<permalink>
-    permalink: '/all-sebastien-lorber-articles'
-  socials:
-    x: sebastienlorber
-    linkedin: sebastienlorber
-    github: slorber
-    newsletter: https://thisweekinreact.com

package/docs-site/blog/tags.yml

@@ -1,19 +0,0 @@
-facebook:
-  label: Facebook
-  permalink: /facebook
-  description: Facebook tag description
-
-hello:
-  label: Hello
-  permalink: /hello
-  description: Hello tag description
-
-docusaurus:
-  label: Docusaurus
-  permalink: /docusaurus
-  description: Docusaurus tag description
-
-hola:
-  label: Hola
-  permalink: /hola
-  description: Hola tag description

package/docs-site/docs/commands/agent.md

@@ -1,162 +0,0 @@
----
-sidebar_position: 12
----
-
-# vibecode agent
-
-**Agent Mode** - Autonomous multi-module builder with self-healing.
-
-## Synopsis
-
-```bash
-vibecode agent <description> [options]
-```
-
-## Description
-
-The `agent` command is designed for complex projects with multiple modules. It decomposes your project into independent modules, builds them sequentially, and uses self-healing to recover from errors.
-
-## Arguments
-
-| Argument | Description |
-|----------|-------------|
-| `description` | Description of the project to build |
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `-n, --new` | Create new project directory |
-| `-v, --verbose` | Show detailed progress |
-| `--analyze` | Analyze project without building |
-| `--status` | Show agent status and memory |
-| `--report` | Export memory report |
-| `--clear` | Clear agent memory |
-| `--force` | Force operation |
-| `--json` | Output as JSON |
-| `--max-retries <n>` | Max retries per module (default: 3) |
-| `--skip-tests` | Skip tests after each module |
-| `--continue` | Continue on module failure |
-
-## Examples
-
-### Build Complex Project
-
-```bash
-vibecode agent "E-commerce platform with user auth, product catalog, shopping cart, and checkout"
-```
-
-### Create New Project
-
-```bash
-vibecode agent "Blog platform with CMS" --new
-```
-
-### Analyze Without Building
-
-```bash
-vibecode agent "My project" --analyze
-```
-
-### Check Agent Status
-
-```bash
-vibecode agent --status
-```
-
-### Export Report
-
-```bash
-vibecode agent --report
-```
-
-## How It Works
-
-### 1. Decomposition
-
-The agent analyzes your description and breaks it into modules:
-
-```
-📦 Project: E-commerce Platform
-├── 🔐 auth          (User authentication)
-├── 📦 products      (Product catalog)
-├── 🛒 cart          (Shopping cart)
-├── 💳 checkout      (Payment processing)
-└── 📊 admin         (Admin dashboard)
-```
-
-### 2. Sequential Building
-
-Each module is built in dependency order with its own:
-- Requirements capture
-- Code generation
-- Test execution
-- Verification
-
-### 3. Self-Healing
-
-If a module fails:
-1. Analyze the error
-2. Generate fix
-3. Retry build
-4. Max 3 attempts per module
-
-### 4. Memory System
-
-The agent remembers:
-- Successful patterns
-- Common errors
-- Fix strategies
-
-## Progress Dashboard
-
-```
-╭────────────────────────────────────────────────────────────╮
-│  🤖 VIBECODE AGENT                                         │
-│                                                            │
-│  Project: e-commerce-platform                              │
-│  Mode: build                                               │
-│                                                            │
-│  [████████████████░░░░░░░░░░░░░░░░░░░░░░]  40%             │
-│                                                            │
-│  ✓ auth                                                    │
-│  ✓ products                                                │
-│  ◐ cart (building...)                                      │
-│  ○ checkout                                                │
-│  ○ admin                                                   │
-│                                                            │
-│  Elapsed: 5m 32s     │  ETA: ~8m remaining                 │
-│                                                            │
-╰────────────────────────────────────────────────────────────╯
-```
-
-## Memory Report
-
-```bash
-vibecode agent --report
-```
-
-Output:
-```markdown
-# Vibecode Agent Memory Report
-
-## Statistics
-- Total builds: 15
-- Success rate: 87%
-- Modules built: 42
-
-## Common Patterns
-- Next.js App Router: 8 times
-- Prisma + PostgreSQL: 5 times
-- Tailwind CSS: 12 times
-
-## Learned Fixes
-- TypeScript strict mode: 3 applications
-- ESLint config: 2 applications
-```
-
-## See Also
-
-- [Agent Mode Guide](../guides/agent-mode) - In-depth guide
-- [go](./go) - For simpler single-module projects
-- [debug](./debug) - For fixing issues

package/docs-site/docs/commands/assist.md

@@ -1,71 +0,0 @@
----
-sidebar_position: 14
----
-
-# vibecode assist
-
-**Expert Mode** - Direct Claude Code access with project context.
-
-## Synopsis
-
-```bash
-vibecode assist [prompt...] [options]
-```
-
-## Alias
-
-```bash
-vibecode expert [prompt...]
-```
-
-## Description
-
-The `assist` command provides direct access to Claude Code with full project context injected. Use it for quick questions, code explanations, or custom tasks.
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--no-context` | Skip context injection |
-
-## Examples
-
-### Ask a Question
-
-```bash
-vibecode assist "How do I add authentication to this app?"
-```
-
-### Code Explanation
-
-```bash
-vibecode assist "Explain the user service module"
-```
-
-### Custom Task
-
-```bash
-vibecode assist "Add error handling to all API routes"
-```
-
-### Without Context
-
-```bash
-vibecode assist "What is the best way to handle state in React?" --no-context
-```
-
-## Context Injection
-
-By default, `assist` injects project context including:
-
-- Current state and session info
-- Contract and blueprint (if available)
-- Recent build history
-- Error patterns
-
-This helps Claude Code provide more relevant responses.
-
-## See Also
-
-- [debug](./debug) - For bug fixing
-- [go](./go) - For building new features

package/docs-site/docs/commands/build.md

@@ -1,53 +0,0 @@
----
-sidebar_position: 7
----
-
-# vibecode build
-
-Manage build process and capture evidence.
-
-## Synopsis
-
-```bash
-vibecode build [options]
-```
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `-s, --start` | Start build process |
-| `-c, --complete` | Mark build complete |
-| `-e, --evidence` | Capture evidence snapshot |
-| `-a, --auto` | Auto-build with Claude Code |
-| `-i, --iterate` | Build-test-fix loop |
-| `-m, --max <n>` | Max iterations |
-| `--strict` | Exit with error if tests fail |
-| `--provider <name>` | Provider (default: claude-code) |
-
-## Examples
-
-### Manual Build
-
-```bash
-vibecode build --start
-# ... do work ...
-vibecode build --complete
-```
-
-### Auto Build
-
-```bash
-vibecode build --auto
-```
-
-### Iterative Build
-
-```bash
-vibecode build --iterate --max 5
-```
-
-## See Also
-
-- [plan](./plan) - Create plan first
-- [review](./review) - Review after build

package/docs-site/docs/commands/config.md

@@ -1,30 +0,0 @@
----
-sidebar_position: 10
----
-
-# vibecode config
-
-Manage Vibecode configuration.
-
-## Synopsis
-
-```bash
-vibecode config [options]
-```
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--show` | Show current configuration |
-| `--provider <name>` | Set default AI provider |
-
-## Examples
-
-```bash
-# Show config
-vibecode config --show
-
-# Set provider
-vibecode config --provider claude-code
-```

package/docs-site/docs/commands/debug.md

@@ -1,173 +0,0 @@
----
-sidebar_position: 13
----
-
-# vibecode debug
-
-**Debug Mode** - Intelligent 9-step bug fixing.
-
-## Synopsis
-
-```bash
-vibecode debug [description...] [options]
-```
-
-## Description
-
-The `debug` command uses a systematic 9-step protocol to identify, fix, and prevent bugs. It combines error analysis, AI-powered fixing, and automated verification.
-
-## Arguments
-
-| Argument | Description |
-|----------|-------------|
-| `description` | Description of the error (optional) |
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `-i, --interactive` | Interactive debug session |
-| `-a, --auto` | Auto-scan and fix errors |
-| `-l, --log <text>` | Provide error log directly |
-| `--image <path>` | Provide error screenshot |
-| `--attempts <n>` | Max fix attempts (default: 3) |
-| `-v, --verbose` | Show detailed output |
-| `-q, --quiet` | Minimal output |
-
-## Examples
-
-### Interactive Mode
-
-```bash
-vibecode debug
-```
-
-### With Error Description
-
-```bash
-vibecode debug "TypeError: Cannot read properties of undefined"
-```
-
-### Auto-Scan Mode
-
-```bash
-vibecode debug --auto
-```
-
-### From Error Log
-
-```bash
-vibecode debug --log "Error: ENOENT: no such file or directory"
-```
-
-### With Screenshot
-
-```bash
-vibecode debug --image ./error-screenshot.png
-```
-
-## The 9-Step Protocol
-
-### 1. EVIDENCE
-Gather error information from logs, description, or screenshots.
-
-### 2. REPRODUCE
-Confirm the error exists by running relevant commands.
-
-### 3. ANALYZE
-Identify root cause using pattern matching and AI analysis.
-
-### 4. HYPOTHESIZE
-Generate fix hypotheses ranked by confidence.
-
-### 5. TEST
-Prepare fix prompt and validate approach.
-
-### 6. FIX
-Apply fix via Claude Code.
-
-### 7. VERIFY
-Confirm the fix works by re-running tests.
-
-### 8. DOCUMENT
-Log the fix for future reference.
-
-### 9. PREVENT
-Add prevention rules to CLAUDE.md.
-
-## Error Translation
-
-Vibecode translates technical errors to human-friendly Vietnamese:
-
-```
-❌ TypeError: Cannot read properties of undefined (reading 'map')
-
-Translates to:
-
-╭────────────────────────────────────────────────────────────╮
-│  ❌ LỖI: Biến chưa được định nghĩa                         │
-│                                                            │
-│  Vấn đề: Code đang cố truy cập thuộc tính 'map'           │
-│           của một biến undefined                           │
-│                                                            │
-│  💡 Gợi ý:                                                 │
-│  • Kiểm tra biến có được khởi tạo trước khi sử dụng       │
-│  • Thêm optional chaining (?.) khi truy cập thuộc tính    │
-│  • Kiểm tra null/undefined với if statement               │
-│                                                            │
-╰────────────────────────────────────────────────────────────╯
-```
-
-## Output
-
-```
-🔍 VIBECODE DEBUG - Intelligent Bug Fixing
-
-[1/9 EVIDENCE] Gathering error information...
-  Type: TypeError
-  Category: RUNTIME
-  Error: Biến chưa được định nghĩa
-  → Code đang cố truy cập thuộc tính 'map' của một biến undefined
-
-[2/9 REPRODUCE] Confirming error exists...
-  ✓ Error confirmed
-
-[3/9 ANALYZE] Analyzing root cause...
-  Root cause: Missing null check
-  Confidence: 85%
-
-[4/9 HYPOTHESIZE] Generating fix hypotheses...
-  Generated 2 hypothesis(es):
-  - Add optional chaining... (90%)
-  - Add null check... (85%)
-
-[5/9 TEST] Preparing fix...
-[6/9 FIX] Applying fix via Claude Code...
-[7/9 VERIFY] Verifying fix...
-  ✓ Fix verified successfully!
-
-[8/9 DOCUMENT] Documenting fix...
-[9/9 PREVENT] Adding prevention rules...
-
-✅ Bug fixed and documented!
-```
-
-## Learning Integration
-
-After each fix, Vibecode asks for feedback:
-
-```
-? Fix này có đúng không?
-  ✅ Đúng, hoạt động tốt
-  ❌ Không đúng
-  🔄 Đúng một phần
-  ⏭️  Bỏ qua
-```
-
-Your feedback helps improve future suggestions.
-
-## See Also
-
-- [Debug Mode Guide](../guides/debug-mode) - In-depth guide
-- [learn](./learn) - View learning statistics
-- [assist](./assist) - Direct AI assistance

package/docs-site/docs/commands/doctor.md

@@ -1,34 +0,0 @@
----
-sidebar_position: 5
----
-
-# vibecode doctor
-
-Check configuration and diagnose issues.
-
-## Synopsis
-
-```bash
-vibecode doctor
-```
-
-## Description
-
-Runs diagnostic checks:
-- Node.js version
-- Claude Code availability
-- Workspace integrity
-- Configuration validity
-
-## Example Output
-
-```
-🔍 Vibecode Doctor
-
-✓ Node.js 20.10.0
-✓ Claude Code installed
-✓ Workspace valid
-✓ Configuration OK
-
-All checks passed!
-```