@ggdna/dna-gg 0.14.0 → 1.1.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/dna/_generated.json
CHANGED
|
@@ -39,7 +39,7 @@
|
|
|
39
39
|
"ecosystem": null,
|
|
40
40
|
"resolvedVersion": null,
|
|
41
41
|
"via": null,
|
|
42
|
-
"hash": "
|
|
42
|
+
"hash": "0x8654064a14538e39"
|
|
43
43
|
}
|
|
44
44
|
],
|
|
45
45
|
"claude": {
|
|
@@ -83,7 +83,7 @@
|
|
|
83
83
|
},
|
|
84
84
|
{
|
|
85
85
|
"path": ".claude/skills/gg-ticket/SKILL.md",
|
|
86
|
-
"hash": "
|
|
86
|
+
"hash": "0x0532d8ac37060521"
|
|
87
87
|
},
|
|
88
88
|
{
|
|
89
89
|
"path": ".claude/skills/gg/SKILL.md",
|
|
@@ -111,7 +111,7 @@
|
|
|
111
111
|
},
|
|
112
112
|
{
|
|
113
113
|
"path": "doc/guides/for-ai/ai-dev-guide.md",
|
|
114
|
-
"hash": "
|
|
114
|
+
"hash": "0x5ac430cba252b5bc"
|
|
115
115
|
},
|
|
116
116
|
{
|
|
117
117
|
"path": "doc/guides/index-guide.md",
|
|
@@ -130,7 +130,11 @@ code away is narrowed accordingly, and `interfaces.uses` and
|
|
|
130
130
|
Never split a repo, add or create one, or move code without the user's
|
|
131
131
|
confirmation.
|
|
132
132
|
|
|
133
|
-
## Open the workspace in Vscode
|
|
133
|
+
## Open the workspace in Vscode — only on request
|
|
134
|
+
|
|
135
|
+
Do not open VS Code on your own — many tickets need no editor. Tell the
|
|
136
|
+
user they can open the workspace from the ticket folder with the following
|
|
137
|
+
command, and run it only when the user asks for it:
|
|
134
138
|
|
|
135
139
|
```bash
|
|
136
140
|
gg do code
|
|
@@ -141,7 +145,7 @@ gg do code
|
|
|
141
145
|
Requirements come before the plan. If the project management repo keeps
|
|
142
146
|
requirements (`doc/requirements`) and none of its accepted requirements
|
|
143
147
|
covers the ticket, engineer them with the user first — with
|
|
144
|
-
`/plan-requirements` if the repo has it — and plan the ticket only after
|
|
148
|
+
`/gg-plan-requirements` if the repo has it — and plan the ticket only after
|
|
145
149
|
that. Bug tickets are the exception, they name their bug file.
|
|
146
150
|
|
|
147
151
|
Ask the user whether the ticket is planned before it is implemented.
|
|
@@ -74,17 +74,22 @@ After the confirmation:
|
|
|
74
74
|
gg do add repo1 repo2
|
|
75
75
|
```
|
|
76
76
|
|
|
77
|
-
## 5. Open the workspace
|
|
77
|
+
## 5. Open the workspace only on request
|
|
78
|
+
|
|
79
|
+
Do not open VS Code on your own — many tickets need no editor. Tell the
|
|
80
|
+
user they can open the workspace from the ticket folder with:
|
|
78
81
|
|
|
79
82
|
```bash
|
|
80
83
|
gg do code
|
|
81
84
|
```
|
|
82
85
|
|
|
86
|
+
Run it only when the user asks for it.
|
|
87
|
+
|
|
83
88
|
## 6. Plan or implement
|
|
84
89
|
|
|
85
90
|
If the project management repo keeps requirements (`doc/requirements`)
|
|
86
91
|
and no accepted requirement covers the ticket, engineer them with the user
|
|
87
|
-
first — with `/plan-requirements` if the repo has it — before any plan or
|
|
92
|
+
first — with `/gg-plan-requirements` if the repo has it — before any plan or
|
|
88
93
|
code. Bug tickets are the exception, they name their bug file.
|
|
89
94
|
|
|
90
95
|
Ask the user whether the ticket is planned first. If yes, write the plan
|
|
@@ -128,5 +133,6 @@ repo concerned. Section "Keep every repo in its scope" of
|
|
|
128
133
|
- Never add repos without confirmation — a manually entered list counts as
|
|
129
134
|
one. Rather too few than too many — more can be added later.
|
|
130
135
|
- Do not start the implementation unasked.
|
|
136
|
+
- Do not open VS Code unasked.
|
|
131
137
|
- Never split a repo, add or create one, or move code without the user's
|
|
132
138
|
confirmation.
|