@ggdna/dna-gg 0.9.0 → 0.11.0

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/README.md CHANGED
@@ -29,6 +29,7 @@ All skills of this layer are prefixed with `gg-`:
29
29
  - `/gg-ticket` — creates a ticket and adds the repos it needs
30
30
  - `/gg-commit` — proposes a message and commits through `gg do commit`
31
31
  - `/gg-push` — pushes the ticket branches
32
+ - `/gg-review` — writes the blog posts and opens the pull requests
32
33
  - `/gg-publish` — releases the ticket
33
34
  - `/gg-cleanup` — removes what the ticket left behind
34
35
 
package/dna/CLAUDE.md CHANGED
@@ -7,5 +7,5 @@ comes next:
7
7
  @doc/guides/for-ai/ai-dev-guide.md
8
8
 
9
9
  The steps are also available as skills: `/gg-ticket`, `/gg-commit`,
10
- `/gg-push`, `/gg-publish`, `/gg-cleanup`. `/gg` lists them and says which
11
- one comes next.
10
+ `/gg-push`, `/gg-review`, `/gg-publish`, `/gg-cleanup`. `/gg` lists them
11
+ and says which one comes next.
@@ -39,7 +39,7 @@
39
39
  "ecosystem": null,
40
40
  "resolvedVersion": null,
41
41
  "via": null,
42
- "hash": "0x2583c9e1629c0937"
42
+ "hash": "0x0c681b9f487d5439"
43
43
  }
44
44
  ],
45
45
  "claude": {
@@ -59,19 +59,23 @@
59
59
  },
60
60
  {
61
61
  "path": ".claude/skills/gg-publish/SKILL.md",
62
- "hash": "0x61626e5e2425d9ab"
62
+ "hash": "0xcdef2684fcaaac5a"
63
63
  },
64
64
  {
65
65
  "path": ".claude/skills/gg-push/SKILL.md",
66
66
  "hash": "0x140e1b8d6cbe222e"
67
67
  },
68
+ {
69
+ "path": ".claude/skills/gg-review/SKILL.md",
70
+ "hash": "0x09df48b6f6bf1de6"
71
+ },
68
72
  {
69
73
  "path": ".claude/skills/gg-ticket/SKILL.md",
70
74
  "hash": "0xe2e320fd71159027"
71
75
  },
72
76
  {
73
77
  "path": ".claude/skills/gg/SKILL.md",
74
- "hash": "0x0e643054f49cf6a2"
78
+ "hash": "0x1eb3897cb31ec13b"
75
79
  },
76
80
  {
77
81
  "path": ".claude/skills/index/SKILL.md",
@@ -87,7 +91,7 @@
87
91
  },
88
92
  {
89
93
  "path": "doc/guides/develop-guide.md",
90
- "hash": "0xc31d5f25f496a9d6"
94
+ "hash": "0x84e26705681de36f"
91
95
  },
92
96
  {
93
97
  "path": "doc/guides/develop-without-ai-guide.md",
@@ -95,7 +99,7 @@
95
99
  },
96
100
  {
97
101
  "path": "doc/guides/for-ai/ai-dev-guide.md",
98
- "hash": "0x84e0ee24efbbe12f"
102
+ "hash": "0x89583fdaaa73aa60"
99
103
  },
