pi-graphite 0.3.3 → 0.3.5

package/README.md

@@ -8,9 +8,12 @@ graphite_status → (graphite_setup if needed) → graphite_sync → graphite_na
        → graphite_change → graphite_submit_stack (dry-run) → graphite_submit_stack (apply)
 ```
 
-The extension wraps `gt` only. It deliberately does **not** call `gh`, edit PR
-titles/bodies, fetch review comments, or perform stack surgery
-(split/fold/move/squash). Use the `gt` or `gh` CLI directly for those.
+The extension wraps `gt` only. It deliberately does **not** call `gh`, edit
+PR titles/bodies, fetch review comments, or perform stack surgery (split /
+fold / move / squash / reorder). For those flows, run the underlying `gt`
+or `gh` command yourself in your own terminal; the agent should not invoke
+them from bash, as their defaults open interactive prompts, hunk pickers,
+or editors that will hang non-interactive sessions.
 
 ## Requirements
 
@@ -64,7 +67,7 @@ graphite_submit_stack apply=true confirmRemote=true
 Conflict path:
 
 ```text
-# resolve files, git add them
+# resolve files, then: git add -- <paths>
 graphite_recover action=continue
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-graphite",
-  "version": "0.3.3",
+  "version": "0.3.5",
   "description": "Opinionated pi tools + skill for stacked PR workflows with the Graphite (gt) CLI.",
   "keywords": [
     "pi",

package/skills/graphite/SKILL.md

@@ -22,8 +22,9 @@ Use this skill whenever the user wants to:
 
 Do not use it for:
 
-- editing PR titles / bodies / labels / reviewers metadata (use `gh` directly)
-- reading PR review comments or CI status (use `gh` directly)
+- editing PR titles / bodies / labels / reviewers metadata — prefer a
+  dedicated `gh` tool/extension; see the `gh` rule below
+- reading PR review comments or CI status — same
 - rewriting history beyond create/amend (split / fold / move / squash /
   reorder). The extension does not expose stack surgery. Do not invoke
   `gt` directly from bash for these — those subcommands prompt
@@ -68,7 +69,7 @@ graphite_submit_stack apply=true    (push, with confirmRemote=true)
 When a `gt` command halts on conflict:
 
 ```
-resolve files in editor → git add <files> → graphite_recover action="continue"
+resolve files in editor → git add -- <paths> → graphite_recover action="continue"
 ```
 
 Never run `git rebase --continue` after a Graphite-initiated rebase; use