@snipcodeit/mgw 0.1.3 → 0.2.1

package/commands/init.md

@@ -1,7 +1,7 @@
 ---
 name: mgw:init
-description: Bootstrap current repo for MGW integration — creates .mgw/ state, GitHub templates, gitignore entries
-argument-hint: ""
+description: Bootstrap current repo for MGW integration — creates .mgw/ state, GitHub templates, gitignore entries, installs shell completions, and runs config wizard
+argument-hint: "[--no-config]"
 allowed-tools:
   - Bash
   - Read
@@ -12,8 +12,9 @@ allowed-tools:
 
 <objective>
 One-time setup for a repo to work with MGW. Creates the .mgw/ state directory,
-GitHub issue/PR templates, and ensures gitignore entries. Safe to re-run — skips
-anything that already exists.
+GitHub issue/PR templates, ensures gitignore entries, and runs an interactive
+config wizard for first-time setup preferences. Safe to re-run — skips anything
+that already exists. Pass --no-config to skip the wizard.
 </objective>
 
 <execution_context>
@@ -213,6 +214,109 @@ gh label create "mgw:blocked" --description "Pipeline blocked by stakeholder com
 `--force` updates existing labels without error.
 </step>
 
+<step name="install_completions">
+**Offer to install shell completions (opt-in):**
+
+Locate the completions directory bundled with the MGW package:
+```bash
+MGW_PKG_DIR=$(node -e "const path = require('path'); console.log(path.resolve(__dirname, '..', '..'))" 2>/dev/null || echo "")
+COMPLETIONS_DIR="${MGW_PKG_DIR}/completions"
+```
+
+If completions are not found (package not globally installed or completions dir absent) → skip silently, note "Shell completions not available (mgw not installed globally)" in report.
+
+If completions are found, detect the user's shell and determine the install target:
+```bash
+CURRENT_SHELL=$(basename "${SHELL:-}")
+```
+
+Shell → target directory mapping:
+- `bash` → `~/.local/share/bash-completion/completions/` (source file: `mgw.bash`)
+- `zsh`  → `~/.zsh/completions/` (source file: `mgw.zsh`)
+- `fish` → `~/.config/fish/completions/` (source file: `mgw.fish`)
+
+If shell is unrecognized or `SHELL` is unset → show all three install commands and skip auto-install.
+
+**Interactive mode (default):** Ask the user:
+```
+Shell completions are available for ${CURRENT_SHELL}.
+
+Install to ${COMPLETION_TARGET_DIR}? [Y/n]
+```
+
+If the user answers yes (or presses Enter for the default):
+```bash
+mkdir -p "${COMPLETION_TARGET_DIR}"
+cp "${COMPLETIONS_DIR}/mgw.${SHELL_EXT}" "${COMPLETION_TARGET_DIR}/mgw.${SHELL_EXT}"
+```
+
+Then show the source/activation line appropriate for the shell:
+- bash: `# Reload with: source ~/.local/share/bash-completion/completions/mgw.bash`
+  (or add to ~/.bashrc: `source ~/.local/share/bash-completion/completions/mgw.bash`)
+- zsh: Add to ~/.zshrc (required — ~/.zsh/completions is not in default $fpath):
+  ```
+  fpath=(~/.zsh/completions $fpath)
+  autoload -Uz compinit
+  compinit
+  ```
+  Then reload: `source ~/.zshrc`
+- fish: `# Completions loaded automatically from ~/.config/fish/completions/`
+
+If user answers no → skip, note "Shell completions: skipped" in report.
+
+If the completion file already exists at the target → overwrite (idempotent re-run).
+
+**Non-interactive mode** (stdin is not a TTY): Skip the prompt entirely, print the install command as a hint:
+```
+  Shell completions available. Install manually:
+    cp ${COMPLETIONS_DIR}/mgw.${SHELL_EXT} ${COMPLETION_TARGET_DIR}/mgw.${SHELL_EXT}
+```
+</step>
+
+<step name="run_config_wizard">
+**Run interactive config wizard for first-time setup (skip if --no-config or config already exists):**
+
+Check whether the wizard should run:
+```bash
+# Skip if --no-config flag is present
+# Skip if stdin is not a TTY (CI/piped context)
+# Skip if .mgw/config.json already exists
+```
+
+Use `lib/config-wizard.cjs` to determine and execute:
+```javascript
+const { runWizard, shouldRunWizard } = require('./lib/config-wizard.cjs');
+const mgwDir = path.join(REPO_ROOT, '.mgw');
+
+if (shouldRunWizard(mgwDir, process.argv)) {
+  await runWizard(mgwDir);
+} else if (fs.existsSync(path.join(mgwDir, 'config.json'))) {
+  // report: ".mgw/config.json   exists, skipping wizard"
+} else {
+  // report: ".mgw/config.json   skipped (--no-config)"
+}
+```
+
+The wizard asks the user four questions in order:
+1. **GitHub username** — auto-detected from `gh api user -q .login`; user may accept or override
+2. **Default issue state filter** — `open` (default) or `all`
+3. **Default issue limit** — `10`, `25` (default), or `50`
+4. **Default assignee filter** — `me` (default) or `all`
+
+Answers are written to `${REPO_ROOT}/.mgw/config.json`:
+```json
+{
+  "github_username": "...",
+  "default_issue_state": "open",
+  "default_issue_limit": 25,
+  "default_assignee": "me",
+  "created_at": "<ISO timestamp>"
+}
+```
+
+If the wizard errors or is interrupted, report the failure but do not abort the overall init — config is optional.
+</step>
+
 <step name="report">
 **Report setup status:**
 
