codymaster 4.1.0

package/skills/cm-dockit/scripts/dockit-task.sh

@@ -0,0 +1,166 @@
+#!/bin/bash
+# ============================================================
+# DocKit Master v2 — Task Worker
+# Executes a single documentation generation task
+# ============================================================
+set -euo pipefail
+
+# ── Colors ──────────────────────────────────────────────────
+RED='\033[0;31m'; GREEN='\033[0;32m'; CYAN='\033[0;36m'
+YELLOW='\033[1;33m'; BOLD='\033[1m'; DIM='\033[2m'; NC='\033[0m'
+
+log() { echo -e "${DIM}$(date +%H:%M:%S)${NC} [task:${TASK_ID:-?}] $1"; }
+
+# ── Parse Args ──────────────────────────────────────────────
+TASK_ID=""
+PROJECT_PATH=""
+OUTPUT_PATH=""
+ENGINE="gemini"
+SKILL_DIR=""
+LANGUAGE="vi"
+
+while [[ $# -gt 0 ]]; do
+  case $1 in
+    --task-id)   TASK_ID="$2"; shift 2 ;;
+    --project)   PROJECT_PATH="$2"; shift 2 ;;
+    --output)    OUTPUT_PATH="$2"; shift 2 ;;
+    --engine)    ENGINE="$2"; shift 2 ;;
+    --skill-dir) SKILL_DIR="$2"; shift 2 ;;
+    --language)  LANGUAGE="$2"; shift 2 ;;
+    *) shift ;;
+  esac
+done
+
+if [[ -z "$TASK_ID" || -z "$PROJECT_PATH" || -z "$OUTPUT_PATH" ]]; then
+  echo "Usage: dockit-task.sh --task-id ID --project PATH --output PATH --engine ENGINE --skill-dir DIR"
+  exit 1
+fi
+
+PROMPTS_DIR="${SKILL_DIR}/prompts"
+PROJECT_NAME="$(basename "$PROJECT_PATH")"
+
+# ── Prompt Builder ──────────────────────────────────────────
+build_prompt() {
+  local prompt_file="$PROMPTS_DIR/${TASK_ID}.md"
+  
+  if [[ -f "$prompt_file" ]]; then
+    # Load from prompts directory and substitute variables
+    sed -e "s|{{PROJECT_PATH}}|$PROJECT_PATH|g" \
+        -e "s|{{PROJECT_NAME}}|$PROJECT_NAME|g" \
+        -e "s|{{OUTPUT_PATH}}|$OUTPUT_PATH|g" \
+        -e "s|{{LANGUAGE}}|$LANGUAGE|g" \
+        "$prompt_file"
+  else
+    # Fallback: generate a generic prompt
+    cat << PROMPT
+You are DocKit Master, a documentation generator.
+
+Task: Generate the "$TASK_ID" documentation for the project at: $PROJECT_PATH
+
+Language: $LANGUAGE
+Output file: $OUTPUT_PATH
+
+Instructions:
+1. Scan the project codebase thoroughly
+2. Generate comprehensive documentation
+3. Write the output as a Markdown file
+4. Include YAML frontmatter with title, description, keywords
+5. Use Mermaid diagrams where helpful
+6. Include tables for structured data
+
+Write the complete file content for: $OUTPUT_PATH
+PROMPT
+  fi
+}
+
+# ── Execute via Gemini CLI ──────────────────────────────────
+run_gemini() {
+  local prompt
+  prompt="$(build_prompt)"
+  
+  log "Running via Gemini CLI..."
+  
+  # Create temp prompt file
+  local tmp_prompt="/tmp/dockit-prompt-${TASK_ID}-$$.md"
+  echo "$prompt" > "$tmp_prompt"
+  
+  # Run Gemini CLI
+  # The exact command depends on Gemini CLI version
+  local result_file="/tmp/dockit-result-${TASK_ID}-$$.md"
+  
+  if command -v gemini &>/dev/null; then
+    # Try Gemini CLI with file output
+    gemini -p "$(cat "$tmp_prompt")" > "$result_file" 2>/dev/null
+    
+    if [[ -f "$result_file" ]] && [[ -s "$result_file" ]]; then
+      mkdir -p "$(dirname "$OUTPUT_PATH")"
+      cp "$result_file" "$OUTPUT_PATH"
+      log "✅ Output written to: $OUTPUT_PATH"
+      rm -f "$tmp_prompt" "$result_file"
+      return 0
+    fi
+  fi
+  
+  # Fallback: save prompt for manual execution
+  log "⚠️ Gemini CLI execution failed. Saving prompt for manual use."
+  mkdir -p "$(dirname "$OUTPUT_PATH")"
+  echo "<!-- DOCKIT: Task $TASK_ID - Prompt saved, needs manual execution -->" > "$OUTPUT_PATH"
+  echo "<!-- Run: gemini -p \"\$(cat $tmp_prompt)\" > $OUTPUT_PATH -->" >> "$OUTPUT_PATH"
+  cat "$tmp_prompt" >> "$OUTPUT_PATH"
+  rm -f "$result_file"
+  return 1
+}
+
+# ── Execute via Prompt Copy ─────────────────────────────────
+run_prompt_copy() {
+  local prompt
+  prompt="$(build_prompt)"
+  
+  log "Saving prompt for manual execution..."
+  mkdir -p "$(dirname "$OUTPUT_PATH")"
+  
+  # Save the prompt
+  local prompt_save="$PROJECT_PATH/docs/_prompts/${TASK_ID}.md"
+  mkdir -p "$(dirname "$prompt_save")"
+  echo "$prompt" > "$prompt_save"
+  
+  # Create placeholder output
+  cat > "$OUTPUT_PATH" << PLACEHOLDER
+---
+title: "$TASK_ID (pending)"
+description: "This document needs to be generated manually"
+---
+
+# $TASK_ID
+
+> ⚠️ This document was not auto-generated. Run the prompt manually:
+> \`$prompt_save\`
+
+Paste the prompt into Gemini CLI or Antigravity to generate this document.
+PLACEHOLDER
+
+  log "Prompt saved: $prompt_save"
+  return 0  # Don't fail, just mark as needing manual work
+}
+
+# ═══════════════════════════════════════════════════════════
+# MAIN
+# ═══════════════════════════════════════════════════════════
+
+log "Starting task: $TASK_ID"
+log "Project: $PROJECT_PATH"
+log "Output: $OUTPUT_PATH"
+log "Engine: $ENGINE"
+
+case "$ENGINE" in
+  gemini)
+    run_gemini
+    ;;
+  prompt|*)
+    run_prompt_copy
+    ;;
+esac
+
+exit_code=$?
+log "Task $TASK_ID finished with exit code $exit_code"
+exit $exit_code

package/skills/cm-dockit/skills/analyze-codebase.md

@@ -0,0 +1,174 @@
+# Analyze Codebase — UX Master Edition
+
+Deeply analyze the codebase to create metadata for other documentation generation skills. Produces a comprehensive analysis with architecture diagrams, dependency graphs, and framework detection.
+
+## Procedure
+
+### 1. Scan Project Root
+
+```
+- Read README.md, package.json, Makefile, docker-compose.yml, etc.
+- List all top-level directories
+- Count files by extension to detect languages
+- Identify monorepo structure if applicable
+```
+
+### 2. Detect Tech Stack
+
+| Signal | Detected As |
+|--------|------------|
+| `package.json` + `next.config.*` | Next.js |
+| `package.json` + `vite.config.*` | Vite + React/Vue |
+| `package.json` + `nuxt.config.*` | Nuxt.js |
+| `package.json` + `svelte.config.*` | SvelteKit |
+| `package.json` + `astro.config.*` | Astro |
+| `requirements.txt` / `pyproject.toml` | Python |
+| `go.mod` | Go |
+| `Cargo.toml` | Rust |
+| `pom.xml` / `build.gradle` | Java |
+| `*.csproj` | .NET/C# |
+| `docker-compose.yml` | Containerized |
+| `Dockerfile` | Docker |
+| `deno.json` / `deno.jsonc` | Deno |
+| `bun.lockb` / `bunfig.toml` | Bun |
+| `tauri.conf.json` | Tauri |
+| `electron-builder.yml` | Electron |
+| `Makefile` | Build automation |
+| `setup.py` / `setup.cfg` | Python package |
+
+### 3. Map Architecture
+
+Identify and document:
+
+1. **Presentation Layer** — Routes, pages, components, views
+2. **Business Logic** — Services, controllers, handlers, middleware
+3. **Data Layer** — Models, migrations, repositories, ORM config
+4. **Infrastructure** — Config, Docker, CI/CD, deployment scripts
+5. **External Integrations** — API clients, webhooks, SDKs
+6. **Testing** — Test framework, test directories, coverage config
+
+### 4. Identify Key Entry Points
+
+- Web server startup file (e.g., `index.ts`, `main.py`, `main.go`, `app.py`)
+- Route registration files
+- Database migration files
+- Environment/config files
+- CLI entry points (`bin/`, `scripts/`)
+
+### 5. Extract Route Map
+
+Scan route/controller files and build a table:
+
+| Method | Path | Handler | Auth | Middleware | Description |
+|--------|------|---------|------|------------|-------------|
+| GET | /api/users | getUsers | Yes | rateLimit | List users |
+| POST | /api/users | createUser | Yes | validate | Create user |
+
+### 6. Extract Database Schema
+
+From migration files or ORM models, build:
+
+- Table list with columns, types, and constraints
+- Relationships (FK, many-to-many, polymorphic)
+- Indexes and unique constraints
+- Enum types
+
+### 7. Analyze Dependencies
+
+Build a dependency overview:
+
+| Category | Package | Version | Purpose |
+|----------|---------|---------|---------|
+| Core | express | 4.18 | HTTP server |
+| Database | prisma | 5.0 | ORM |
+| Auth | jsonwebtoken | 9.0 | JWT handling |
+| Testing | jest | 29.0 | Unit tests |
+
+### 8. Detect Test Coverage
+
+- Identify test framework (Jest, Pytest, Go test, etc.)
+- Count test files vs source files
+- Note CI/CD test integration
+
+### 9. Output
+
+Generate `docs/analysis.md` (note: NO underscore prefix — breaks auto-sidebar detection) with all findings:
+
+```markdown
+---
+title: "Codebase Analysis"
+description: "Automated analysis of the project codebase"
+---
+
+# Codebase Analysis
+
+> **Quick Reference**
+> - **Project**: [name from package.json/README]
+> - **Type**: [Web App / API / Library / CLI / SDK]
+> - **Languages**: [TypeScript, Python, etc.]
+> - **Frameworks**: [Next.js, FastAPI, etc.]
+> - **Lines of Code**: ~[estimate]
+
+## Architecture
+
+```mermaid
+graph TB
+
+    subgraph Presentation
+        UI["🖥️ Frontend"]
+    end
+
+    subgraph Business
+        API["⚙️ API Server"]
+    end
+
+    subgraph Data
+        DB["🗄️ Database"]
+    end
+
+    UI --> API --> DB
+```
+
+## Directory Structure
+
+```
+[Annotated tree — show only important directories]
+```
+
+## Dependencies
+
+| Category | Package | Version | Purpose |
+|----------|---------|---------|---------|
+
+## Route Map
+
+| Method | Path | Handler | Auth | Description |
+|--------|------|---------|------|-------------|
+
+## Database Schema
+
+| Table | Columns | Relationships |
+|-------|---------|---------------|
+
+## Key Files
+
+| File | Role | Lines |
+|------|------|-------|
+| src/index.ts | Entry point | 150 |
+| src/routes/ | API routes | — |
+
+## Test Coverage
+
+| Framework | Test Files | Coverage |
+|-----------|-----------|----------|
+```
+
+## Rules
+
+- **TRACE actual code** — never guess from filenames
+- **Cite every finding**: `(file_path:line_number)`
+- **Output file**: `analysis.md` (**NOT** `_analysis.md` — underscore breaks auto-sidebar)
+- Use Mermaid diagrams — do NOT hardcode colors (let native theming handle light/dark)
+- If a section cannot be determined, state **"Undetermined — requires further inspection"**
+- **Quick Reference card** at top of output
+- **Include dependency analysis** — essential for understanding the project

package/skills/cm-dockit/skills/api-reference.md

@@ -0,0 +1,237 @@
+# API Reference Generator — UX Master Edition
+
+Automatically generate API reference documentation with multi-language SDK examples and visual request flows.
+
+## Input Required
+
+- `docs/_analysis.md` (output from analyze-codebase)
+- Access to route files, controllers, middleware, type definitions
+
+## Content Guidelines
+
+**Before generating, read `skills/content-guidelines.md` for:**
+- Writing style rules
+- Mermaid theme-neutral rules
+
+## Procedure
+
+### 1. Scan Route Files
+
+Detect routing patterns by framework:
+
+| Framework | Route Pattern |
+|-----------|--------------|
+| Express.js | `router.get('/path', handler)` |
+| Next.js API | `app/api/*/route.ts` |
+| FastAPI | `@app.get('/path')` |
+| Hono | `app.get('/path', handler)` |
+| Go (chi/gin) | `r.Get("/path", handler)` |
+| NestJS | `@Get('/path')` decorator |
+| Bun / Elysia | `app.get('/path', handler)` |
+| Deno / Fresh | `GET /api/path` handler exports |
+
+### 2. Extract Endpoint Details
+
+For each endpoint, extract:
+- HTTP method + path (with params)
+- Middleware / guards (auth, rate limit)
+- Request body schema (from types/validators)
+- Response schema (from return types)
+- Status codes (from error handlers)
+
+### 3. Group by Resource
+
+Organize endpoints by resource:
+```
+/api/users      → Users
+/api/orders     → Orders
+/api/products   → Products
+```
+
+### 4. Generate Files
+
+Output to `docs/api/[resource].md`
+
+## API Reference Template
+
+```markdown
+---
+title: "[Resource Name] API"
+description: "API reference for [resource]"
+---
+
+# [Resource Name] API
+
+> **Quick Reference**
+> - **Base URL**: `[base_url]/api/[resource]`
+> - **Auth**: Bearer Token / API Key / None
+> - **Rate Limit**: [X requests/min]
+> - **Content-Type**: `application/json`
+
+## Endpoints Overview
+
+| Method | Endpoint | Description | Auth |
+|--------|----------|-------------|------|
+| GET | `/api/resource` | List items | ✅ |
+| GET | `/api/resource/:id` | Get details | ✅ |
+| POST | `/api/resource` | Create item | ✅ |
+| PUT | `/api/resource/:id` | Update item | ✅ |
+| DELETE | `/api/resource/:id` | Delete item | ✅ |
+
+---
+
+## GET /api/resource
+
+List all [resource].
+
+### Parameters
+
+| Name | Location | Type | Required | Default | Description |
+|------|----------|------|----------|---------|-------------|
+| page | query | number | ❌ | 1 | Page number |
+| limit | query | number | ❌ | 20 | Items per page |
+| sort | query | string | ❌ | `created_at` | Sort field |
+
+### Response
+
+**200 OK**
+```json
+{
+  "data": [...],
+  "total": 100,
+  "page": 1,
+  "limit": 20
+}
+```
+
+**401 Unauthorized**
+```json
+{
+  "error": "Authentication required",
+  "code": "AUTH_REQUIRED"
+}
+```
+
+### Examples
+
+<details>
+<summary>cURL</summary>
+
+```bash
+curl -X GET "https://api.example.com/api/resource?page=1&limit=10" \
+  -H "Authorization: Bearer <token>"
+```
+
+</details>
+
+<details>
+<summary>Python</summary>
+
+```python
+import requests
+
+response = requests.get(
+    "https://api.example.com/api/resource",
+    params={"page": 1, "limit": 10},
+    headers={"Authorization": f"Bearer {token}"}
+)
+data = response.json()
+```
+
+</details>
+
+<details>
+<summary>JavaScript (fetch)</summary>
+
+```javascript
+const response = await fetch('/api/resource?page=1&limit=10', {
+  headers: { 'Authorization': `Bearer ${token}` }
+});
+const data = await response.json();
+```
+
+</details>
+
+<details>
+<summary>Go</summary>
+
+```go
+req, _ := http.NewRequest("GET", "https://api.example.com/api/resource?page=1", nil)
+req.Header.Set("Authorization", "Bearer "+token)
+resp, _ := http.DefaultClient.Do(req)
+```
+
+</details>
+```
+
+## Index File
+
+Generate `docs/api/index.md`:
+
+```markdown
+---
+title: "API Reference"
+description: "API reference documentation"
+---
+
+# API Reference
+
+> **Quick Reference**
+> - **Base URL**: `[detected base URL]`
+> - **Auth Method**: [Bearer token / API key / OAuth2]
+> - **Response Format**: JSON
+> - **API Version**: [v1 / v2]
+
+## Authentication
+
+```bash
+# Include this header in all authenticated requests
+Authorization: Bearer <your_access_token>
+```
+
+:::warning
+API keys should never be exposed in client-side code. Use server-side proxying or environment variables.
+:::
+
+## Endpoints
+
+| Resource | Endpoints | Base Path | Auth |
+|----------|-----------|-----------|------|
+| Users | 5 | /api/users | ✅ |
+| Orders | 4 | /api/orders | ✅ |
+
+## Error Codes
+
+| Code | Name | Description |
+|------|------|-------------|
+| 400 | Bad Request | Invalid or missing request data |
+| 401 | Unauthorized | Authentication required |
+| 403 | Forbidden | Insufficient permissions |
+| 404 | Not Found | Resource does not exist |
+| 422 | Unprocessable | Validation failed |
+| 429 | Too Many Requests | Rate limit exceeded |
+| 500 | Server Error | Internal server error |
+
+## Rate Limiting
+
+| Tier | Limit | Window |
+|------|-------|--------|
+| Free | 60 req | per minute |
+| Pro | 600 req | per minute |
+
+:::tip
+Rate limit headers are included in every response:
+`X-RateLimit-Remaining`, `X-RateLimit-Reset`
+:::
+```
+
+## Rules
+
+- **Quick Reference card** at top of every API page
+- **Extract schemas from actual type definitions** — never guess
+- **Include real validation rules** from validators (Zod, Joi, class-validator)
+- **Show both success and error responses** for every endpoint
+- **Multi-language SDK examples** using `<details>` (cURL, Python, JS, Go)
+- **Use `:::warning` admonition** for security-related notes
+- **Use `:::tip` admonition** for usage tips
+- **Cite source**: `(file_path:line_number)` for each endpoint