tide-commander 0.52.0

package/dist/src/packages/server/data/builtin-skills/bitbucket-pr.js

@@ -0,0 +1,298 @@
+export const bitbucketPR = {
+    slug: 'bitbucket-pr',
+    name: 'Bitbucket PR',
+    description: 'Create pull requests on Bitbucket using curl. Use this skill when asked to create PRs, merge requests, or submit code for review on Bitbucket.',
+    allowedTools: ['Bash(curl:*)', 'Bash(git:*)', 'Read', 'Grep', 'Glob'],
+    content: `# Bitbucket Pull Request Creator
+
+Create pull requests on Bitbucket Cloud using curl API requests.
+
+## Required Secrets
+
+This skill requires the following secrets to be configured in Tide Commander's Toolbox > Secrets:
+
+| Secret Key | Description |
+|------------|-------------|
+| \`BITBUCKET_USERNAME\` | Your Bitbucket username |
+| \`BITBUCKET_APP_PASSWORD\` | Bitbucket App Password with repo and PR permissions |
+
+**Setting up Bitbucket App Password:**
+1. Go to Bitbucket Settings > App passwords
+2. Create a new app password with permissions:
+   - Repositories: Read, Write
+   - Pull Requests: Read, Write
+3. Add it to Tide Commander secrets as \`BITBUCKET_APP_PASSWORD\`
+
+Once configured, use the placeholders \`{{BITBUCKET_USERNAME}}\` and \`{{BITBUCKET_APP_PASSWORD}}\` in your curl commands.
+
+---
+
+## Integration with Streaming Exec
+
+For long-running git operations (like pushing large branches), use the **Streaming Command Execution** skill to stream output to the terminal. Example:
+
+\`\`\`bash
+curl -s -X POST http://localhost:5174/api/exec \\
+  -H "Content-Type: application/json" \\
+  -d '{"agentId":"YOUR_AGENT_ID","command":"git push -u origin feature-branch"}'
+\`\`\`
+
+---
+
+## Workflow: Create Pull Request
+
+When asked to "create PR", "make pull request", "submit for review" on Bitbucket:
+
+### Step 1: Gather Information
+
+First, collect the required information:
+
+\`\`\`bash
+# Get current branch
+CURRENT_BRANCH=$(git branch --show-current)
+echo "Source branch: $CURRENT_BRANCH"
+
+# Get remote URL to extract workspace/repo
+git remote -v
+
+# Check for unpushed commits
+git status
+\`\`\`
+
+**Extract workspace and repo from remote URL:**
+- HTTPS: \`https://bitbucket.org/WORKSPACE/REPO.git\`
+- SSH: \`git@bitbucket.org:WORKSPACE/REPO.git\`
+
+### Step 2: Ensure Branch is Pushed
+
+\`\`\`bash
+# Push current branch to remote
+git push -u origin $(git branch --show-current)
+\`\`\`
+
+### Step 3: Gather PR Details
+
+Ask the user for (or infer from context):
+- **Title**: Brief description of the change
+- **Description**: Detailed explanation
+- **Target branch**: Usually \`main\` or \`master\`
+- **Reviewers**: Optional, Bitbucket account IDs
+
+### Step 4: Create the Pull Request
+
+\`\`\`bash
+curl -s -X POST \\
+  -u "{{BITBUCKET_USERNAME}}:{{BITBUCKET_APP_PASSWORD}}" \\
+  -H "Content-Type: application/json" \\
+  "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests" \\
+  -d '{
+    "title": "PR_TITLE",
+    "description": "PR_DESCRIPTION",
+    "source": {
+      "branch": {
+        "name": "SOURCE_BRANCH"
+      }
+    },
+    "destination": {
+      "branch": {
+        "name": "TARGET_BRANCH"
+      }
+    },
+    "close_source_branch": true
+  }'
+\`\`\`
+
+**Replace placeholders:**
+- \`{workspace}\`: Bitbucket workspace (e.g., "mycompany")
+- \`{repo_slug}\`: Repository name (e.g., "my-project")
+- \`PR_TITLE\`: Title of the PR
+- \`PR_DESCRIPTION\`: Description in markdown
+- \`SOURCE_BRANCH\`: Your feature branch
+- \`TARGET_BRANCH\`: Usually "main" or "master"
+
+### Step 5: Parse Response
+
+On success, extract the PR URL from the response:
+
+\`\`\`bash
+# Response contains: {"links": {"html": {"href": "https://bitbucket.org/..."}}}
+# Use jq if available, or grep for the URL
+\`\`\`
+
+Report the PR URL to the user.
+
+---
+
+## Complete Example Script
+
+\`\`\`bash
+# Variables (gather these first)
+WORKSPACE="myworkspace"
+REPO_SLUG="myrepo"
+SOURCE_BRANCH=$(git branch --show-current)
+TARGET_BRANCH="main"
+PR_TITLE="feat: Add new feature"
+PR_DESCRIPTION="## Summary\\n\\n- Added X\\n- Fixed Y\\n\\n## Testing\\n\\n- Ran unit tests"
+
+# Create PR using secrets placeholders
+curl -s -X POST \\
+  -u "{{BITBUCKET_USERNAME}}:{{BITBUCKET_APP_PASSWORD}}" \\
+  -H "Content-Type: application/json" \\
+  "https://api.bitbucket.org/2.0/repositories/$WORKSPACE/$REPO_SLUG/pullrequests" \\
+  -d "$(cat <<EOF
+{
+  "title": "$PR_TITLE",
+  "description": "$PR_DESCRIPTION",
+  "source": {
+    "branch": {
+      "name": "$SOURCE_BRANCH"
+    }
+  },
+  "destination": {
+    "branch": {
+      "name": "$TARGET_BRANCH"
+    }
+  },
+  "close_source_branch": true
+}
+EOF
+)"
+\`\`\`
+
+---
+
+## Add Reviewers
+
+To add reviewers, include them in the request:
+
+\`\`\`json
+{
+  "title": "PR Title",
+  "reviewers": [
+    {"account_id": "557058:12345678-1234-1234-1234-123456789012"},
+    {"account_id": "557058:abcdefgh-abcd-abcd-abcd-abcdefghijkl"}
+  ],
+  ...
+}
+\`\`\`
+
+**Find reviewer account IDs:**
+\`\`\`bash
+# List workspace members
+curl -s -u "{{BITBUCKET_USERNAME}}:{{BITBUCKET_APP_PASSWORD}}" \\
+  "https://api.bitbucket.org/2.0/workspaces/{workspace}/members"
+\`\`\`
+
+---
+
+## Other Useful API Endpoints
+
+### List Open PRs
+
+\`\`\`bash
+curl -s -u "{{BITBUCKET_USERNAME}}:{{BITBUCKET_APP_PASSWORD}}" \\
+  "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests?state=OPEN"
+\`\`\`
+
+### Get PR Details
+
+\`\`\`bash
+curl -s -u "{{BITBUCKET_USERNAME}}:{{BITBUCKET_APP_PASSWORD}}" \\
+  "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{pr_id}"
+\`\`\`
+
+### Approve a PR
+
+\`\`\`bash
+curl -s -X POST \\
+  -u "{{BITBUCKET_USERNAME}}:{{BITBUCKET_APP_PASSWORD}}" \\
+  "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{pr_id}/approve"
+\`\`\`
+
+### Merge a PR
+
+\`\`\`bash
+curl -s -X POST \\
+  -u "{{BITBUCKET_USERNAME}}:{{BITBUCKET_APP_PASSWORD}}" \\
+  -H "Content-Type: application/json" \\
+  "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{pr_id}/merge" \\
+  -d '{
+    "merge_strategy": "squash",
+    "close_source_branch": true,
+    "message": "Merged PR: Title"
+  }'
+\`\`\`
+
+**Merge strategies:**
+- \`merge_commit\`: Standard merge
+- \`squash\`: Squash all commits
+- \`fast_forward\`: Fast-forward if possible
+
+### Decline a PR
+
+\`\`\`bash
+curl -s -X POST \\
+  -u "{{BITBUCKET_USERNAME}}:{{BITBUCKET_APP_PASSWORD}}" \\
+  "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{pr_id}/decline"
+\`\`\`
+
+### Add Comment to PR
+
+\`\`\`bash
+curl -s -X POST \\
+  -u "{{BITBUCKET_USERNAME}}:{{BITBUCKET_APP_PASSWORD}}" \\
+  -H "Content-Type: application/json" \\
+  "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{pr_id}/comments" \\
+  -d '{
+    "content": {
+      "raw": "Your comment here"
+    }
+  }'
+\`\`\`
+
+---
+
+## Error Handling
+
+Common errors and solutions:
+
+| HTTP Code | Meaning | Solution |
+|-----------|---------|----------|
+| 401 | Unauthorized | Check BITBUCKET_USERNAME and BITBUCKET_APP_PASSWORD secrets |
+| 403 | Forbidden | App password lacks permissions |
+| 404 | Not Found | Check workspace/repo slug |
+| 400 | Bad Request | Check JSON payload format |
+| 409 | Conflict | PR already exists for this branch |
+
+**Debug requests:**
+\`\`\`bash
+# Add -v for verbose output
+curl -v -X POST ...
+\`\`\`
+
+---
+
+## Safety Rules
+
+1. **NEVER commit credentials** to the repository - always use \`{{SECRET}}\` placeholders
+2. **ALWAYS verify** the target branch before creating PR
+3. **ALWAYS push** the source branch before creating PR
+4. **CHECK** for existing PRs before creating duplicates
+5. **CONFIRM** with user before merging or declining PRs
+
+---
+
+## Quick Reference
+
+| Action | Endpoint | Method |
+|--------|----------|--------|
+| Create PR | \`/pullrequests\` | POST |
+| List PRs | \`/pullrequests\` | GET |
+| Get PR | \`/pullrequests/{id}\` | GET |
+| Approve | \`/pullrequests/{id}/approve\` | POST |
+| Merge | \`/pullrequests/{id}/merge\` | POST |
+| Decline | \`/pullrequests/{id}/decline\` | POST |
+| Comment | \`/pullrequests/{id}/comments\` | POST |
+
+Base URL: \`https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}\``,
+};

