@buildinternet/releases-skills 0.25.0 → 0.26.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.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/skills/managing-sources/SKILL.md +1 -1
  3. package/skills/seeding-playbooks/SKILL.md +4 -7
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@buildinternet/releases-skills",
3
- "version": "0.25.0",
3
+ "version": "0.26.0",
4
4
  "description": "Agent skills bundled with the Releases CLI. Markdown playbooks for changelog ingest, discovery, and analysis.",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/skills/managing-sources/SKILL.md CHANGED
@@ -30,7 +30,7 @@ Operations can be performed via CLI commands or typed MCP/agent tools. Use which
30
30
  | Ignore URL | `releases admin policy ignore add --org <org> <url>` | `exclude_url` action "ignore" with url, organization |
31
31
  | Block URL | `releases admin policy block add <url>` | `exclude_url` action "block" with url |
32
32
  | Get playbook | `releases admin playbook <org>` | `manage_playbook` action "get" with organization |
33
- | Update playbook notes | `releases admin playbook <org> --notes "..."` | `manage_playbook` action "update_notes" with organization, notes |
33
+ | Update playbook notes | `releases admin playbook <org> --notes-file <path>` (use `-` for stdin) | `manage_playbook` action "update_notes" with organization, notes |
34
34
 
35
35
  Valid categories (pass to `manage_org`/`manage_product`): see the enum in those tool descriptions or your system prompt. `list_categories` (now retired) has been folded into the two tool descriptions.
36
36
 
package/skills/seeding-playbooks/SKILL.md CHANGED
@@ -109,15 +109,14 @@ Products: {product list or "none"}
109
109
  **Coverage**: 2-3 sentences. Which sources are canonical, whether there are gaps.
110
110
 
111
111
  Save by running:
112
- releases admin playbook {slug} --notes "$(cat <<'NOTES'
112
+ releases admin playbook {slug} --notes-file - 2>/dev/null <<'NOTES'
113
113
  YOUR NOTES HERE
114
114
  NOTES
115
- )" 2>/dev/null
116
115
 
117
116
  Verify with: releases admin playbook {slug} 2>/dev/null | tail -20
118
117
  ```
119
118
 
120
- The playbook header regenerates automatically after any source create/update/delete, and the `--notes` PATCH seeds a fresh header on first write — no separate regenerate step needed.
119
+ The playbook header regenerates automatically after any source create/update/delete, and the `--notes-file` PATCH seeds a fresh header on first write — no separate regenerate step needed.
121
120
 
122
121
  ### Verified prompt template
123
122
 
@@ -156,10 +155,9 @@ Every claim must cite observed data. If uncertain, say so explicitly.
156
155
 
157
156
  ## Step 4: Save
158
157
 
159
- releases admin playbook {slug} --notes "$(cat <<'NOTES'
158
+ releases admin playbook {slug} --notes-file - 2>/dev/null <<'NOTES'
160
159
  YOUR NOTES HERE
161
160
  NOTES
162
- )" 2>/dev/null
163
161
 
164
162
  Verify with: releases admin playbook {slug} 2>/dev/null | tail -20
165
163
  ```
@@ -184,10 +182,9 @@ Sub-agents may be blocked from saving notes via Bash (heredoc permission issues)
184
182
  2. The parent agent (you) saves the notes manually:
185
183
 
186
184
  ```bash
187
- releases admin playbook {slug} --notes "$(cat <<'NOTES'
185
+ releases admin playbook {slug} --notes-file - 2>/dev/null <<'NOTES'
188
186
  {paste notes from agent result}
189
187
  NOTES
190
- )" 2>/dev/null
191
188
  ```
192
189
 
193
190
  This is a known limitation of subagent permissions. Plan for it — check each agent's result and save manually if needed.