@vibescope/mcp-server 0.0.1

package/dist/knowledge.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Knowledge Base
+ *
+ * Embedded help topics for on-demand agent guidance.
+ */
+export declare const KNOWLEDGE_BASE: Record<string, string>;

package/dist/knowledge.js

@@ -0,0 +1,121 @@
+/**
+ * Knowledge Base
+ *
+ * Embedded help topics for on-demand agent guidance.
+ */
+export const KNOWLEDGE_BASE = {
+    getting_started: `# Getting Started
+1. Call start_work_session(git_url) to initialize
+2. Response includes next_task - start working on it immediately
+3. Use update_task to mark in_progress and track progress
+4. Call complete_task when done - it returns your next task
+5. Use get_help(topic) when you need guidance on specific workflows`,
+    tasks: `# Task Workflow
+- Mark task in_progress with update_task before starting
+- Update progress_percentage regularly (every 15-20% progress)
+- Include progress_note to auto-log milestones
+- One task at a time - complete current before starting another
+- complete_task returns next_task and context counts (validation, blockers, deployment)
+- Priority: 1=highest, 5=lowest`,
+    validation: `# Task Validation
+Completed tasks need validation before deployment. PRIORITIZE validation over new tasks.
+1. Check: get_tasks_awaiting_validation(project_id)
+2. Claim: claim_validation(task_id) - marks "being reviewed" on dashboard
+3. Review code changes and run tests
+4. Complete: validate_task(task_id, approved: true/false, validation_notes: "...")
+Self-validation allowed when single-agent or to unblock deployment.`,
+    deployment: `# Deployment Workflow
+1. Ensure all completed tasks are validated first
+2. request_deployment(project_id, environment: "production")
+3. claim_deployment_validation(project_id) - claim for validation
+4. Run: pnpm build && pnpm test
+5. report_validation(project_id, build_passed: true, tests_passed: true)
+6. start_deployment(project_id) - returns project's deployment_instructions
+7. Follow the instructions (e.g., push to main, run deploy command)
+8. complete_deployment(project_id, success: true, summary: "...")`,
+    git: `# Git Workflow
+
+Call get_git_workflow(project_id) for project-specific config.
+
+## Workflow Types
+- **none**: No branching strategy
+- **trunk-based**: Commit directly to main, small frequent commits
+- **github-flow**: Feature branches, merge via PR after validation
+- **git-flow**: develop/release/feature branches
+
+## Lifecycle Integration
+
+### 1. Starting a Task
+When you call update_task(status: "in_progress"), the response includes:
+- **branch_name**: Suggested branch (e.g., feature/a1b2c3d4-task-title)
+- **base_branch**: Branch to branch from
+- **steps**: Git commands to create the branch
+- **reminder**: Call to update task with git_branch
+
+### 2. Completing a Task
+When you call complete_task, the response includes:
+- **steps**: Push commands
+- **pr_suggestion**: { title, body_template } - ready-to-use PR content
+- **next_step**: Reminder that merge happens AFTER validation
+
+Add the PR link via add_task_reference(task_id, url, label: "Pull Request").
+
+### 3. Validation Approved
+When validate_task(approved: true) is called, the response includes:
+- **target_branch**: Where to merge
+- **feature_branch**: Branch being merged
+- **steps**: Merge options (UI or command line)
+- **cleanup**: Branch deletion commands
+- **note**: Confirmation it's safe to merge
+
+## Key Rules
+- Create branch when starting task (github-flow/git-flow)
+- Push and create PR when completing task
+- Wait for validation before merging
+- Clean up branch after successful merge`,
+    blockers: `# Working with Blockers
+When stuck and need human input:
+1. add_blocker(project_id, description: "What's blocking")
+2. Ask your question to the user
+3. resolve_blocker(blocker_id, resolution_note: "How resolved")
+Only use for genuine blockers requiring decisions - not routine questions.`,
+    milestones: `# Task Milestones
+For complex tasks, break into milestones:
+1. add_milestone(task_id, title: "Design schema")
+2. add_milestone(task_id, title: "Implement API")
+3. Update with complete_milestone(milestone_id) as you go
+Dashboard shows progress bar with completed/total.`,
+    fallback: `# Fallback Activities
+When no tasks available, get_next_task suggests activities:
+- feature_ideation, code_review, performance_audit
+- security_review, test_coverage, documentation_review
+1. start_fallback_activity(project_id, activity: "code_review")
+2. Do the work, use add_finding for issues, add_idea for improvements
+3. stop_fallback_activity(project_id, summary: "...")`,
+    session: `# Session Management
+- start_work_session initializes and returns next_task (lite mode default)
+- Use mode:'full' for complete context when needed
+- heartbeat every 30-60 seconds maintains active status
+- end_work_session releases claimed tasks and returns summary
+- NEVER STOP: After completing a task, immediately start the next one
+- When context grows large: /clear then start_work_session to continue fresh
+- Your progress is saved to the dashboard - nothing is lost on /clear`,
+    tokens: `# Token Efficiency
+Be mindful of token costs - every tool call has a cost.
+- Use mode:'lite' (default) - saves ~85% vs full mode
+- Call get_token_usage() to check consumption
+- /compact when context grows large
+- Batch related updates when possible
+- Trust lite mode; only use full mode for initial exploration`,
+    topics: `# Available Help Topics
+- getting_started: Basic workflow overview
+- tasks: Working on tasks, progress tracking
+- validation: Cross-agent task validation
+- deployment: Deployment coordination
+- git: Git workflow configuration
+- blockers: Handling blockers
+- milestones: Breaking down complex tasks
+- fallback: Background activities when idle
+- session: Session management
+- tokens: Token efficiency tips`,
+};

package/dist/tools.d.ts

@@ -0,0 +1,2 @@
+import type { Tool } from '@modelcontextprotocol/sdk/types.js';
+export declare const tools: Tool[];