package/dist/src/packages/server/data/builtin-skills/full-notifications.js

@@ -0,0 +1,49 @@
+export const fullNotifications = {
+    slug: 'full-notifications',
+    name: 'Full Notifications',
+    description: 'Send notification via browser, android or in-app',
+    allowedTools: ['Bash(curl:*)', 'Bash(gdbus:*)'],
+    content: `# Task Completion Notifications (MANDATORY)
+
+**IMPORTANT: You MUST send a notification automatically whenever you complete a task. This is not optional.**
+
+## Trigger Conditions (Act Immediately)
+1. **Task Completed** - Right after finishing any user request
+2. **Blocking Error** - When you cannot proceed
+3. **Awaiting Input** - When you need user decision
+
+## Command Template
+\`\`\`bash
+curl -s -X POST http://localhost:5174/api/notify -H "Content-Type: application/json" -d '{"agentId":"YOUR_AGENT_ID","title":"TITLE","message":"MESSAGE"}' & gdbus call --session --dest=org.freedesktop.Notifications --object-path=/org/freedesktop/Notifications --method=org.freedesktop.Notifications.Notify 'Tide Commander' 0 'ICON' 'TITLE' 'MESSAGE' '[]' '{}' 5000
+\`\`\`
+
+## Examples by Type
+
+**Task Complete:**
+\`\`\`bash
+curl -s -X POST http://localhost:5174/api/notify -H "Content-Type: application/json" -d '{"agentId":"YOUR_AGENT_ID","title":"Task Complete","message":"Build succeeded"}' & gdbus call --session --dest=org.freedesktop.Notifications --object-path=/org/freedesktop/Notifications --method=org.freedesktop.Notifications.Notify 'Tide Commander' 0 'dialog-information' 'Task Complete' 'Build succeeded' '[]' '{}' 5000
+\`\`\`
+
+**Error/Attention Needed:**
+\`\`\`bash
+curl -s -X POST http://localhost:5174/api/notify -H "Content-Type: application/json" -d '{"agentId":"YOUR_AGENT_ID","title":"Error","message":"Build failed"}' & gdbus call --session --dest=org.freedesktop.Notifications --object-path=/org/freedesktop/Notifications --method=org.freedesktop.Notifications.Notify 'Tide Commander' 0 'dialog-warning' 'Error' 'Build failed' '[]' '{}' 5000
+\`\`\`
+
+**Input Required:**
+\`\`\`bash
+curl -s -X POST http://localhost:5174/api/notify -H "Content-Type: application/json" -d '{"agentId":"YOUR_AGENT_ID","title":"Input Needed","message":"Which database?"}' & gdbus call --session --dest=org.freedesktop.Notifications --object-path=/org/freedesktop/Notifications --method=org.freedesktop.Notifications.Notify 'Tide Commander' 0 'dialog-question' 'Input Needed' 'Which database?' '[]' '{}' 5000
+\`\`\`
+
+## Icons (gdbus)
+- \`dialog-information\` - Task complete
+- \`dialog-warning\` - Error/attention needed
+- \`dialog-question\` - Input required
+
+## Rules
+- Replace \`YOUR_AGENT_ID\` with your actual agent ID from the system prompt
+- Keep messages under 50 characters
+- **IMPORTANT: Do NOT use exclamation marks (!) in messages** - they cause bash history expansion errors
+- Send notification as your FINAL action after completing work
+- Do NOT skip this step - the user relies on notifications
+- The \`&\` runs both commands in parallel (curl for mobile/browser, gdbus for Linux desktop)`,
+};

