@ginkoai/cli 2.1.6-beta.0 → 2.1.6

package/dist/templates/skills/ginko/commands-reference.md

@@ -1,221 +0,0 @@
-# Ginko CLI Commands Reference
-
-Complete reference for all ginko CLI commands.
-
-## Session Commands
-
-### `ginko start [sessionId]`
-Start or resume a session with event-based context loading.
-- Loads context from `.ginko/sessions/[user]/`
-- Shows active sprint and next task
-- Warns about uncommitted files
-
-### `ginko status`
-Show current session status.
-
-### `ginko handoff [message]`
-Pause current session and create handoff document.
-- Archives previous session
-- Creates continuity document for next session
-
-### `ginko log [description]`
-Log an event to the current session (defensive logging).
-
-### `ginko compact`
-Reduce context size by removing stale information.
-
-## Task Management
-
-### `ginko task complete <taskId>`
-Mark task as complete. Updates knowledge graph (syncs to dashboard).
-- Options: `--cascade` (auto-complete parent if all siblings done)
-
-### `ginko task start <taskId>`
-Mark task as in progress.
-
-### `ginko task pause <taskId>`
-Return task to not_started state.
-
-### `ginko task block <taskId> [reason]`
-Block task with reason. Prompts for reason if not provided.
-
-### `ginko task show <taskId>`
-Show current task status.
-
-## Sprint Management
-
-### `ginko sprint start <sprintId>`
-Start sprint (planned → active).
-
-### `ginko sprint complete <sprintId>`
-Complete sprint (active → complete).
-
-### `ginko sprint pause <sprintId>`
-Pause sprint (active → paused).
-
-### `ginko sprint status show <sprintId>`
-Show current sprint status.
-
-### `ginko sprint deps`
-Visualize task dependencies as a tree.
-
-## Knowledge Graph
-
-### `ginko graph init`
-Initialize knowledge graph for your project.
-
-### `ginko graph load [options]`
-Upload documents to knowledge graph.
-- `--docs-only`: Load ADRs and PRDs only
-- `--extended-only`: Load patterns, gotchas, sessions only
-- `--force`: Reload all documents even if unchanged
-
-### `ginko graph status`
-Show graph statistics and health.
-
-### `ginko graph health`
-Show graph reliability metrics (success rate, latency, retries).
-
-### `ginko graph query <text>`
-Search documents using semantic similarity.
-- Options: `--limit N`, `--type <TYPE>`
-
-### `ginko graph explore <documentId>`
-Explore document and its connections.
-
-### `ginko graph migrate <migration>`
-Run graph migrations.
-
-## Team & Assignment
-
-### `ginko assign <taskIdOrEmail> [email]`
-Assign tasks to team members.
-- Updates both graph and sprint markdown
-- Options: `--sprint <id> --all` (assign all tasks in sprint)
-
-### `ginko sync [options]`
-Pull dashboard knowledge edits to local git.
-- `--preview`: Preview without syncing
-- `--dry-run`: Preview what files would sync
-- `--force`: Overwrite local files
-- `--type <type>`: Sync only specific type (ADR, PRD, Pattern, etc.)
-- `--no-commit`: Sync without committing
-
-### `ginko team-activity [user]`
-View team activity from user-namespaced session logs.
-
-### `ginko invite [email]`
-Invite collaborators to join your team.
-
-### `ginko join [code]`
-Join a team using an invitation code.
-
-## Planning & Architecture
-
-### `ginko charter`
-Create and manage project charter (AI-assisted).
-
-### `ginko epic`
-Create and manage epics with status tracking.
-
-### `ginko sprint [intent]`
-Sprint management and planning commands.
-
-### `ginko plan [feature]`
-Create phased implementation plan with acceptance criteria.
-
-### `ginko architecture [decision]`
-Design mode for crafting ADRs with AI enhancement.
-
-### `ginko roadmap`
-View product roadmap (Now/Next/Later priority lanes).
-
-### `ginko backlog`
-Manage git-native backlog items.
-
-### `ginko feature <description>`
-Quick create a feature (shortcut for backlog create feature).
-
-### `ginko story <description>`
-Quick create a story (shortcut for backlog create story).
-
-## Development Tools
-
-### `ginko ship [message]`
-AI-enhanced shipping with smart commit messages and PR descriptions.
-
-### `ginko verify <taskId>`
-Verify task completion by running acceptance criteria checks.
-
-### `ginko vibecheck [concern]`
-Pause moment for recalibration - conversational check-in.
-
-### `ginko capture [description]`
-Capture a learning, discovery, or important context.
-
-### `ginko explore [topic]`
-Collaborative thinking mode for exploring problems and solutions.
-
-### `ginko reflect <intent>`
-Universal reflection pattern for AI-enhanced content generation.
-
-## Multi-Agent
-
-### `ginko orchestrate`
-Run as supervisor agent to coordinate multi-agent task execution.
-
-### `ginko agent`
-Manage AI agents for multi-agent collaboration.
-
-### `ginko checkpoint`
-Manage checkpoints for task rollback and recovery.
-
-### `ginko dlq`
-Manage Dead Letter Queue (failed events).
-
-### `ginko escalation`
-Manage human escalations for multi-agent collaboration.
-
-### `ginko notifications`
-Manage notification hooks for human observability.
-
-## Authentication
-
-### `ginko login`
-Authenticate CLI with GitHub via Supabase OAuth.
-
-### `ginko logout`
-Clear local authentication session.
-
-### `ginko whoami`
-Display current authentication status and user information.
-
-## Configuration
-
-### `ginko init`
-Initialize Ginko in your project (sets up local structure + cloud graph).
-
-### `ginko config [key] [value]`
-Manage Ginko configuration.
-
-### `ginko context`
-Manage session context.
-
-## IDE Integration
-
-### `ginko init-cursor`
-Generate Cursor setup preview or apply it to the repository.
-
-### `ginko uninstall-cursor`
-Remove Cursor integration.
-
-### `ginko init-copilot`
-Generate GitHub Copilot setup preview or apply to repository.
-
-### `ginko uninstall-copilot`
-Remove GitHub Copilot integration.
-
-## Migration
-
-### `ginko migrate`
-Migration utilities for syncing markdown to graph.

