revspec 0.7.1 → 0.7.3

package/README.md

@@ -21,6 +21,22 @@ git clone https://github.com/icyrainz/revspec.git
 cd revspec && bun install && bun link
 ```
 
+### Claude Code plugin
+
+Install the `/revspec` skill for Claude Code:
+
+```bash
+/plugin marketplace add icyrainz/revspec
+/plugin install revspec
+```
+
+Or manually (symlink, stays updated with repo):
+
+```bash
+mkdir -p ~/.claude/skills
+ln -sfn /path/to/revspec/skills/revspec ~/.claude/skills/revspec
+```
+
 ## Usage
 
 ```bash
@@ -137,16 +153,6 @@ Sends an AI reply that appears instantly in the reviewer's TUI.
 8. Repeat 3-7 until A (approve)
 ```
 
-### Claude Code skill
-
-Install the `/revspec` skill for Claude Code:
-
-```bash
-./scripts/install-skill.sh
-```
-
-Then use `/revspec` in Claude Code after generating a spec.
-
 ## Testing
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "revspec",
-  "version": "0.7.1",
+  "version": "0.7.3",
   "description": "Terminal-based spec review tool with real-time AI conversation",
   "type": "module",
   "license": "MIT",

package/skills/revspec/SKILL.md

@@ -1,17 +1,18 @@
 ---
 name: revspec
-description: Launch revspec to review a spec document with real-time AI feedback. Use when the user says /revspec, "review the spec", "let me review this", or after generating a spec/design document that needs human review. Also use when a brainstorming or writing-plans skill produces a markdown spec file.
+description: Launch revspec to review a spec document with real-time AI feedback. Use when the user says /revspec, "review the spec", "let me review this", or after generating a spec/design document that needs human review. Also use when a brainstorming or writing-plans skill produces a markdown spec file. Works on any markdown file (ADRs, READMEs, etc.) but primarily designed for spec review. Works even when no .md file exists yet (inline or plan mode content gets saved to a file first). Supports `/revspec <path>` to review a specific file and resuming previous review sessions.
 ---
 
 # Revspec — Live Spec Review
 
-Launch revspec to let the human review a spec document with real-time AI conversation. The reviewer comments on specific lines, you reply instantly, and the discussion continues until the spec is approved.
+Launch revspec to let the human review a spec document with real-time AI conversation. The reviewer comments on specific lines, you reply instantly, and the discussion continues until the spec is approved. Also works on any markdown file.
 
 ## When to Use
 
 - After writing or updating a spec/design document
 - When the user explicitly asks to review a spec
 - After the brainstorming or writing-plans skill produces a `.md` file
+- When the user provides a file path: `/revspec <path>`
 
 ## How It Works
 
@@ -21,12 +22,22 @@ You and the human communicate through revspec's CLI:
 
 The reviewer stays in the revspec TUI for the entire session. You run the watch/reply loop.
 
-## Step 1: Find the Spec File
+## Step 1: Find or Create the File
 
-Detect which spec was recently created or modified in this conversation. Look for:
+**If a file path was provided** (e.g., `/revspec docs/my-spec.md`):
+Use it directly — skip the search below.
+
+**Otherwise**, detect which file was recently created or modified in this conversation:
 - Files written to `docs/superpowers/specs/*.md`
 - The last `.md` file you created or edited
-- If ambiguous, ask the user which file to review
+
+**If the content was written inline** (proposed in conversation output or plan mode, never saved to a file):
+1. Save the content to a `.md` file — use `docs/superpowers/specs/<topic>.md` or a reasonable path in the project
+2. Confirm the file path with the user before proceeding
+
+If ambiguous, ask the user which file to review.
+
+**Resuming a previous review:** Check if a `.review.jsonl` file already exists for the target file (e.g., `spec.review.jsonl`). If it does, the TUI will restore previous threads automatically — let the user know they're resuming where they left off.
 
 ## Step 2: Launch Revspec
 
@@ -42,7 +53,21 @@ echo $TMUX
 tmux split-window -t "$TMUX_PANE" -v "revspec <spec-file>"
 ```
 
-**If no tmux:**
+**If no tmux, but on macOS:** detect the terminal and open a new window:
+
+```bash
+echo $TERM_PROGRAM
+```
+
+| `$TERM_PROGRAM` | Launch command |
+|---|---|
+| `Apple_Terminal` | `osascript -e 'tell application "Terminal" to do script "revspec <spec-file>"'` |
+| `iTerm.app` | `osascript -e 'tell application "iTerm2" to create window with default profile command "revspec <spec-file>"'` |
+| `WezTerm` | `wezterm start -- revspec <spec-file>` |
+| `ghostty` | `ghostty -e revspec <spec-file>` |
+| Other/unknown | Fall back to `osascript` with Terminal.app |
+
+**Otherwise (not macOS):**
 Tell the user: "Please run in another terminal: `revspec <spec-file>`"
 
 ## Step 3: Run the Watch/Reply Loop

package/src/cli/watch.ts

@@ -235,8 +235,8 @@ function processNewEvents(
     return { approved: false, output: "", newOffset: offset };
   }
 
-  // Save new offset
-  atomicWriteFileSync(offsetPath, String(newOffset));
+  // Save new offset (preserve submit_ts if present)
+  atomicWriteFileSync(offsetPath, lastSubmitTs ? `${newOffset}\n${lastSubmitTs}` : String(newOffset));
 
   // Check for approve event
   const hasApprove = events.some((e) => e.type === "approve");

package/src/tui/app.ts

@@ -626,6 +626,11 @@ export async function runTui(
           break;
         }
         case "submit":
+          if (state.threads.length === 0) {
+            setBottomBarMessage(bottomBar, " No threads to submit.");
+            renderer.requestRender();
+            break;
+          }
           unresolvedGate(() => {
             appendEvent(jsonlPath, { type: "submit", author: "reviewer", ts: Date.now() });
 

package/src/tui/ui/theme.ts

@@ -1,8 +1,8 @@
 export const theme = {
   // Surfaces
-  base: "#1e1e2e",
+  base: undefined,
   backgroundPanel: "#313244",
-  backgroundElement: "#45475a",
+  backgroundElement: undefined,
 
   // Text hierarchy
   text: "#cdd6f4",