package/dist/src/packages/server/data/builtin-skills/git-captain.js

@@ -0,0 +1,304 @@
+export const gitCaptain = {
+    slug: 'git-captain',
+    name: 'Git Captain',
+    description: 'Use this skill for Git operations: committing changes, updating versions, managing changelogs, creating tags, pulling remote changes, and handling merge conflicts safely.',
+    allowedTools: ['Bash(git:*)', 'Bash(npm:*)', 'Read', 'Edit', 'Grep', 'Glob'],
+    content: `# Git Captain
+
+A comprehensive Git workflow skill for version management, changelogs, tagging, and safe collaboration.
+
+## Core Principles
+
+1. **Never force push** to shared branches (main, master, develop)
+2. **Never auto-resolve conflicts** - always report them to the user
+3. **Always verify** the current branch before operations
+4. **Always show diffs** before committing
+5. **Keep changelogs organized** and human-readable
+
+---
+
+## Workflow: Upload Changes (Commit, Version, Changelog, Tag)
+
+When asked to "upload changes", "release", "bump version", or similar:
+
+### Step 1: Check Current State
+
+\`\`\`bash
+# Check we're on the right branch and have no conflicts
+git status
+git branch --show-current
+\`\`\`
+
+If there are untracked files or changes, list them for the user.
+
+### Step 2: Pull Latest Changes First
+
+\`\`\`bash
+# Always pull before pushing to avoid conflicts
+git pull --rebase origin $(git branch --show-current)
+\`\`\`
+
+**If conflicts occur:** STOP immediately and report to user:
+> "Merge conflicts detected. Please resolve these manually:
+> [list conflicting files]
+> After resolving, run \`git add <files>\` and \`git rebase --continue\`"
+
+### Step 3: Review Changes
+
+\`\`\`bash
+# Show what will be committed
+git diff --stat
+git diff
+\`\`\`
+
+Present a summary of changes to the user.
+
+### Step 4: Determine Version Bump
+
+Ask the user or infer from changes:
+- **patch** (0.0.X): Bug fixes, small changes
+- **minor** (0.X.0): New features, non-breaking changes
+- **major** (X.0.0): Breaking changes, major rewrites
+
+Read current version from \`package.json\`:
+\`\`\`bash
+cat package.json | grep '"version"'
+\`\`\`
+
+### Step 5: Update Version
+
+\`\`\`bash
+# Use npm version (updates package.json and creates git tag)
+npm version <patch|minor|major> --no-git-tag-version
+\`\`\`
+
+Or manually edit package.json if npm is not available.
+
+### Step 6: Update Changelog
+
+Look for \`CHANGELOG.md\` in the project root. If it doesn't exist, create one.
+
+**Changelog Format:**
+\`\`\`markdown
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [X.Y.Z] - YYYY-MM-DD
+
+### Added
+- New feature descriptions
+
+### Changed
+- Changes to existing functionality
+
+### Fixed
+- Bug fixes
+
+### Removed
+- Removed features
+
+### Security
+- Security-related changes
+
+### Deprecated
+- Features that will be removed in future versions
+\`\`\`
+
+**How to categorize commits:**
+- \`feat:\` or \`add:\` -> Added
+- \`fix:\` or \`bugfix:\` -> Fixed
+- \`change:\` or \`update:\` or \`refactor:\` -> Changed
+- \`remove:\` or \`delete:\` -> Removed
+- \`security:\` -> Security
+- \`deprecate:\` -> Deprecated
+
+Read recent commits to summarize:
+\`\`\`bash
+git log --oneline -20
+\`\`\`
+
+### Step 7: Stage and Commit
+
+\`\`\`bash
+# Stage all changes including version and changelog
+git add package.json CHANGELOG.md
+git add -A  # or specific files
+
+# Create commit with conventional format
+git commit -m "chore(release): v<VERSION>
+
+- Summary of main changes
+- Another change
+
+Co-Authored-By: Claude <noreply@anthropic.com>"
+\`\`\`
+
+### Step 8: Create Tag
+
+\`\`\`bash
+# Create annotated tag
+git tag -a v<VERSION> -m "Release v<VERSION>
+
+Highlights:
+- Main feature or fix
+- Another highlight"
+\`\`\`
+
+### Step 9: Push Changes and Tags
+
+\`\`\`bash
+# Push commits
+git push origin $(git branch --show-current)
+
+# Push tags
+git push origin v<VERSION>
+\`\`\`
+
+### Step 10: Create GitHub Release
+
+After pushing the tag, create a GitHub release to make it visible in the "Releases" tab:
+
+\`\`\`bash
+# Create GitHub release with notes
+gh release create v<VERSION> --notes "<RELEASE_NOTES>"
+\`\`\`
+
+**Release notes format:**
+\`\`\`markdown
+## Highlights
+
+### ✨ Feature Name
+Brief description of what was added.
+
+### 🐛 Bug Fixes
+Description of bugs fixed.
+
+## Changes
+- Bullet point of changes
+- Another change
+
+## Technical Details
+- Technical implementation note
+- Architecture changes
+\`\`\`
+
+---
+
+## Workflow: Download Changes (Pull/Sync)
+
+When asked to "pull", "sync", "download changes", or "update from remote":
+
+### Step 1: Stash Local Changes (if any)
+
+\`\`\`bash
+git status
+# If there are uncommitted changes:
+git stash push -m "Auto-stash before pull $(date +%Y%m%d-%H%M%S)"
+\`\`\`
+
+### Step 2: Fetch and Pull
+
+\`\`\`bash
+git fetch origin
+git pull --rebase origin $(git branch --show-current)
+\`\`\`
+
+### Step 3: Handle Conflicts
+
+**If conflicts occur:** STOP and report to user:
+
+> "Merge conflicts detected during pull. The following files have conflicts:
+>
+> [list files from \`git diff --name-only --diff-filter=U\`]
+>
+> **Do not attempt to auto-resolve.** Please:
+> 1. Open each file and look for \`<<<<<<<\`, \`=======\`, \`>>>>>>>\` markers
+> 2. Decide which changes to keep
+> 3. Remove the conflict markers
+> 4. Run \`git add <resolved-files>\`
+> 5. Run \`git rebase --continue\`
+>
+> If you want to abort: \`git rebase --abort\`"
+
+### Step 4: Restore Stashed Changes
+
+\`\`\`bash
+# If we stashed earlier
+git stash pop
+\`\`\`
+
+If stash pop causes conflicts, report to user.
+
+---
+
+## Workflow: Check Status
+
+When asked about git status, branch info, or repository state:
+
+\`\`\`bash
+# Comprehensive status check
+echo "=== Branch ===" && git branch -vv
+echo ""
+echo "=== Status ===" && git status -sb
+echo ""
+echo "=== Recent Commits ===" && git log --oneline -5
+echo ""
+echo "=== Remote ===" && git remote -v
+\`\`\`
+
+---
+
+## Safety Rules
+
+1. **NEVER run these commands without explicit user permission:**
+   - \`git push --force\` or \`git push -f\`
+   - \`git reset --hard\`
+   - \`git clean -fd\`
+   - \`git checkout .\` (discards all changes)
+   - \`git branch -D\` (force delete branch)
+
+2. **ALWAYS stop and report to user when:**
+   - Merge conflicts are detected
+   - Rebase conflicts occur
+   - Push is rejected
+   - Branch is behind remote by many commits (>10)
+
+3. **ALWAYS verify before destructive operations:**
+   - Confirm branch name before pushing
+   - Show diff before committing
+   - List files before \`git add -A\`
+
+---
+
+## Quick Reference Commands
+
+| Action | Command |
+|--------|---------|
+| Check status | \`git status -sb\` |
+| View diff | \`git diff\` |
+| View staged diff | \`git diff --cached\` |
+| Recent commits | \`git log --oneline -10\` |
+| Current branch | \`git branch --show-current\` |
+| List branches | \`git branch -a\` |
+| List tags | \`git tag -l\` |
+| Undo last commit (keep changes) | \`git reset --soft HEAD~1\` |
+| Discard file changes | \`git checkout -- <file>\` |
+| Create branch | \`git checkout -b <name>\` |
+| Switch branch | \`git checkout <name>\` |
+
+---
+
+## Version Number Guidelines
+
+- **0.x.x** - Pre-release, API may change
+- **1.0.0** - First stable release
+- **x.Y.0** - New features added (backwards compatible)
+- **x.x.Z** - Bug fixes only
+
+When in doubt about version type, ask the user:
+> "What type of release is this?
+> - **patch** (bug fixes only)
+> - **minor** (new features, no breaking changes)
+> - **major** (breaking changes)"`,
+};

