patchcord 0.5.103 → 0.5.104
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.
package/package.json
CHANGED
|
@@ -1,14 +1,15 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: patchcord-inbox
|
|
3
3
|
description: Read Patchcord inbox and reply to messages
|
|
4
|
-
type: flow
|
|
5
4
|
---
|
|
6
5
|
|
|
7
|
-
|
|
6
|
+
Run this with `/skill:patchcord-inbox`. (Kimi Code has no `/flow:` — `/skill:` injects this as a prompt and you act on it.)
|
|
8
7
|
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
8
|
+
Call the `inbox` MCP tool now. In its response, the first header line is YOUR own identity (the recipient); the real sender of each message is on a `From X` line — never confuse the two.
|
|
9
|
+
|
|
10
|
+
For each pending message, classify it and act:
|
|
11
|
+
- **ACK** — short signals like thanks, noted, works, great, ok, 👍 with no task → close it silently: `reply(message_id, resolve=true)` with NO content. Never send a text reply to an ack (it creates infinite ack chains).
|
|
12
|
+
- **BLOCKED** — you cannot do the work right now (busy, missing credentials, ambiguous target) → `reply(message_id, "<reason>", defer=true)` so it stays in your inbox as a reminder. Never silently skip a message.
|
|
13
|
+
- **ACTIONABLE** — do the work the message asks for FIRST (edit the file, run the command, write the code), THEN `reply(message_id, "<concrete summary of what you did, with file paths and line numbers>")`. Never reply "will do" / "understood" before doing the work.
|
|
14
|
+
|
|
15
|
+
After handling every message, re-arm the background listener: use the Shell tool to run `patchcord subscribe --kimi 5` with run_in_background=true, timeout=86400, description="Patchcord listener".
|
|
@@ -1,14 +1,13 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: patchcord-subscribe
|
|
3
3
|
description: Start the Patchcord background polling listener
|
|
4
|
-
type: flow
|
|
5
4
|
---
|
|
6
5
|
|
|
7
|
-
|
|
6
|
+
Run this with `/skill:patchcord-subscribe`. (Kimi Code has no `/flow:` — `/skill:` injects this as a prompt and you act on it.)
|
|
8
7
|
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
8
|
+
First, call the `inbox` MCP tool and DRAIN every pending message before starting the listener (the listener exits immediately if messages are already waiting). In the inbox response, the first header line is YOUR identity (recipient); the real sender is on each `From X` line. For each message:
|
|
9
|
+
- **ACK** (thanks, noted, works, ok, 👍) → `reply(message_id, resolve=true)`, no content.
|
|
10
|
+
- **BLOCKED** → `reply(message_id, "<reason>", defer=true)`.
|
|
11
|
+
- **ACTIONABLE** → do the work first, then `reply(message_id, "<what you did>")`.
|
|
12
|
+
|
|
13
|
+
Then start the background listener: use the Shell tool to run `patchcord subscribe --kimi 5` with run_in_background=true, timeout=86400, description="Patchcord listener". Tell the user in one sentence: Patchcord listener active.
|
|
@@ -1,17 +1,15 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: patchcord-wait
|
|
3
3
|
description: Wait for one incoming Patchcord message
|
|
4
|
-
type: flow
|
|
5
4
|
---
|
|
6
5
|
|
|
7
|
-
|
|
6
|
+
Run this with `/skill:patchcord-wait`. (Kimi Code has no `/flow:` — `/skill:` injects this as a prompt and you act on it.)
|
|
8
7
|
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
```
|
|
8
|
+
Call the `wait_for_message` MCP tool now to block until a message arrives or ~5 minutes elapse.
|
|
9
|
+
|
|
10
|
+
When a message arrives, classify it and act:
|
|
11
|
+
- **ACK** (thanks, noted, works, ok, 👍, no task) → `reply(message_id, resolve=true)` with NO content. Never text-reply an ack.
|
|
12
|
+
- **BLOCKED** (cannot do the work right now) → `reply(message_id, "<reason>", defer=true)`.
|
|
13
|
+
- **ACTIONABLE** → do the work FIRST, then `reply(message_id, "<concrete summary of what you did>")`.
|
|
14
|
+
|
|
15
|
+
Then re-arm the background listener: use the Shell tool to run `patchcord subscribe --kimi 5` with run_in_background=true, timeout=86400, description="Patchcord listener".
|