@kurrent/kcap 0.8.17 → 0.8.18

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,5 +1,5 @@
1
1
  {
2
2
  "name": "kcap",
3
- "version": "0.8.17",
3
+ "version": "0.8.18",
4
4
  "description": "Records and visualizes Claude Code sessions via kcap CLI hooks"
5
5
  }
package/kcap/.mcp.json CHANGED
@@ -14,7 +14,7 @@
14
14
  "command": "kcap",
15
15
  "args": ["mcp", "flows"],
16
16
  "cwd": "${CLAUDE_PROJECT_DIR}",
17
- "description": "Structured AI review flows — start_review_flow, submit_review_round, get_review_flow_status, close_review_flow. Launches a hosted reviewer agent through your daemon; requires `kcap login` and a running daemon with this repo checked out (the tools are inert otherwise)."
17
+ "description": "Structured AI review flows — start_review_flow, submit_review_round, get_review_flow_status, close_review_flow. Launches a SEPARATE hosted reviewer agent through your daemon and iterates to sign-off; requires `kcap login` and a running daemon with this repo checked out (the tools are inert otherwise). Use only when the user explicitly asks for a review flow / to submit for review — for an ordinary 'review my PR' or 'code review' request, review directly and do not call these tools."
18
18
  }
19
19
  }
20
20
  }
@@ -1,20 +1,32 @@
1
1
  ---
2
2
  name: review-flows
3
3
  description: >-
4
- This skill should be used when the user asks to "review this spec",
5
- "review this design", "review my PR", "code review", "get this reviewed",
6
- "re-review", "start a review flow", "review flow", "submit for review",
7
- or wants structured iterative review with findings and sign-off.
4
+ This skill should be used ONLY when the user explicitly asks to run a
5
+ structured review *flow* e.g. "start a review flow", "submit this for
6
+ review", "re-review after I address findings", or wants an iterative review
7
+ loop run by a separate reviewer that continues until sign-off. Do NOT use
8
+ this skill (and do NOT call the flows MCP tools) for an ordinary review
9
+ request such as "review my PR", "review this diff/spec/design", or "code
10
+ review" where the user just wants you to review it yourself — perform that
11
+ review directly instead.
8
12
  ---
9
13
 
10
14
  # Review Flows
11
15
 
12
- Use `kcap mcp flows` MCP tools to run structured review loops for specs/designs and PR/code work. A review flow submits your work to a reviewer, collects findings, lets you address them, and keeps iterating until the reviewer returns `NO FINDINGS`.
16
+ Use the `kcap mcp flows` MCP tools (`start_review_flow`, `submit_review_round`, …) to run a structured review **flow**: your work is submitted to a **separate, hosted reviewer** agent, which returns findings; you address them and keep iterating until the reviewer returns `NO FINDINGS`. This is a deliberate, heavier workflow — use it only when the user explicitly opts into it.
13
17
 
14
- ## When to use
18
+ ## When NOT to use this skill / these tools
15
19
 
16
- - Reviewing a spec or design document use `kind: "spec-review"`
17
- - Reviewing code changes or a pull request → use `kind: "code-review"`
20
+ These tools do **not** perform a review they hand the work off to a separate hosted reviewer. If the user simply asked *you* to review something in a normal session — e.g. "review my PR", "review this diff", "code review this", "look over this spec" — just perform the review yourself and report your findings directly. Do **NOT** call `start_review_flow` / `submit_review_round` for an ordinary review request; that would spin up a hosted reviewer the user did not ask for.
21
+
22
+ Only start a flow when the user explicitly asks for a review *flow* — e.g. "start a review flow", "submit this for review", "get an independent review", or "re-review after I address the findings".
23
+
24
+ ## Choosing the flow kind
25
+
26
+ Once the user has explicitly opted into a flow (see above), pick the `kind`:
27
+
28
+ - Spec or design document → `kind: "spec-review"`
29
+ - Code changes or a pull request → `kind: "code-review"`
18
30
 
19
31
  ## If the flows MCP tools are not loaded
20
32
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kurrent/kcap",
3
- "version": "0.8.17",
3
+ "version": "0.8.18",
4
4
  "description": "CLI companion for Kurrent Capacitor — records and visualizes Claude Code sessions",
5
5
  "license": "SEE LICENSE IN LICENSE.md",
6
6
  "repository": {
@@ -14,12 +14,12 @@
14
14
  "postinstall": "node bin/postinstall.js"
15
15
  },
16
16
  "optionalDependencies": {
17
- "@kurrent/kcap-darwin-arm64": "0.8.17",
18
- "@kurrent/kcap-linux-x64": "0.8.17",
19
- "@kurrent/kcap-linux-arm64": "0.8.17",
20
- "@kurrent/kcap-linux-musl-x64": "0.8.17",
21
- "@kurrent/kcap-linux-musl-arm64": "0.8.17",
22
- "@kurrent/kcap-win-x64": "0.8.17"
17
+ "@kurrent/kcap-darwin-arm64": "0.8.18",
18
+ "@kurrent/kcap-linux-x64": "0.8.18",
19
+ "@kurrent/kcap-linux-arm64": "0.8.18",
20
+ "@kurrent/kcap-linux-musl-x64": "0.8.18",
21
+ "@kurrent/kcap-linux-musl-arm64": "0.8.18",
22
+ "@kurrent/kcap-win-x64": "0.8.18"
23
23
  },
24
24
  "files": [
25
25
  "bin/",