@@ -223,11 +327,13 @@ gh label create "mgw:blocked" --description "Pipeline blocked by stakeholder com
 
   .mgw/                  ${created|exists}
   .mgw/cross-refs.json   ${created|exists}
+  .mgw/config.json       ${written|exists|skipped}
   .gitignore entries     ${added|exists}
   Issue templates        ${created|exists}
   PR template            ${created|exists}
   GitHub labels          synced
   MGW pipeline labels    synced (7 labels)
+  Shell completions      ${installed (bash|zsh|fish)|skipped|not available}
 
 Ready to use:
   /mgw:issues            Browse issues
@@ -242,9 +348,13 @@ Ready to use:
 - [ ] .mgw/ directory structure created
 - [ ] .mgw/ and .worktrees/ in .gitignore
 - [ ] cross-refs.json initialized
+- [ ] Config wizard run (or skipped via --no-config / pre-existing config.json)
+- [ ] .mgw/config.json written with user preferences (unless skipped)
 - [ ] Issue templates created (bug + enhancement)
 - [ ] PR template created
 - [ ] GitHub labels ensured (bug, enhancement)
 - [ ] MGW pipeline labels ensured (7 mgw:* labels)
-- [ ] Setup report shown
+- [ ] Shell completion install offered (interactive) or hint printed (non-interactive)
+- [ ] Completion install skipped gracefully if completions dir not found
+- [ ] Setup report shown with completion status line
 </success_criteria>

package/commands/issues.md

@@ -1,7 +1,7 @@
 ---
 name: mgw:issues
 description: List and filter GitHub issues, pick one to triage
-argument-hint: "[--label <label>] [--milestone <name>] [--assignee <user>] [--state open|closed|all]"
+argument-hint: "[--label <label>] [--milestone <name>] [--assignee <user>] [--state open|closed|all] [--search <query>]"
 allowed-tools:
   - Bash
   - Read
@@ -14,6 +14,10 @@ Browse GitHub issues for the current repo. Presents a scannable table filtered b
 assignment (defaults to @me), labels, milestone, or state. Pick an issue to route
 into triage via /mgw:issue.
 
+This is the Claude Code slash-command variant (table + AskUserQuestion). When running
+from the CLI (`mgw issues`), an interactive TUI browser launches instead — see
+`docs/TUI-DESIGN.md` and `lib/tui/index.cjs` for the TUI implementation.
+
 No side effects — read-only GitHub access. Safe to run anytime.
 </objective>
 
@@ -107,3 +111,61 @@ If invalid → re-prompt.
 - [ ] User can pick an issue number
 - [ ] Routes to /mgw:issue <number>
 </success_criteria>
