@ggdna/dna-gg 1.5.0 → 1.6.0

package/dna/_generated.json

@@ -39,7 +39,7 @@
       "ecosystem": null,
       "resolvedVersion": null,
       "via": null,
-      "hash": "0xff6654f75712aad8"
+      "hash": "0xf809b20d01f13cce"
     }
   ],
   "claude": {
@@ -67,7 +67,7 @@
     },
     {
       "path": ".claude/skills/gg-cleanup/SKILL.md",
-      "hash": "0x4a6903a51168486a"
+      "hash": "0x634921912309c933"
     },
     {
       "path": ".claude/skills/gg-commit/SKILL.md",
@@ -75,7 +75,7 @@
     },
     {
       "path": ".claude/skills/gg-publish/SKILL.md",
-      "hash": "0x806b4c1fd5f6f654"
+      "hash": "0x501ac99a5d586b58"
     },
     {
       "path": ".claude/skills/gg-push/SKILL.md",
@@ -87,7 +87,7 @@
     },
     {
       "path": ".claude/skills/gg-ticket/SKILL.md",
-      "hash": "0x8f9f5eb3d5567659"
+      "hash": "0xa44f6e5ad54a6d0b"
     },
     {
       "path": ".claude/skills/gg/SKILL.md",
@@ -111,11 +111,11 @@
     },
     {
       "path": "doc/guides/develop-without-ai-guide.md",
-      "hash": "0xe74449f72357f23c"
+      "hash": "0x88551202636c10c0"
     },
     {
       "path": "doc/guides/for-ai/ai-dev-guide.md",
-      "hash": "0xa7bc4ac78f9387d6"
+      "hash": "0x66658aeee6353ced"
     },
     {
       "path": "doc/guides/index-guide.md",

package/dna/doc/guides/develop-without-ai-guide.md

@@ -22,12 +22,15 @@ If you have not done that yet:
 cd ~/dev/
 ```
 
-## Add tickets
+## Add repos to the ticket
 
 ```bash
 gg do add repo1 repo2
 ```
 
+Name all repos in one call: every call refreshes the ocean and builds
+the dependency graph again.
+
 ## Open the workspace in Vscode
 
 ```bash
@@ -58,6 +61,12 @@ gg do review
 
 ## Publish
 
+Publish from the workspace root and name the ticket with `-i`:
+
 ```bash
-gg do publish
+cd ~/dev/
+gg do publish -i <ticket>
 ```
+
+At the end gg moves the ticket folder to the trash. On Windows this fails
+while a terminal sits in the ticket folder ("used by another process").

package/dna/doc/guides/for-ai/ai-dev-guide.md

@@ -104,6 +104,12 @@ After the user's confirmation, add the repos to the ticket:
 gg do add repo1 repo2
 ```
 
+Name all code repos in this one call, never one `gg do add` per repo —
+not even for repos you find one after the other. Every call refreshes
+the ocean and builds the dependency graph again, and a ticket repo that
+depends on several new repos is resolved again for each call. The same
+goes for repos you find later, while implementing: add them together.
+
 ## Keep every repo in its scope
 
 Every repo covers one fixed scope: the `summary` and `domain` of its
@@ -121,7 +127,8 @@ as code does not fit the repo it is in or is about to land in:
   covers: propose creating one with `gg do create repo`, which adds it to
   the ticket
 - **Add an existing repo** — the code belongs to a repo in .ocean that is
-  not part of the ticket yet: propose adding it with `gg do add`
+  not part of the ticket yet: propose adding it with `gg do add`,
+  several repos in one call
 - **Move code** — existing code, or code you just wrote, belongs to another
   repo: propose moving it there
 
@@ -348,11 +355,17 @@ Afterwards load the review-light skill and execute it.
   of each repo — `gg do publish` offers them as defaults
 - If the ticket was only planned, publish the project management repo only
 
-Ask the user to run the following command **manually**:
+Ask the user to run the following command **manually** from the workspace
+root, not from the ticket folder:
 
 ```bash
-gg do publish
+cd ~/dev/ # workspace root
+gg do publish -i fix_login_crash
 ```
 
+At the end gg moves the ticket folder to the trash. Windows refuses to move
+a folder a terminal sits in ("used by another process", errno 32), so the
+terminal must stay outside the ticket — `-i` names the ticket instead.
+
 gg triggers the pull request merge and publishes the changes to the
 registry. Finally the version tag is created and pushed.

package/dna/dot-claude/skills/gg-cleanup/SKILL.md

@@ -52,10 +52,13 @@ git merge --abort
 ## 3. Remove the ticket folder
 
 ```bash
-cd ~/dev/ # workspace
-rm -rf tickets/DnaJiraPrefix-145
+cd ~/dev/ # workspace root
+rm -rf fix_login_crash
 ```
 
+On Windows, no terminal and no VS Code window may sit in the ticket folder —
+otherwise the deletion fails with "used by another process".
+
 ## 4. Update the workspace
 
 Pull `main` in the repos the ticket touched, so the workspace matches the

package/dna/dot-claude/skills/gg-publish/SKILL.md

@@ -30,12 +30,18 @@ it is interactive. Check that `CHANGELOG.md` reads well.
 
 ## 3. Let the user publish
 
-Ask the user to run this **manually** from the ticket folder:
+Ask the user to run this **manually** from the workspace root, not from the
+ticket folder. Fill in the real workspace root and ticket folder:
 
 ```bash
-gg do publish
+cd ~/dev/ # workspace root
+gg do publish -i fix_login_crash
 ```
 
+At the end gg moves the ticket folder to the trash. Windows refuses to move
+a folder a terminal sits in ("used by another process", errno 32), so the
+terminal must stay outside the ticket — `-i` names the ticket instead.
+
 It asks whether the ticket and the remote feature branches may be deleted.
 If the user declines, run `/gg-cleanup` afterwards.
 

package/dna/dot-claude/skills/gg-ticket/SKILL.md

@@ -90,6 +90,12 @@ After the confirmation:
 gg do add repo1 repo2
 ```
 
+Name all code repos in this one call, never one `gg do add` per repo —
+not even for repos you find one after the other. Every call refreshes
+the ocean and builds the dependency graph again, and a ticket repo that
+depends on several new repos is resolved again for each call. The same
+goes for repos you find later, while implementing: add them together.
+
 ## 5. Open the workspace only on request
 
 Do not open VS Code on your own — many tickets need no editor. Tell the
@@ -136,7 +142,8 @@ not fit the repo it is in or is about to land in:
 
 - **Split a repo** that has grown a second scope into two repos
 - **Add a new repo** with `gg do create repo` for a domain no repo covers
-- **Add an existing repo** with `gg do add` when the code belongs there
+- **Add an existing repo** with `gg do add` when the code belongs there;
+  several repos in one call
 - **Move code**, existing or just written, into the repo whose scope it fits
 
 Name the code, the repo it is in, the repo it should go to and why. Let the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ggdna/dna-gg",
-  "version": "1.5.0",
+  "version": "1.6.0",
   "description": "DNA layer: gg CLI workflow guides, repo setup scripts and CI check",
   "keywords": [
     "dna",