myte 0.0.6 → 0.0.7
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 +51 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -12,16 +12,22 @@ Use one of these flows:
|
|
|
12
12
|
- then run `npx myte bootstrap`
|
|
13
13
|
- then run `npx myte sync-qaqc`
|
|
14
14
|
- then run `npx myte query "What changed in logging?" --with-diff`
|
|
15
|
+
- then run `npx myte update-team "Backend deploy completed; QAQC rerun queued."`
|
|
16
|
+
- then run `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
|
|
15
17
|
- or `npm exec myte -- query "What changed in logging?" --with-diff`
|
|
16
18
|
- Global install:
|
|
17
19
|
- `npm i -g myte`
|
|
18
20
|
- then run `myte bootstrap`
|
|
19
21
|
- then run `myte sync-qaqc`
|
|
20
22
|
- then run `myte query "What changed in logging?" --with-diff`
|
|
23
|
+
- then run `myte update-team "Backend deploy completed; QAQC rerun queued."`
|
|
24
|
+
- then run `myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
|
|
21
25
|
- No install:
|
|
22
26
|
- `npx myte@latest bootstrap`
|
|
23
27
|
- `npx myte@latest sync-qaqc`
|
|
24
28
|
- `npx myte@latest query "What changed in logging?" --with-diff`
|
|
29
|
+
- `npx myte@latest update-team "Backend deploy completed; QAQC rerun queued."`
|
|
30
|
+
- `npx myte@latest update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
|
|
25
31
|
|
|
26
32
|
`npm install myte` by itself does not put `myte` on your shell PATH. Use `npx myte` or `npm exec myte -- ...` unless you installed globally.
|
|
27
33
|
|
|
@@ -188,6 +194,49 @@ To inspect the exact payload before sending it:
|
|
|
188
194
|
- `npx myte create-prd ./drafts/auth-prd.md --print-context`
|
|
189
195
|
- `npx myte create-prd ./drafts/auth-prd.md --description "Short card summary" --print-context`
|
|
190
196
|
|
|
197
|
+
## Team updates
|
|
198
|
+
|
|
199
|
+
Use `update-team` to add a project comment through the project-key Project Assistant surface.
|
|
200
|
+
|
|
201
|
+
Examples:
|
|
202
|
+
|
|
203
|
+
- `npx myte update-team "Backend deploy completed; QAQC rerun queued."`
|
|
204
|
+
- `npm exec myte -- update-team "Frontend review is ready for sign-off."`
|
|
205
|
+
- `Get-Content -Raw .\notes\team-update.md | npx myte update-team --stdin`
|
|
206
|
+
|
|
207
|
+
What it sends:
|
|
208
|
+
|
|
209
|
+
- `POST /api/project-assistant/project-comment`
|
|
210
|
+
- payload: `{ "content": "..." }`
|
|
211
|
+
|
|
212
|
+
Useful forms:
|
|
213
|
+
|
|
214
|
+
- `npx myte update-team "Backend deploy completed." --print-context`
|
|
215
|
+
- `npx myte update-team "Backend deploy completed." --json`
|
|
216
|
+
|
|
217
|
+
## Client update drafts
|
|
218
|
+
|
|
219
|
+
Use `update-client` to draft a branded client update email for owner review.
|
|
220
|
+
|
|
221
|
+
Examples:
|
|
222
|
+
|
|
223
|
+
- `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
|
|
224
|
+
- `npx myte update-client --subject "Weekly client update" --body-markdown "## Progress\n- Login complete" --target-contact-ids 507f1f77bcf86cd799439011,507f1f77bcf86cd799439012`
|
|
225
|
+
- `Get-Content -Raw .\updates\week-12.md | npx myte update-client --stdin --subject "Weekly client update"`
|
|
226
|
+
|
|
227
|
+
What it sends:
|
|
228
|
+
|
|
229
|
+
- `POST /api/project-assistant/client-update-drafts`
|
|
230
|
+
- payload: `{ "subject": "...", "body_markdown": "...", "target_contact_ids": ["..."] }`
|
|
231
|
+
|
|
232
|
+
Notes:
|
|
233
|
+
|
|
234
|
+
- `--subject` is required.
|
|
235
|
+
- The body can come from `--body-markdown`, `--body-file`, a positional file path, positional inline text, or `--stdin`.
|
|
236
|
+
- `target_contact_ids` are optional. If omitted, the backend selects the linked primary client contact when available.
|
|
237
|
+
- Use `--target-contact-id <id>` multiple times or `--target-contact-ids <id1,id2>`.
|
|
238
|
+
- The CLI prints the returned draft summary, including the draft id, status, recipients, and snippet.
|
|
239
|
+
|
|
191
240
|
## Common commands
|
|
192
241
|
|
|
193
242
|
- `npm install myte`
|
|
@@ -196,3 +245,5 @@ To inspect the exact payload before sending it:
|
|
|
196
245
|
- `npx myte config --json`
|
|
197
246
|
- `npx myte query "Summarize the current branch changes" --with-diff`
|
|
198
247
|
- `npx myte create-prd ./drafts/auth-prd.md`
|
|
248
|
+
- `npx myte update-team "Backend deploy completed; QAQC rerun queued."`
|
|
249
|
+
- `npx myte update-client --subject "Weekly client update" --body-file ./updates/week-12.md`
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "myte",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.7",
|
|
4
4
|
"description": "Myte developer CLI (Project Assistant + deterministic diffs).",
|
|
5
5
|
"type": "commonjs",
|
|
6
6
|
"license": "MIT",
|
|
@@ -16,6 +16,6 @@
|
|
|
16
16
|
"node": ">=18"
|
|
17
17
|
},
|
|
18
18
|
"dependencies": {
|
|
19
|
-
"@mytegroupinc/myte-core": "0.0.
|
|
19
|
+
"@mytegroupinc/myte-core": "0.0.7"
|
|
20
20
|
}
|
|
21
21
|
}
|