package/dist/templates/skills/pull.md

@@ -1,56 +0,0 @@
-# Pull Skill (ADR-077)
-
-## Purpose
-Pull dashboard edits from the Ginko Cloud knowledge graph to local git repository.
-
-## When to Use
-- At the start of a session when team context may be stale
-- When `ginko start` shows staleness warnings
-- When user requests updates from dashboard
-- After team members have made edits in the dashboard
-
-## Command Reference
-
-```bash
-# Pull all changes from graph
-ginko pull
-
-# Pull specific entity types
-ginko pull sprint              # Pull sprint changes (status updates)
-ginko pull adr                 # Pull ADR edits
-ginko pull epic                # Pull epic changes
-
-# Options
-ginko pull --dry-run           # Preview without pulling
-ginko pull --force             # Overwrite local with graph versions
-```
-
-## Options
-
-| Flag | Description | Default |
-|------|-------------|---------|
-| `--dry-run` | Preview what would be pulled | false |
-| `--force` | Overwrite local files with graph versions | false |
-
-## Error Handling
-
-| Error | Action |
-|-------|--------|
-| `Not authenticated` | Prompt: Run `ginko login` |
-| `Graph not initialized` | Prompt: Run `ginko graph init` |
-| Conflict detected | Interactive resolution (use-graph, use-local, skip) |
-| 5xx server error | Retry with exponential backoff |
-
-## Behavioral Rules
-
-1. **Pull at session start** - When `ginko start` shows staleness, auto-pull
-2. **Content conflicts: local wins** - Per ADR-060, content in git is authoritative
-3. **State conflicts: graph wins** - Status, assignments are graph-authoritative
-4. **Never use deprecated alternatives** - Do not use `ginko sync` (deprecated)
-5. **After pull, suggest push** - If local has unpushed changes, suggest `ginko push`
-
-## Anti-Patterns (DO NOT)
-
-- Do NOT use `ginko sync` (deprecated, use `ginko pull`)
-- Do NOT use curl/fetch to hit graph API directly
-- Do NOT skip pull when team context is stale

package/dist/templates/skills/push.md