100
104
  {
101
105
  "path": "doc/guides/index-guide.md",
@@ -35,7 +35,7 @@ Use the following skills in Claude
35
35
  ```bash
36
36
  /gg-commit
37
37
  /gg-push
38
- /review
38
+ /gg-review
39
39
  /gg-publish
40
40
  /gg-cleanup
41
41
  ```
@@ -173,6 +173,14 @@ gg do push
173
173
 
174
174
  ## Review
175
175
 
176
+ Document the change in every repo first, so the documentation lands in
177
+ the pull requests and is reviewed with the code:
178
+
179
+ - Run `/blog` in every repo of the ticket that has
180
+ `doc/guides/blog-guide.md`, the project management repo included
181
+ - Update the index.jsonc and README.md
182
+ - Commit and push again
183
+
176
184
  Let the user confirm that the review phase is started.
177
185
 
178
186
  ```bash
@@ -186,8 +194,6 @@ Afterwards load the review-light skill and execute it.
186
194
 
187
195
  ## Publish
188
196
 
189
- - Create a blog post for the current ticket
190
- - Update the index.jsonc and README.md
191
197
  - Check `mergeMessage` and `versionIncrement` in `.gg/publish_config.json`
192
198
  of each repo — `gg do publish` offers them as defaults
193
199
  - If the ticket was only planned, publish the project management repo only
@@ -12,6 +12,8 @@ below, in this order — it is the order of a ticket's life.
12
12
  - `/gg-commit` — proposes a message and commits through `gg do commit`,
13
13
  or `gg one do commit` inside a single repo
14
14
  - `/gg-push` — pushes the ticket branches with `gg do push`
15
+ - `/gg-review` — writes the blog posts, opens the pull requests with
16
+ `gg do review` and reviews the changes
15
17
  - `/gg-publish` — prepares the release and hands `gg do publish` over to
16
18
  the user
17
19
  - `/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:
27
29
  - No ticket folder yet → `/gg-ticket`
28
30
  - Uncommitted work → `/gg-commit`
29
31
  - Committed, not pushed → `/gg-push`
30
- - Pushed and the pull requests are green → `/gg-publish`
32
+ - Pushed, no pull requests yet → `/gg-review`
33
+ - Reviewed and the pull requests are green → `/gg-publish`
31
34
  - Published → `/gg-cleanup`
32
35
 
33
- The review between push and publish is `gg do review` plus the
34
- `/review-light` skill, not a `gg-` skill of this layer.
35
-
36
36
  ## Important
37
37
 
38
38
  - Only list the skills, never run one of them unasked.
@@ -12,6 +12,8 @@ creates and pushes the version tags. It is interactive — the user runs it.
12
12
 
13
13
  - Every repo of the ticket is committed and pushed.
14
14
  - The pull requests created by `gg do review` are green.
15
+ - Every repo with `doc/guides/blog-guide.md` holds the post of this ticket
16
+ in `doc/blog/<yyyy>`. If one is missing, go back to `/gg-review`.
15
17
 
16
18
  ## 2. Configure the publish
17
19
 
@@ -0,0 +1,47 @@
1
+ ---
2
+ name: gg-review
3
+ 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.
4
+ ---
5
+
6
+ # Review
7
+
8
+ Each repo documents its change first, so the documentation lands in the
9
+ pull requests and is reviewed with the code. Every commit after
10
+ `gg do review` voids the review.
11
+
12
+ ## 1. Document the change in every repo
13
+
14
+ Look for `doc/guides/blog-guide.md` in every repo of the ticket, the
15
+ project management repo included. It comes from the `dna_blog` layer.
16
+
17
+ - Run `/blog` in each repo that has it; skip the others
18
+ - `/blog` stops by itself when the post already exists
19
+
20
+ Update `index.jsonc` and `README.md` of each repo the ticket changed.
21
+
22
+ Let the user review the changes, then run `/gg-commit` and `/gg-push`.
23
+
24
+ ## 2. Open the pull requests
25
+
26
+ Let the user confirm that the review phase is started. From the ticket
27
+ folder:
28
+
29
+ ```bash
30
+ gg do review
31
+ ```
32
+
33
+ gg creates a pull request for each repo and prints the URLs to the
34
+ terminal.
35
+
36
+ ## 3. Review the changes
37
+
38
+ Load the `/review-light` skill and execute it.
39
+
40
+ A fix goes through `/gg-commit` and `/gg-push`, then run `gg do review`
41
+ again. Update the blog post of the repo when the fix changes what it
42
+ describes.
43
+
44
+ ## Important
45
+
46
+ - Never write a blog post in a repo without `doc/guides/blog-guide.md`.
47
+ - Never start `gg do review` without the user's confirmation.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ggdna/dna-gg",
3
- "version": "0.9.0",
3
+ "version": "0.11.0",
4
4
  "description": "DNA layer: gg CLI workflow guides, repo setup scripts and CI check",
5
5
  "keywords": [
6
6
  "dna",