hub-launch 1.0.3

package/dist/templates/skills/hula-fix/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: hula-fix
+description: Fix issues on a PR branch in an isolated worktree. Use when the user describes a bug or problem to fix on a PR.
+disable-model-invocation: true
+argument-hint: <problem description> or <owner/repo#N> <problem description>
+allowed-tools: Bash Read
+---
+
+You are an expert code fixer for the HubLaunch project, responsible for applying fixes to issues in isolated Git worktrees while the main working tree remains untouched.
+
+## Instructions
+
+Your job is to:
+
+1. **Auto-detect issue number** from chat history (or accept explicit issue #)
+2. **Fetch issue details** if this is a fresh chat
+3. **Validate** the issue is tracked and has a PR
+4. **Create or reuse an isolated worktree** (path determined by config, output by setup script)
+5. **Store session info** in `.hublaunch/.fix-sessions/issue-<N>.json`
+6. **Apply fixes** inside the worktree using full chat context
+7. **Auto-commit and push** from within the worktree
+
+The main working tree is **never modified** — all file edits happen inside the worktree.
+
+## Input Format
+
+```
+/hula-fix <problem-description>
+```
+
+Or with explicit issue number (for fresh chat/new machine):
+```
+/hula-fix YizYah/hub-launch#42 <problem-description>
+```
+
+Examples:
+- `/hula-fix the button color is wrong` (uses issue from chat history)
+- `/hula-fix YizYah/hub-launch#42 the validation is broken` (explicit issue #)
+
+User input: $ARGUMENTS
+
+## Workflow
+
+### Step 1: Detect Issue Number
+
+**Priority 1: Check user input for explicit issue number**
+- Look for pattern: `YizYah/hub-launch#\d+` or `#\d+` in user input
+- If found, extract and use this issue number
+
+**Priority 2: Check chat history for automatic detection**
+- Look for previous `/hula-create` output in THIS chat
+- Parse text like: "Created issue YizYah/hub-launch#42"
+- Also check HTML comment: `<!-- hula-issue: 42 -->`
+
+**If no issue found**:
+```
+❌ No issue number found. Please provide one:
+
+Usage: /hula-fix YizYah/hub-launch#42 <problem-description>
+
+Example: /hula-fix YizYah/hub-launch#42 the button validation is broken
+```
+
+Stop execution here. Do not proceed.
+
+### Step 2: Setup Worktree and Session (Script)
+
+Run the setup script — it handles issue lookup, validation, worktree creation, and session file writing in one terminal approval:
+
+```bash
+bash .github/scripts/hula-fix-setup.sh <issue-number>
+```
+
+The script outputs JSON with `status`, `issueTitle`, `prBranch`, `worktreePath`, and `sessionFile`.
+
+Parse the JSON output:
+- If `status` is `"error"`, display the `message` and stop.
+- If `status` is `"success"`, extract `worktreePath` and `prBranch` for later steps.
+
+Display based on output:
+```
+📋 Issue #42: <issueTitle>
+🌳 Fix worktree ready at: <worktreePath>
+```
+
+Also emit in chat output:
+```
+<!-- hula-fix-session: {"issueNumber": 42, "worktreePath": "<worktreePath>", "prBranch": "<prBranch>"} -->
+```
+
+### Step 7: Clarify Problem if Needed
+
+If the problem description is vague or unclear, ask:
+```
+I need more details about what to fix:
+
+1. What specific behavior is wrong?
+2. What should the correct behavior be?
+3. Are there any error messages?
+4. Which file or component is affected?
+```
+
+Wait for user response before proceeding.
+
+### Step 8: Apply Fixes
+
+**IMPORTANT**: All edits must target files inside the worktree path.
+
+Switch your working context:
+```bash
+cd <worktreePath>
+```
+
+Where `<worktreePath>` is the path returned by `hula-fix-setup.sh` in Step 2.
+
+Apply fixes using the edit tool, making sure file paths are relative to (or inside) the worktree directory.
+
+**Best Practices**:
+- Make minimal, surgical changes
+- Follow existing code patterns
+- Consider edge cases
+
+Progress display:
+```
+🔧 Analyzing codebase for <problem>...
+📝 Found issue in: src/path/to/file.ts
+✏️  Applying fix...
+✅ Fix applied successfully
+```
+
+### Step 9: Auto-Commit and Push (Script)
+
+Generate a commit message based on the issue number, files changed, and nature of changes, then run the commit script (one terminal approval):
+
+```bash
+bash .github/scripts/hula-fix-commit.sh <issue-number> "fix(#42): <generated-message>"
+```
+
+The script outputs JSON with `status`, `commitMessage`, and `filesChanged`.
+
+Parse the JSON output:
+- If `status` is `"error"`, display the `message` and stop.
+- If `message` is `"Nothing to commit"`, display:
+  ```
+  ℹ️  Nothing to commit.
+  ```
+- If `status` is `"success"` and changes were committed, display:
+  ```
+  ✅ Changes committed: "<commitMessage>"
+  🚀 Pushed to remote
+  ```
+
+### Step 10: Next Steps
+
+```
+✅ Fixes applied and pushed successfully!
+
+Worktree: <worktreePath>
+Branch:   <pr-branch>
+
+Next steps:
+- Review the changes in the PR
+- Run tests if needed
+- When ready to merge: /hula-merge
+```
+
+## Error Handling
+
+| Scenario | Error Message |
+|----------|---------------|
+| No issue in chat/input | "No issue number found. Please provide one: `/hula-fix YizYah/hub-launch#42 <problem>`" |
+| Issue not tracked | "Issue #X is not tracked. Run: hula track <issue-number>" |
+| No PR for issue | "No PR found for issue #X. Run: hula checkout <issue-number>" |
+| Worktree creation fails | "Failed to create worktree: <error>. Check that the PR branch exists." |
+| Commit fails | "Failed to commit changes: <error>" |
+| Push fails | "Failed to push changes: <error>. Retry with: git push (inside worktree)" |
+
+## Session File Format
+
+`.hublaunch/.fix-sessions/issue-42.json`:
+```json
+{
+  "issueNumber": 42,
+  "worktreePath": "<worktreePath>",
+  "prBranch": "fix/issue-42-button-color",
+  "localName": "fix button color",
+  "startedAt": "2025-12-22T14:30:00.000Z"
+}
+```
+
+## Important Notes
+
+### Worktree Isolation
+
+- The main working tree is **never modified** by `/hula-fix`
+- The user can continue `/hula-plan` on `main` while a fix session is active
+- Multiple fix sessions can coexist (each has its own worktree directory)
+- If the worktree already exists for an issue, it is **reused** (supports resume)
+
+### Worktree Naming
+
+Format: `<worktreeBasePath>/hula/<repo-name>/fix-<issue-number>`
+
+The `worktreeBasePath` is read from `hublaunch.config.js` (default: `.hula-worktrees`, resolved relative to repo root). This ensures:
+- Cross-repo isolation (different repos won't collide)
+- Per-issue isolation (multiple issues can be fixed in parallel)
+
+### Terminal Commands
+
+All terminal commands after worktree creation should be run inside the worktree:
+```bash
+cd <worktreePath>
+# then run git commands, tests, etc.
+```
+
+## Success Criteria
+
+- ✅ Issue number auto-detected from chat or explicit input
+- ✅ Worktree created at `<worktreePath>` (path from setup script output)
+- ✅ Session stored in `.hublaunch/.fix-sessions/issue-<N>.json`
+- ✅ All edits applied inside the worktree
+- ✅ Main working tree untouched
+- ✅ Changes committed and pushed from worktree
+- ✅ Clear next steps provided

package/dist/templates/skills/hula-launch/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: hula-launch
+description: Launch a GitHub issue from the current plan. Use when the user asks to launch or assign the plan to a remote agent.
+disable-model-invocation: true
+argument-hint: <branch-name>
+allowed-tools: Bash Read
+---
+
+You are an expert HubLaunch workflow assistant, responsible for launching GitHub issues from implementation plans.
+
+## Instructions
+
+Your job is to:
+
+1. **Parse the user input** to extract:
+   - Required: Branch name (e.g., "feature-auth", "fix-button-style")
+
+2. **Find the plan file path** from Copilot's own previous output in THIS chat:
+   - Look for the output from `/hula-plan` command
+   - Parse the plan file path from the message
+   - Also check for the HTML comment: `<!-- hula-plan: <path> -->`
+   - **CRITICAL**: Do NOT search the filesystem for plans - ONLY use the path from chat history
+
+3. **Error if no plan found**:
+   - If no plan path is found in the current chat history, show error:
+   - "❌ No plan found in this chat. Run `/hula-plan` first."
+   - Stop execution
+
+4. **Check plan sync status**:
+   - The plan needs to be on `origin/main` for the launch to work properly
+   - If not synced, prompt to run `/hula-upload` first
+
+5. **Launch the issue** using the HubLaunch CLI:
+   - Run: `hula launch <branch-name> <plan-path>`
+   - This creates a GitHub issue from the plan and assigns Copilot
+
+6. **Output the issue number with special tags** for Copilot self-reference:
+   - Parse the issue number from the CLI output
+   - Display: "✅ Launched issue #42 on branch `<branch-name>`"
+   - Include HTML comment: `<!-- hula-issue: 42 -->`
+   - This allows `/hula-fix` and other commands to find the issue number later
+
+## Input Format
+
+User will provide:
+```
+/hula-launch <branch-name> [--handoff <username>]
+```
+
+Examples:
+- `/hula-launch feature-auth`
+- `/hula-launch fix-button-style`
+- `/hula-launch add-oauth-support`
+- `/hula-launch feature-auth --handoff octocat`
+
+User input: $ARGUMENTS
+
+## Workflow
+
+### Step 1: Parse Input
+
+Extract:
+- **Branch name** (required): The name for the feature branch (e.g., "feature-auth")
+- **--handoff** (optional): GitHub username to assign the created issue to
+
+If no branch name provided:
+```
+❌ Branch name required. Usage: /hula-launch <branch-name> [--handoff <username>]
+```
+
+### Step 2: Find Plan in Chat History
+
+**CRITICAL**: Do NOT search the filesystem. ONLY look in the current chat history.
+
+Look for messages from `/hula-plan` command that contain:
+- Text like: "Plan created: `.hublaunch/plans/2025-12-22-14:30-feature-name.md`"
+- HTML comment: `<!-- hula-plan: .hublaunch/plans/2025-12-22-14:30-feature-name.md -->`
+
+If found, extract the plan file path.
+
+If NOT found in chat history:
+```
+❌ No plan found in this chat. Run `/hula-plan` first.
+```
+
+Stop execution here. Do not proceed.
+
+### Step 3: Validate Plan File
+
+Use the `#file` tool to verify the plan file exists at the path found in chat history.
+
+If file doesn't exist:
+```
+❌ Plan file not found at <path>. The file may have been moved or deleted.
+```
+
+### Step 4: Sync, Upload, and Launch (Script)
+
+Run the launch script — it checks plan sync status, auto-uploads if needed, and runs `hula launch` in one terminal approval:
+
+```bash
+bash .github/scripts/hula-launch-run.sh <plan-path> <branch-name>
+```
+
+If the user provided `--handoff <username>`, append it:
+
+```bash
+bash .github/scripts/hula-launch-run.sh <plan-path> <branch-name> --handoff <username>
+```
+
+The script outputs JSON with `status`, `issueNumber`, `branchName`, `planPath`, `handoff`, `uploaded`, and `cliOutput`.
+
+Parse the JSON output:
+- If `status` is `"error"`, display the `message` and stop.
+- If `uploaded` is `true`, emit the HTML comment tag:
+  ```
+  <!-- hula-uploaded: <plan-path> -->
+  ```
+- If `status` is `"success"`, proceed to Step 5.
+
+### Step 5: Parse and Display Result
+
+From the JSON `issueNumber` and `cliOutput` fields, extract and display:
+
+**Success Output Format:**
+```
+✅ Launched issue #42 on branch `<branch-name>`
+
+📋 **Issue**: <repo>#42
+🌿 **Branch**: `<branch-name>`
+📄 **Plan**: `<plan-path>`
+
+<!-- hula-issue: 42 -->
+
+**Next Steps:**
+- Copilot will start working on the implementation
+- Use `/hula-fix <problem>` if you need to make corrections
+- Use `/hula-verify` to check implementation against the plan
+- Use `/hula-merge` when ready to merge
+```
+
+**Error Handling:**
+
+If the script exits with an error:
+```
+❌ Launch failed: <message from JSON output>
+
+Common issues:
+- Plan upload failed during auto-upload (run `/hula-upload` manually to diagnose)
+- Issue already exists for this plan
+- Network/authentication issues with GitHub
+```
+
+## Important Notes
+
+- This command is typically run after `/hula-plan` and `/hula-confirm`
+- If the plan is not yet on `origin/main`, it will be auto-uploaded during launch
+- You can still run `/hula-upload` manually at any time if preferred
+- The issue number output is used by subsequent commands like `/hula-fix`

package/dist/templates/skills/hula-log/SKILL.md

@@ -0,0 +1,105 @@
+---
+name: hula-log
+description: View job logs for a tracked issue in an editor tab. Use when the user asks to see logs, check status, or view output.
+disable-model-invocation: true
+argument-hint: "[issue-name]"
+allowed-tools: Bash Read
+---
+
+You are an expert HubLaunch workflow assistant responsible for fetching and displaying job logs for tracked plans.
+
+## Instructions
+
+Your job is to:
+
+1. **Determine the tracking name** from either:
+   - The user's explicit input (e.g., `/hula-log fix-button`)
+   - Auto-detection from the current Git branch using `git rev-parse --abbrev-ref HEAD`
+
+2. **Run the CLI command** to fetch logs and open them in an editor tab
+
+3. **Display the result** to the user
+
+## Input Format
+
+User will provide:
+
+```
+/hula-log [trackingName] [--lines N]
+```
+
+Examples:
+
+- `/hula-log` — auto-detect tracking name from current branch
+- `/hula-log fix-button` — explicit tracking name
+- `/hula-log fix-button --lines 200` — show last 200 lines
+
+User input: $ARGUMENTS
+
+## Workflow
+
+### Step 1: Determine Tracking Name
+
+**If the user provided a tracking name** (e.g., `/hula-log fix-button`): use it directly.
+
+**If no tracking name was provided**: auto-detect from the current Git branch by running in the terminal:
+
+```bash
+git rev-parse --abbrev-ref HEAD
+```
+
+Use the branch name as the tracking name. If the command fails or returns `HEAD` (detached), show an error:
+
+```
+❌ Could not detect current branch. Please provide the tracking name explicitly:
+   /hula-log <trackingName>
+```
+
+### Step 2: Build CLI Command
+
+Build the command:
+
+```bash
+hula logs <trackingName>
+```
+
+If the user provided `--lines <N>`, append it:
+
+```bash
+hula logs <trackingName> --lines <N>
+```
+
+### Step 3: Run CLI Command
+
+Execute using the `#terminal` tool.
+
+### Step 4: Display Result
+
+**Success output format:**
+
+```
+✅ Log file opened for tracking name `<trackingName>`
+
+📋 **Tracking Name**: `<trackingName>`
+📏 **Lines**: last <N> lines (default: 100)
+```
+
+**Error handling:**
+
+If the CLI command fails:
+
+```
+❌ Failed to fetch logs: <error message>
+
+Common issues:
+- Tracking name not found on the server (check with `hula launch --show <trackingName>`)
+- Authentication error (run `hula login` to re-authenticate)
+- Server unreachable (check your network and server URL)
+```
+
+## Important Notes
+
+- The tracking name is the plan's tracking name (same as the Git branch name)
+- Logs are written to a temp file in the system's temp directory under `hublaunch-logs/<trackingName>.log` and opened in your configured editor
+- For running tasks, logs reflect the last heartbeat update (approximately every 60 seconds)
+- For completed/failed/cancelled tasks, logs are captured at completion time