package/dist/src/packages/server/data/builtin-skills/index.js

@@ -0,0 +1,61 @@
+/**
+ * Built-in Skills
+ *
+ * These are core Tide Commander skills that ship with the application.
+ * They cannot be modified or deleted by users.
+ */
+// Import individual skills
+import { fullNotifications } from './full-notifications.js';
+import { sendMessageToAgent } from './send-message-to-agent.js';
+import { gitCaptain } from './git-captain.js';
+import { serverLogs } from './server-logs.js';
+import { streamingExec } from './streaming-exec.js';
+import { bitbucketPR } from './bitbucket-pr.js';
+import { pm2Logs } from './pm2-logs.js';
+/**
+ * All built-in skills that ship with Tide Commander
+ */
+export const BUILTIN_SKILLS = [
+    fullNotifications,
+    sendMessageToAgent,
+    gitCaptain,
+    serverLogs,
+    streamingExec,
+    bitbucketPR,
+    pm2Logs,
+];
+/**
+ * Get the ID for a built-in skill based on its slug
+ * Built-in skills use a predictable ID format: "builtin-{slug}"
+ */
+export function getBuiltinSkillId(slug) {
+    return `builtin-${slug}`;
+}
+/**
+ * Check if a skill ID is a built-in skill
+ */
+export function isBuiltinSkillId(id) {
+    return id.startsWith('builtin-');
+}
+/**
+ * Convert a built-in skill definition to a full Skill object
+ */
+export function createBuiltinSkill(definition) {
+    const now = Date.now();
+    return {
+        id: getBuiltinSkillId(definition.slug),
+        slug: definition.slug,
+        name: definition.name,
+        description: definition.description,
+        content: definition.content,
+        allowedTools: definition.allowedTools,
+        model: definition.model,
+        context: definition.context,
+        assignedAgentIds: [],
+        assignedAgentClasses: definition.assignedAgentClasses || [],
+        enabled: true,
+        builtin: true,
+        createdAt: now,
+        updatedAt: now,
+    };
+}