@@ -1,73 +0,0 @@
-# Push Skill (ADR-077)
-
-## Purpose
-Push local content changes to the Ginko Cloud knowledge graph using git-integrated change detection.
-
-## When to Use
-- After creating or modifying content files (epics, sprints, ADRs, charters, patterns, gotchas)
-- After `ginko handoff` to ensure all work is synced
-- After `ginko task complete` / `ginko sprint complete` to persist state
-- When the orchestrator detects unpushed content changes
-- When user requests sync to graph
-
-## Command Reference
-
-```bash
-# Push all changes since last push
-ginko push
-
-# Push specific entity types
-ginko push epic                   # All changed epics
-ginko push epic EPIC-001          # Specific epic
-ginko push sprint e001_s01        # Specific sprint
-ginko push charter                # Project charter
-ginko push adr                    # All changed ADRs
-
-# Options
-ginko push --dry-run              # Preview without pushing
-ginko push --force                # Overwrite graph content
-ginko push --all                  # Push all (not just changes)
-ginko push --no-events            # Skip event files
-```
-
-## Options
-
-| Flag | Description | Default |
-|------|-------------|---------|
-| `--dry-run` | Preview what would be pushed | false |
-| `--force` | Overwrite graph even if conflicts | false |
-| `--all` | Push all content files, ignoring change detection | false |
-| `--no-events` | Skip pushing event JSONL files | false |
-
-## Error Handling
-
-| Error | Action |
-|-------|--------|
-| `Not authenticated` | Prompt: Run `ginko login` |
-| `Graph not initialized` | Prompt: Run `ginko graph init` |
-| 5xx server error | Retry with exponential backoff (handled by API client) |
-| 4xx client error | Report to user, do not retry |
-| Network error | Retry up to 3 times |
-
-## Behavioral Rules
-
-1. **Always push after entity creation** - When an epic, sprint, charter, or ADR is created, push immediately
-2. **Push is non-blocking for auto-push** - When dispatched as a subagent, run in background
-3. **Prefer targeted push** - Use `ginko push epic` instead of `ginko push` when you know the entity type
-4. **Never use deprecated alternatives** - Do not use `ginko graph load` or `--sync` flags
-5. **Report results concisely** - Show file count, task count, and event count
-
-## Anti-Patterns (DO NOT)
-
-- Do NOT use `ginko graph load` (deprecated, use `ginko push --all`)
-- Do NOT use `ginko epic --sync` (deprecated, use `ginko push epic`)
-- Do NOT use `ginko charter --sync` (deprecated, use `ginko push charter`)
-- Do NOT use curl/fetch to hit graph API directly
-- Do NOT skip push after creating content
-
-## Exit Codes
-
-| Code | Meaning |
-|------|---------|
-| 0 | Push completed successfully |
-| 1 | Push failed (auth, config, or API error) |

package/dist/templates/skills/skills/ginko/SKILL.md

