kankaku-claude 0.2.0 → 0.2.1

package/CHANGELOG.md

@@ -8,6 +8,9 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ### Added
 
+- `/kankaku:sync-status` and `/kankaku:sync-all` slash commands for local
+  sync state inspection and full hub sync, respectively.
+
 - Phase 1: per-prompt work records from Claude Code hooks. Writes one
   `WorkRecord` per user prompt to `<KANKAKU_DIR>/worklog.jsonl`, in the same
   schema the kankaku pi extension writes, so kankaku's existing

package/README.md

@@ -85,8 +85,11 @@ anything behind in whatever project happens to be open.
   and the last cost the statusline reported (wraps `node src/cli.ts status`).
 - `/kankaku:setup` — prints the `statusLine` snippet described above (wraps
   `node src/cli.ts setup`).
-- `/kankaku:sync` — manually syncs local work records to the hub (wraps
-  `node src/cli.ts sync`; the slash command does not forward arguments).
+- `/kankaku:sync` — manually syncs recent local work records to the hub
+  (wraps `node src/cli.ts sync`; the slash command does not forward arguments).
+- `/kankaku:sync-status` — inspects local pending counts and sync state
+  (wraps `node src/cli.ts sync status`; no hub request or credentials required).
+- `/kankaku:sync-all` — requests a full sync (wraps `node src/cli.ts sync all`).
 
 The report, status, and setup subcommands are also available directly via
 `node src/cli.ts <report|status|setup>`; `report` accepts `--days N` and
@@ -96,9 +99,10 @@ defaults to the last 7 days.
 
 Configure hub credentials with `KANKAKU_PB_URL`, `KANKAKU_PB_EMAIL`, and
 `KANKAKU_PB_PASSWORD`, or use `~/.kankaku/credentials.json` (the shared
-kankaku hub credential file). Then run `/kankaku:sync` or
-`node src/cli.ts sync` in the project whose worklog you want to upload.
-For options not forwarded by the slash command, use the CLI directly:
+kankaku hub credential file). Then run `/kankaku:sync` for recent records or
+`/kankaku:sync-all` for a full sync in the project whose worklog you want to
+upload. Use `/kankaku:sync-status` to inspect local sync state without a hub
+request or credentials. The same operations are available directly via CLI:
 
 | Command | Purpose |
 |---------|---------|
@@ -181,9 +185,9 @@ also runs for the current session's own leftover state at `SessionEnd`.
   document a link between a `SubagentStart`/`SubagentStop` pair and the
   `tool_use_id` that launched it, so kankaku-claude cannot join them; the
   subagent's own time is not separately measured here.
-- **Hub sync is best-effort.** Use `/kankaku:sync` or the direct CLI to retry
-  failures or request a full sync. Prompts are omitted from uploads unless
-  `KANKAKU_SYNC_PROMPT` is `truncated` or `full`.
+- **Hub sync is best-effort.** Use `/kankaku:sync` to retry recent records or
+  `/kankaku:sync-all` to request a full sync. Prompts are omitted from uploads
+  unless `KANKAKU_SYNC_PROMPT` is `truncated` or `full`.
 
 See [kankaku.io](https://kankaku.io) for the pi extension this plugin shares
 its worklog format with.

package/commands/sync-all.md

@@ -0,0 +1,9 @@
+---
+description: Request a full sync of local kankaku work records to the hub
+allowed-tools: Bash(node:*)
+---
+
+Run the kankaku CLI sync all command and show its output to the user verbatim,
+inside a code block, with no summarizing or reformatting:
+
+!node "${CLAUDE_PLUGIN_ROOT}/src/cli.ts" sync all

package/commands/sync-status.md

@@ -0,0 +1,9 @@
+---
+description: Show local kankaku hub sync status
+allowed-tools: Bash(node:*)
+---
+
+Run the kankaku CLI sync status command and show its output to the user verbatim,
+inside a code block, with no summarizing or reformatting:
+
+!node "${CLAUDE_PLUGIN_ROOT}/src/cli.ts" sync status

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kankaku-claude",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Claude Code plugin that records how long the agent works on each user prompt, in kankaku's worklog format.",
   "type": "module",
   "files": [