@ggdna/dna-gg 0.10.0 → 0.11.0

package/README.md

@@ -29,6 +29,7 @@ All skills of this layer are prefixed with `gg-`:
 - `/gg-ticket` — creates a ticket and adds the repos it needs
 - `/gg-commit` — proposes a message and commits through `gg do commit`
 - `/gg-push` — pushes the ticket branches
+- `/gg-review` — writes the blog posts and opens the pull requests
 - `/gg-publish` — releases the ticket
 - `/gg-cleanup` — removes what the ticket left behind
 

package/dna/CLAUDE.md

@@ -7,5 +7,5 @@ comes next:
 @doc/guides/for-ai/ai-dev-guide.md
 
 The steps are also available as skills: `/gg-ticket`, `/gg-commit`,
-`/gg-push`, `/gg-publish`, `/gg-cleanup`. `/gg` lists them and says which
-one comes next.
+`/gg-push`, `/gg-review`, `/gg-publish`, `/gg-cleanup`. `/gg` lists them
+and says which one comes next.

package/dna/_generated.json

@@ -39,7 +39,7 @@
       "ecosystem": null,
       "resolvedVersion": null,
       "via": null,
-      "hash": "0x2437308eb192d742"
+      "hash": "0x0c681b9f487d5439"
     }
   ],
   "claude": {
@@ -59,19 +59,23 @@
     },
     {
       "path": ".claude/skills/gg-publish/SKILL.md",
-      "hash": "0x61626e5e2425d9ab"
+      "hash": "0xcdef2684fcaaac5a"
     },
     {
       "path": ".claude/skills/gg-push/SKILL.md",
       "hash": "0x140e1b8d6cbe222e"
     },
+    {
+      "path": ".claude/skills/gg-review/SKILL.md",
+      "hash": "0x09df48b6f6bf1de6"
+    },
     {
       "path": ".claude/skills/gg-ticket/SKILL.md",
       "hash": "0xe2e320fd71159027"
     },
     {
       "path": ".claude/skills/gg/SKILL.md",
-      "hash": "0x0e643054f49cf6a2"
+      "hash": "0x1eb3897cb31ec13b"
     },
     {
       "path": ".claude/skills/index/SKILL.md",
@@ -87,7 +91,7 @@
     },
     {
       "path": "doc/guides/develop-guide.md",
-      "hash": "0xc31d5f25f496a9d6"
+      "hash": "0x84e26705681de36f"
     },
     {
       "path": "doc/guides/develop-without-ai-guide.md",
@@ -95,7 +99,7 @@
     },
     {
       "path": "doc/guides/for-ai/ai-dev-guide.md",
-      "hash": "0x6b77398ea1658c09"
+      "hash": "0x89583fdaaa73aa60"
     },
     {
       "path": "doc/guides/index-guide.md",

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

@@ -35,7 +35,7 @@ Use the following skills in Claude
 ```bash
 /gg-commit
 /gg-push
-/review
+/gg-review
 /gg-publish
 /gg-cleanup
 ```

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

@@ -173,6 +173,14 @@ gg do push
 
 ## Review
 
+Document the change in every repo first, so the documentation lands in
+the pull requests and is reviewed with the code:
+
+- Run `/blog` in every repo of the ticket that has
+  `doc/guides/blog-guide.md`, the project management repo included
+- Update the index.jsonc and README.md
+- Commit and push again
+
 Let the user confirm that the review phase is started.
 
 ```bash
@@ -186,9 +194,6 @@ Afterwards load the review-light skill and execute it.
 
 ## Publish
 
-- Run `/blog` in every repo of the ticket that has
-  `doc/guides/blog-guide.md`, the project management repo included
-- Update the index.jsonc and README.md
 - Check `mergeMessage` and `versionIncrement` in `.gg/publish_config.json`
   of each repo — `gg do publish` offers them as defaults
 - If the ticket was only planned, publish the project management repo only

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

@@ -12,6 +12,8 @@ below, in this order — it is the order of a ticket's life.
 - `/gg-commit` — proposes a message and commits through `gg do commit`,
   or `gg one do commit` inside a single repo
 - `/gg-push` — pushes the ticket branches with `gg do push`
+- `/gg-review` — writes the blog posts, opens the pull requests with
+  `gg do review` and reviews the changes
 - `/gg-publish` — prepares the release and hands `gg do publish` over to
   the user
 - `/gg-cleanup` — removes what the published ticket left behind
@@ -27,12 +29,10 @@ Read the state of the current ticket and name the next step:
 - No ticket folder yet → `/gg-ticket`
 - Uncommitted work → `/gg-commit`
 - Committed, not pushed → `/gg-push`
-- Pushed and the pull requests are green → `/gg-publish`
+- Pushed, no pull requests yet → `/gg-review`
+- Reviewed and the pull requests are green → `/gg-publish`
 - Published → `/gg-cleanup`
 
-The review between push and publish is `gg do review` plus the
-`/review-light` skill, not a `gg-` skill of this layer.
-
 ## Important
 
 - Only list the skills, never run one of them unasked.

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

@@ -12,6 +12,8 @@ creates and pushes the version tags. It is interactive — the user runs it.
 
 - Every repo of the ticket is committed and pushed.
 - The pull requests created by `gg do review` are green.
+- Every repo with `doc/guides/blog-guide.md` holds the post of this ticket
+  in `doc/blog/<yyyy>`. If one is missing, go back to `/gg-review`.
 
 ## 2. Configure the publish
 

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

@@ -0,0 +1,47 @@
+---
+name: gg-review
+description: Writes the blog posts of the ticket, opens the pull requests with `gg do review` and reviews the changes. Use when the user says "/gg-review" or asks to review the current ticket.
+---
+
+# Review
+
+Each repo documents its change first, so the documentation lands in the
+pull requests and is reviewed with the code. Every commit after
+`gg do review` voids the review.
+
+## 1. Document the change in every repo
+
+Look for `doc/guides/blog-guide.md` in every repo of the ticket, the
+project management repo included. It comes from the `dna_blog` layer.
+
+- Run `/blog` in each repo that has it; skip the others
+- `/blog` stops by itself when the post already exists
+
+Update `index.jsonc` and `README.md` of each repo the ticket changed.
+
+Let the user review the changes, then run `/gg-commit` and `/gg-push`.
+
+## 2. Open the pull requests
+
+Let the user confirm that the review phase is started. From the ticket
+folder:
+
+```bash
+gg do review
+```
+
+gg creates a pull request for each repo and prints the URLs to the
+terminal.
+
+## 3. Review the changes
+
+Load the `/review-light` skill and execute it.
+
+A fix goes through `/gg-commit` and `/gg-push`, then run `gg do review`
+again. Update the blog post of the repo when the fix changes what it
+describes.
+
+## Important
+
+- Never write a blog post in a repo without `doc/guides/blog-guide.md`.
+- Never start `gg do review` without the user's confirmation.

package/package.json

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