elliot-stack 1.0.15 → 1.0.16

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "elliot-stack",
3
- "version": "1.0.15",
3
+ "version": "1.0.16",
4
4
  "description": "Elliot's skill stack for Claude Code — install via npx elliot-stack@latest",
5
5
  "bin": {
6
6
  "elliot-stack": "bin/install.cjs"
@@ -369,3 +369,34 @@ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quo
369
369
  Share the printed URL with the user and offer to open it in their browser.
370
370
 
371
371
  They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
372
+
373
+ ---
374
+
375
+ ## Skill Feedback
376
+
377
+ If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
378
+
379
+ **If `gh` is installed** (`gh --version` succeeds), create the issue directly:
380
+
381
+ ```bash
382
+ gh issue create \
383
+ --repo ElliotDrel/e-stack \
384
+ --title "estack-active-learning-tutor: <concise summary>" \
385
+ --body "<description from user feedback — expected vs. actual behavior and context>"
386
+ ```
387
+
388
+ **If `gh` is not installed**, build a pre-filled URL:
389
+
390
+ ```bash
391
+ python3 -c "
392
+ import urllib.parse
393
+ title = 'estack-active-learning-tutor: <concise summary>'
394
+ body = '<description from user feedback — expected vs. actual behavior and context>'
395
+ base = 'https://github.com/ElliotDrel/e-stack/issues/new'
396
+ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
397
+ "
398
+ ```
399
+
400
+ Share the printed URL with the user and offer to open it in their browser.
401
+
402
+ They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
@@ -123,3 +123,34 @@ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quo
123
123
  Share the printed URL with the user and offer to open it in their browser.
124
124
 
125
125
  They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
126
+
127
+ ---
128
+
129
+ ## Skill Feedback
130
+
131
+ If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
132
+
133
+ **If `gh` is installed** (`gh --version` succeeds), create the issue directly:
134
+
135
+ ```bash
136
+ gh issue create \
137
+ --repo ElliotDrel/e-stack \
138
+ --title "estack-better-title: <concise summary>" \
139
+ --body "<description from user feedback — expected vs. actual behavior and context>"
140
+ ```
141
+
142
+ **If `gh` is not installed**, build a pre-filled URL:
143
+
144
+ ```bash
145
+ python3 -c "
146
+ import urllib.parse
147
+ title = 'estack-better-title: <concise summary>'
148
+ body = '<description from user feedback — expected vs. actual behavior and context>'
149
+ base = 'https://github.com/ElliotDrel/e-stack/issues/new'
150
+ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
151
+ "
152
+ ```
153
+
154
+ Share the printed URL with the user and offer to open it in their browser.
155
+
156
+ They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
@@ -139,3 +139,34 @@ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quo
139
139
  Share the printed URL with the user and offer to open it in their browser.
140
140
 
141
141
  They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
142
+
143
+ ---
144
+
145
+ ## Skill Feedback
146
+
147
+ If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
148
+
149
+ **If `gh` is installed** (`gh --version` succeeds), create the issue directly:
150
+
151
+ ```bash
152
+ gh issue create \
153
+ --repo ElliotDrel/e-stack \
154
+ --title "estack-chris-voss: <concise summary>" \
155
+ --body "<description from user feedback — expected vs. actual behavior and context>"
156
+ ```
157
+
158
+ **If `gh` is not installed**, build a pre-filled URL:
159
+
160
+ ```bash
161
+ python3 -c "
162
+ import urllib.parse
163
+ title = 'estack-chris-voss: <concise summary>'
164
+ body = '<description from user feedback — expected vs. actual behavior and context>'
165
+ base = 'https://github.com/ElliotDrel/e-stack/issues/new'
166
+ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
167
+ "
168
+ ```
169
+
170
+ Share the printed URL with the user and offer to open it in their browser.
171
+
172
+ They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
@@ -119,3 +119,34 @@ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quo
119
119
  Share the printed URL with the user and offer to open it in their browser.
120
120
 
121
121
  They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
122
+
123
+ ---
124
+
125
+ ## Skill Feedback
126
+
127
+ If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
128
+
129
+ **If `gh` is installed** (`gh --version` succeeds), create the issue directly:
130
+
131
+ ```bash
132
+ gh issue create \
133
+ --repo ElliotDrel/e-stack \
134
+ --title "estack-customer-discovery: <concise summary>" \
135
+ --body "<description from user feedback — expected vs. actual behavior and context>"
136
+ ```
137
+
138
+ **If `gh` is not installed**, build a pre-filled URL:
139
+
140
+ ```bash
141
+ python3 -c "
142
+ import urllib.parse
143
+ title = 'estack-customer-discovery: <concise summary>'
144
+ body = '<description from user feedback — expected vs. actual behavior and context>'
145
+ base = 'https://github.com/ElliotDrel/e-stack/issues/new'
146
+ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
147
+ "
148
+ ```
149
+
150
+ Share the printed URL with the user and offer to open it in their browser.
151
+
152
+ They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
@@ -396,3 +396,34 @@ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quo
396
396
  Share the printed URL with the user and offer to open it in their browser.
397
397
 
398
398
  They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
399
+
400
+ ---
401
+
402
+ ## Skill Feedback
403
+
404
+ If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
405
+
406
+ **If `gh` is installed** (`gh --version` succeeds), create the issue directly:
407
+
408
+ ```bash
409
+ gh issue create \
410
+ --repo ElliotDrel/e-stack \
411
+ --title "estack-flight-planner: <concise summary>" \
412
+ --body "<description from user feedback — expected vs. actual behavior and context>"
413
+ ```
414
+
415
+ **If `gh` is not installed**, build a pre-filled URL:
416
+
417
+ ```bash
418
+ python3 -c "
419
+ import urllib.parse
420
+ title = 'estack-flight-planner: <concise summary>'
421
+ body = '<description from user feedback — expected vs. actual behavior and context>'
422
+ base = 'https://github.com/ElliotDrel/e-stack/issues/new'
423
+ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
424
+ "
425
+ ```
426
+
427
+ Share the printed URL with the user and offer to open it in their browser.
428
+
429
+ They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
@@ -370,3 +370,34 @@ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quo
370
370
  Share the printed URL with the user and offer to open it in their browser.
371
371
 
372
372
  They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
373
+
374
+ ---
375
+
376
+ ## Skill Feedback
377
+
378
+ If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
379
+
380
+ **If `gh` is installed** (`gh --version` succeeds), create the issue directly:
381
+
382
+ ```bash
383
+ gh issue create \
384
+ --repo ElliotDrel/e-stack \
385
+ --title "estack-github-issue-tracker: <concise summary>" \
386
+ --body "<description from user feedback — expected vs. actual behavior and context>"
387
+ ```
388
+
389
+ **If `gh` is not installed**, build a pre-filled URL:
390
+
391
+ ```bash
392
+ python3 -c "
393
+ import urllib.parse
394
+ title = 'estack-github-issue-tracker: <concise summary>'
395
+ body = '<description from user feedback — expected vs. actual behavior and context>'
396
+ base = 'https://github.com/ElliotDrel/e-stack/issues/new'
397
+ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
398
+ "
399
+ ```
400
+
401
+ Share the printed URL with the user and offer to open it in their browser.
402
+
403
+ They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
@@ -124,3 +124,34 @@ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quo
124
124
  Share the printed URL with the user and offer to open it in their browser.
125
125
 
126
126
  They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.
127
+
128
+ ---
129
+
130
+ ## Skill Feedback
131
+
132
+ If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
133
+
134
+ **If `gh` is installed** (`gh --version` succeeds), create the issue directly:
135
+
136
+ ```bash
137
+ gh issue create \
138
+ --repo ElliotDrel/e-stack \
139
+ --title "estack-repo-search: <concise summary>" \
140
+ --body "<description from user feedback — expected vs. actual behavior and context>"
141
+ ```
142
+
143
+ **If `gh` is not installed**, build a pre-filled URL:
144
+
145
+ ```bash
146
+ python3 -c "
147
+ import urllib.parse
148
+ title = 'estack-repo-search: <concise summary>'
149
+ body = '<description from user feedback — expected vs. actual behavior and context>'
150
+ base = 'https://github.com/ElliotDrel/e-stack/issues/new'
151
+ print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
152
+ "
153
+ ```
154
+
155
+ Share the printed URL with the user and offer to open it in their browser.
156
+
157
+ They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.