@buildinternet/releases-skills 0.47.0 → 0.48.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/package.json
CHANGED
|
@@ -240,3 +240,5 @@ Organizations can have multiple distinct products (e.g., Vercel → Next.js, Tur
|
|
|
240
240
|
Use product and org management operations to organize what you find. CLI: `releases admin product create`, `releases admin org tag add`, `releases categories`. Typed tools: `manage_product`, `manage_org` — each carries the valid category list in its description (also provided in your system prompt).
|
|
241
241
|
|
|
242
242
|
Don't force product groupings when sources are ambiguous — leave them at the org level and note suggestions in the state file.
|
|
243
|
+
|
|
244
|
+
When a company is multi-product (you found a multi-product `changelog.json`, or distinct product changelogs/repos), carry that grouping into onboarding by tagging each source with its `productName`/`productSlug` (see *Grouping sources into products* in `managing-sources`). Index only the org's own products, not ecosystem/community plugins.
|
|
@@ -65,6 +65,19 @@ Rules, in priority order:
|
|
|
65
65
|
|
|
66
66
|
When in doubt: would a developer reading this name on its own (with the org already shown above) recognize what it is? If yes, strip. If no, keep the prefix.
|
|
67
67
|
|
|
68
|
+
### Grouping sources into products
|
|
69
|
+
|
|
70
|
+
**Grouping sources into products.** Most companies are single-product — leave `productSlug`/`productName` unset and sources attach directly to the org (the default).
|
|
71
|
+
|
|
72
|
+
Only when a company ships **2 or more genuinely distinct products** — each with its own identity and release cadence (Vercel → Next.js, Turborepo, SWR; Datadog → APM, RUM, Browser SDK) — tag each discovered source with the product it belongs to: `productName` (canonical name, same naming rules as sources — no org prefix) and `productSlug` (stable kebab-case, per-org unique).
|
|
73
|
+
|
|
74
|
+
A product is a distinct offering, **not**:
|
|
75
|
+
- the company/engineering blog, newsroom, or all-in-one changelog → leave org-direct (untagged)
|
|
76
|
+
- the docs site or marketing feed → org-direct
|
|
77
|
+
- every individual GitHub repo by default — only repos that are themselves a recognized product
|
|
78
|
+
|
|
79
|
+
If you can't name 2+ distinct products with confidence, tag nothing. Spurious products are worse than none.
|
|
80
|
+
|
|
68
81
|
### Organization descriptions
|
|
69
82
|
|
|
70
83
|
When creating an org, include a brief one-sentence product description. This grounds AI summaries for lesser-known products, and it's also the primary signal for the entity vector index — the unified `search` tool (and the registry side of hybrid search) matches on description + category, not just name. A good description noticeably improves recall.
|