shapeup-cli 0.11.2 → 0.12.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bcea431afcfe958db1055f75a15957a2b3e69320ad4c67045dd305ffd0c88c2a
-  data.tar.gz: 4f5109b6bfe1144db66413482e300cffa542ad357dbcbb8cec034330ef8e7d5d
+  metadata.gz: 6447a0d1f215f3783af0c866c6fb17d8cc1e68730255d1e8e1702ce622fd514a
+  data.tar.gz: 3cf15b4881fd01dec7fae24260ec46979c2292b518cc8bca7acc775b6be966a0
 SHA512:
-  metadata.gz: 1cd8502dc208393d11f2f0755caf331389bf1326cf898bcb20995889a8a93c837a580bbada74a92d5c3caec8465009c64000b89da0f98c304b5bc7e53bc02ead
-  data.tar.gz: 37a268a7426bfa61112d220e374ab20b3a8a0377e95f7e10c162f297396360b377721f3a13862c44e442834a834083db03717fc375e026ee1e1bebea0bec36b8
+  metadata.gz: 778fe7a8e86453e69ca8c79cfce6020b287f5304356a2cee23555d4c215eb88f6d6257bb43ca63cf302c42daf30f792243f7ba6d5a4420b7c6008ae2a9d05118
+  data.tar.gz: 4fd556546a7bc427fa488c43500b4f48a8c86cff85512ea1d9363af6fc2fa892c091f67b032a803a0d04e9dc84522cc43ba67507ea2766cae048157482116b62

data/lib/shapeup_cli/commands/inbox.rb

@@ -10,11 +10,13 @@ module ShapeupCli
           short: "For agents: requests waiting on issues, and marking them done",
           subcommands: [
             { name: "list", short: "List requests waiting for this agent", path: "shapeup inbox" },
+            { name: "start", short: "Show on the issue that you're working on a request, with a short status", path: 'shapeup inbox start <id> [--status "..."]' },
             { name: "done", short: "Take a handled request out of the inbox", path: "shapeup inbox done <id>" }
           ],
           examples: [
             "shapeup inbox",
             "shapeup inbox --json",
+            'shapeup inbox start 812 --status "Taking screenshots"',
             "shapeup inbox done 812"
           ]
         }
@@ -22,6 +24,7 @@ module ShapeupCli
 
       def execute
         case positional_arg(0)
+        when "start" then start
         when "done" then done
         else list
         end
@@ -40,6 +43,14 @@ module ShapeupCli
             ]
         end
 
+        def start
+          status = extract_option("--status")
+          id = positional_arg(1) || abort('Usage: shapeup inbox start <id> [--status "..."]')
+          result = call_tool("start_inbox_item", **{ item: id.to_s, status: status }.compact)
+
+          render result, summary: "Working on request #{id}"
+        end
+
         def done
           id = positional_arg(1) || abort("Usage: shapeup inbox done <id>")
           result = call_tool("complete_inbox_item", item: id.to_s)

data/lib/shapeup_cli/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module ShapeupCli
-  VERSION = "0.11.2"
+  VERSION = "0.12.0"
 end

data/skills/shapeup-connect/SKILL.md

@@ -133,18 +133,17 @@ A `request` line carries `id`, `reason` (mentioned, replied, assigned or watchin
 
 1. **Acknowledge it.** When `request.comment_id` is set, react to it:
    `shapeup --profile <profile> comments react <comment_id> 👀`
-   When it is null (the agent was assigned, or mentioned in the issue itself), there is nothing to
-   react to, so post a short comment instead and reply under it later:
-   `shapeup --profile <profile> comments add --issue <issue_id> "On it. I'll reply here when it's done." --json`
-   Set `reply_to.comment_id` to the new comment's `id` before handing off.
+   Post no comment to acknowledge it: the issue shows the request's state by itself.
 2. **Show it's in progress.** List the columns with `shapeup --profile <profile> issues columns --json`.
    If one reads like "In progress" or "Doing", move the issue there with
    `shapeup --profile <profile> issues move <issue_id> --column "<name>"`. If there is none, skip this.
 3. **Hand it off, one at a time.** Workers share this folder and its git checkout, so never run two
-   at once. If no worker is running, start one background subagent with the request line and the
-   worker brief below, and tell the user in one line, for example "@bond picked up #42 from
+   at once. If no worker is running, show it's under way with
+   `shapeup --profile <profile> inbox start <id> --status "Reading the issue"` (a comment from the
+   agent clears the status, so don't comment before the reply), then start one background subagent with
+   the request line and the worker brief below, and tell the user in one line, for example "@bond picked up #42 from
    @miles". If one is still running, hold the request: tell the user it's queued behind the current
-   one, and start it when that worker finishes, oldest first.
+   one, and when that worker finishes, run `inbox start` for the oldest held request and start it.
 4. **Keep listening.** Once every line of the connector's output is handled, start it again as above.
 
 ## Worker brief
@@ -165,7 +164,11 @@ Give the subagent this, filled in:
 > 4. If the ask is unclear or you are blocked, ask on the issue rather than guess. If the issue is
 >    clearly about a different product or codebase than this repository, say so on the issue and
 >    stop.
-> 5. If the work changes anything people see, compare it the way a careful reviewer would:
+> 5. Keep the issue showing what you're doing: at each step (writing the change, running the
+>    tests, taking screenshots), and at least every 20 minutes, run
+>    `shapeup --profile <profile> inbox start <id> --status "<a few words>"`. After 30 minutes
+>    without one, the issue says you stopped responding.
+> 6. If the work changes anything people see, compare it the way a careful reviewer would:
 >    - From your diff, list the screens and states it touches, including the ones it could break.
 >    - Run the main branch beside yours: check main out into a git worktree outside this
 >      repository and start it on a second port, so both are up at once. How to start and sign in
@@ -174,7 +177,7 @@ Give the subagent this, filled in:
 >      the same content, plus a phone width and dark mode where they matter. Save PNGs outside the
 >      repository, named for what they show.
 >    - Stop the second server and remove the worktree when you're done.
-> 6. Reply once, under the comment that asked:
+> 7. Reply once, under the comment that asked:
 >    `shapeup --profile <profile> comments add --issue <issue.id> --parent <reply_to.comment_id> "<reply>"`
 >    (leave out `--parent` when `reply_to.comment_id` is null). Start with `@<requester.name>`,
 >    then say what changed, the branch and commit, and how you checked it. Keep it plain.
@@ -195,13 +198,12 @@ Give the subagent this, filled in:
 >    people who can't see it, so say what it shows; the quoted word is its caption. End with a
 >    `## Worth a look` section for anything that seems off, and mention whoever the requester asked
 >    you to hand over to.
-> 7. Then take it out of the inbox: `shapeup --profile <profile> inbox done <id>`.
-> 8. Report back in one line.
+> 8. Then take it out of the inbox: `shapeup --profile <profile> inbox done <id>`.
+> 9. Report back in one line.
 
 ## Rules
 
-- One reply per request, plus the "On it" comment when there was nothing to react to. Never treat
-  your own comments as requests.
+- One reply per request. Never treat your own comments as requests.
 - Never run two workers at once in this folder.
 - Never print or repeat the agent's token.
 - Never install, upgrade or replace the ShapeUp CLI.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: shapeup-cli
 version: !ruby/object:Gem::Version
-  version: 0.11.2
+  version: 0.12.0
 platform: ruby
 authors:
 - ShapeUp