@@ -1,209 +0,0 @@
----
-name: ginko
-description: Ginko CLI mastery - session management, task status, graph queries, sprint workflows. Use when working with ginko commands, managing tasks, querying the knowledge graph, or coordinating development sessions.
----
-
-# Ginko CLI Skill
-
-Execute ginko commands effectively for session management, task tracking, and knowledge graph operations.
-
-## Quick Reference
-
-| Need | Command |
-|------|---------|
-| Start session | `ginko start` |
-| End session | `ginko handoff [message]` |
-| Check progress | `ginko sprint status show <sprintId>` |
-| Mark task done | `ginko task complete <taskId>` |
-| Mark sprint done | `ginko sprint complete <sprintId>` |
-| Search knowledge | `ginko graph query "topic"` |
-| View relationships | `ginko graph explore <nodeId>` |
-| Push to graph | `ginko push` |
-| Pull from dashboard | `ginko pull` |
-| Assign work | `ginko assign <taskId> <email>` |
-
-## Session Lifecycle
-
-### Starting Work
-```bash
-GINKO_FORCE_TTY=1 ginko start
-```
-- Shows flow state, work mode, active sprint
-- Displays "Next up" task based on assignment and status
-- Warns about uncommitted files or stale team context
-
-**On staleness warning**: Auto-run `ginko pull` to pull team updates.
-
-### Ending Work
-```bash
-ginko handoff "summary of what was done"
-```
-- Archives session context
-- Creates handoff document for continuity
-
-## Task & Sprint Status Management
-
-### Task Status Flow
-```
-not_started → in_progress → complete
-                ↓
-              blocked (with reason)
-```
-
-### Critical: Marking Work Complete
-
-**Tasks**: Update the knowledge graph (syncs to dashboard)
-```bash
-ginko task complete e016_s01_t01
-ginko task start e016_s01_t02
-ginko task block e016_s01_t03 "waiting for API review"
-```
-
-**Sprints**: Use sprint command, not task command
-```bash
-ginko sprint complete e016_s01
-ginko sprint start e016_s02
-ginko sprint pause e016_s01
-```
-
-**Verify status**:
-```bash
-ginko task show <taskId>      # Shows: ✓ complete, ○ not_started, etc.
-ginko sprint status show <sprintId>
-```
-
-### Common Pitfall
-If dashboard shows tasks as "todo" but `ginko graph explore` shows checkmarks:
-- The graph node has markdown checkmarks but status property wasn't updated
-- Fix: Run `ginko task complete <taskId>` for each task
-- This updates the graph property that syncs to dashboard
-
-### Cascade Completion
-When finishing the last task in a sprint:
-```bash
-ginko task complete e016_s01_t07 --cascade
-```
-Auto-completes parent sprint if all tasks done.
-
-## Knowledge Graph Queries
-
-### Semantic Search
-```bash
-ginko graph query "authentication patterns"
-ginko graph query "error handling" --limit 10
-ginko graph query "topic" --type ADR
-```
-
-### Explore Relationships
-```bash
-ginko graph explore e016_s01        # Sprint and its tasks
-ginko graph explore ADR-039         # ADR and connections
-ginko graph explore e016_s01_t01    # Task details
-```
-
-### Graph Health
-```bash
-ginko graph status    # Node counts, relationships
-ginko graph health    # API reliability metrics
-```
-
-## Assignment & Team
-
-### Assign Tasks
-```bash
-ginko assign e016_s03_t01 user@example.com
-ginko assign --sprint e016_s03 --all user@example.com
-```
-
-### Push/Pull Sync (ADR-077)
-
-**MANDATORY**: Use push/pull for all sync operations. Never use deprecated `ginko sync` or `ginko graph load`.
-
-```bash
-# Push local changes to graph
-ginko push                        # Push all changes since last push
-ginko push epic                   # Push only changed epics
-ginko push sprint e001_s01        # Push specific sprint
-ginko push charter                # Push charter
-ginko push --dry-run              # Preview what would be pushed
-ginko push --all                  # Push all content (like graph load)
-
-# Pull dashboard changes to local
-ginko pull                        # Pull all changes from dashboard
-ginko pull sprint                 # Pull only sprint changes
-ginko pull --force                # Overwrite local with graph
-
-# Compare
-ginko diff epic/EPIC-001          # Show local vs graph diff
-ginko status                      # Show sync state (unpushed/unpulled)
-```
-
-**Auto-push**: Fires automatically after task/sprint status changes and handoff.
-
-**Deprecated commands** (still work but show warnings):
-- `ginko sync` → use `ginko pull`
-- `ginko graph load` → use `ginko push --all`
-- `ginko epic --sync` → use `ginko push epic`
-- `ginko charter --sync` → use `ginko push charter`
-
-## Sprint Planning
-
-### View Roadmap
-```bash
-ginko roadmap    # Now/Next/Later priority lanes
-```
-
-### Sprint Commands
-```bash
-ginko sprint deps              # Visualize task dependencies
-ginko sprint start <id>        # Activate sprint
-ginko sprint complete <id>     # Mark sprint done
-ginko sprint pause <id>        # Temporarily hold
-```
-
-## Entity Naming Convention
-
-| Entity | Format | Example |
-|--------|--------|---------|
-| Epic | `e{NNN}` | `e016` |
-| Sprint | `e{NNN}_s{NN}` | `e016_s03` |
-| Task | `e{NNN}_s{NN}_t{NN}` | `e016_s03_t01` |
-| Ad-hoc | `adhoc_{YYMMDD}_s{NN}` | `adhoc_260123_s01` |
-
-## Environment Variables
-
-| Variable | Purpose |
-|----------|---------|
-| `GINKO_FORCE_TTY=1` | Force rich output (tables, colors) in Claude Code |
-| `FORCE_COLOR=1` | Force chalk colors (auto-set with GINKO_FORCE_TTY) |
-
-## Troubleshooting
-
-| Issue | Solution |
-|-------|----------|
-| Task not found | Check ID format matches `e{NNN}_s{NN}_t{NN}` |
-| Sprint won't complete | Use `ginko sprint complete`, not `ginko task complete` |
-| Dashboard out of sync | Run `ginko push` to push local changes, or `ginko task complete` for status |
-| Stale team context | Run `ginko pull` to pull updates |
-| Graph query fails | Check `ginko graph health` for API issues |
-
-## Common Workflows
-
-### Daily Session
-1. `ginko start` - Load context, see next task
-2. `ginko task start <id>` - Mark task in progress
-3. Do the work
-4. `ginko task complete <id>` - Mark done
-5. `ginko handoff "summary"` - End session
-
-### Sprint Completion
-1. Verify all tasks: `ginko graph explore <sprintId>`
-2. Complete any unmarked tasks: `ginko task complete <taskId>`
-3. Complete sprint: `ginko sprint complete <sprintId>`
-4. Verify: `ginko sprint status show <sprintId>`
-
-### Investigate Status Mismatch
-1. Check graph: `ginko graph explore <id>`
-2. Check status: `ginko task show <id>` or `ginko sprint status show <id>`
-3. If mismatch: update with appropriate command
-4. Verify dashboard reflects changes