+
+## TUI Mode (CLI only)
+
+When `mgw issues` runs from the CLI entry point (`bin/mgw.cjs`) in an interactive
+terminal, it launches a full TUI browser instead of a static table.
+
+**Entry point:** `lib/tui/index.cjs` — `createIssuesBrowser(options)`
+
+**CLI options:**
+```
+mgw issues [options]
+  -l, --label <label>        Filter by label
+  -m, --milestone <name>     Filter by milestone
+  -a, --assignee <user>      Assignee filter (default: @me, 'all' = no filter)
+  -s, --search <query>       Pre-populate the fuzzy search input
+  --state <state>            Issue state: open|closed|all (default: open)
+  --limit <n>                Max issues to load (default: 50)
+```
+
+**TUI keyboard shortcuts:**
+| Key | Action |
+|-----|--------|
+| `j` / `↓` | Scroll down |
+| `k` / `↑` | Scroll up |
+| `/` | Focus search input |
+| `Enter` | Select issue → prints `#N — Title` and exits |
+| `q` / `Esc` | Quit |
+| `Tab` | Cycle focus (list → detail → filter) |
+| `g` / `Home` | Jump to top |
+| `G` / `End` | Jump to bottom |
+| `?` | Toggle keyboard help |
+
+**Non-interactive fallback:**
+When stdout is not a TTY (piped, CI, `MGW_NO_TUI=1`), the static table is printed
+to stdout. Pipe-friendly — no ANSI codes, no interactive elements.
+
+```bash
+mgw issues | grep "auth"
+```
+
+**Implementation modules:**
+```
+lib/tui/
+  index.cjs      — createIssuesBrowser(options) — entry point
+  search.cjs     — FuzzySearch class — pure, no UI dependency
+  keyboard.cjs   — KeyboardHandler (EventEmitter)
+  renderer.cjs   — createRenderer() — blessed/neo-blessed adapter
+  graceful.cjs   — isInteractive(), renderStaticTable()
+```
+
+**Design document:** `docs/TUI-DESIGN.md` — library selection rationale, wireframe, full interface contracts.
+
+**Rendering library:** `neo-blessed` (optional dependency). Renderer is swappable via `lib/tui/renderer.cjs`.
+
+**Slash command vs CLI:**
+This slash command (`/mgw:issues`) uses the static table + `AskUserQuestion` pattern
+because Claude Code sessions don't have raw TTY access. The TUI is CLI-only (`mgw issues`).
+Both paths route to `/mgw:issue <number>` for triage.

package/commands/milestone.md

@@ -141,6 +141,28 @@ Display:
 Issues: ${TOTAL_ISSUES}
 Mode: ${INTERACTIVE ? "Interactive" : "Autonomous"}
 ```
+
+Then print the initial milestone progress bar (0 done, TOTAL_ISSUES total):
+```bash
+ISSUES_WITH_STAGES=$(echo "$ISSUES_JSON" | python3 -c "
+import json,sys
+issues = json.load(sys.stdin)
+result = [{'number': i['github_number'], 'pipeline_stage': i.get('pipeline_stage', 'new')} for i in issues]
+print(json.dumps(result))
+")
+
+node -e "
+const { printMilestoneProgress } = require('./lib/progress.cjs');
+const issues = JSON.parse(process.env.ISSUES_WITH_STAGES || '[]');
+const doneCount = issues.filter(i => i.pipeline_stage === 'done' || i.pipeline_stage === 'pr-created').length;
+printMilestoneProgress({
+  done: doneCount,
+  total: issues.length,
+  label: process.env.MILESTONE_NAME,
+  issues
+});
+" MILESTONE_NAME="$MILESTONE_NAME" ISSUES_WITH_STAGES="$ISSUES_WITH_STAGES"
+```
 </step>
 
 <step name="resolve_execution_order">
@@ -723,6 +745,27 @@ writeProjectState(state);
 
   ISSUES_RUN=$((ISSUES_RUN + 1))
 
+  # Update and print milestone progress bar after each issue completes
+  ISSUES_WITH_STAGES=$(node -e "
+const { loadProjectState, resolveActiveMilestoneIndex } = require('./lib/state.cjs');
+const state = loadProjectState();
+const idx = resolveActiveMilestoneIndex(state);
+if (idx < 0) { console.log('[]'); process.exit(0); }
+const issues = state.milestones[idx].issues || [];
+console.log(JSON.stringify(issues.map(i => ({ number: i.github_number, pipeline_stage: i.pipeline_stage || 'new' }))));
+" 2>/dev/null || echo "[]")
+
+  node -e "
+const { printMilestoneProgress } = require('./lib/progress.cjs');
+const issues = JSON.parse(process.env.ISSUES_WITH_STAGES || '[]');
+const doneCount = issues.filter(i => i.pipeline_stage === 'done' || i.pipeline_stage === 'pr-created').length;
+printMilestoneProgress({
+  done: doneCount,
+  total: issues.length,
+  issues
+});
+" ISSUES_WITH_STAGES="$ISSUES_WITH_STAGES"
+
   # If --interactive: pause between issues
   if [ "$INTERACTIVE" = true ]; then
     AskUserQuestion(