@buildinternet/releases-skills 0.14.0 → 0.16.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@buildinternet/releases-skills",
-  "version": "0.14.0",
+  "version": "0.16.0",
   "description": "Agent skills bundled with the Releases CLI. Markdown playbooks for changelog ingest, discovery, and analysis.",
   "type": "module",
   "license": "MIT",

package/skills/analyzing-releases/SKILL.md

@@ -19,7 +19,7 @@ Turn changelog data into competitive intelligence by analyzing release patterns
 |-----------|-----|------------|
 | Check existing sources | `releases list --query <company> --json` | `list_sources` with query param |
 | Fetch releases | `releases admin source fetch <slug> --max 50` | `fetch_source` with identifier (ID or slug) |
-| Get latest releases | `releases latest <slug> --json` | `get_latest_releases` with source/org and limit |
+| Get latest releases | `releases tail <slug> --json` | `get_latest_releases` with source/org and limit |
 | Search releases | `releases search <query> --json` | `search_releases` with query |
 | Summarize | `releases summary <slug> --json` | (not available as typed tool) |
 | Compare | `releases compare <slugA> <slugB> --json` | (not available as typed tool) |
@@ -70,5 +70,5 @@ Ask the user where to save the analysis, or use your best judgment based on the
 
 - Focus on what companies shipped. If a source has noisy data (blog posts mixed in, missing dates), work around it silently. Don't include source quality commentary in the report unless a company had to be substantially excluded.
 - Fill data gaps with web fetches. List sources to get release URLs, then WebFetch to spot-check pages for missing dates, versions, or feature details.
-- For velocity counting, get the latest releases with dates — CLI: `releases latest <slug> --json`, typed tool: `get_latest_releases`.
+- For velocity counting, get the latest releases with dates — CLI: `releases tail <slug> --json`, typed tool: `get_latest_releases`.
 - AI-powered summarize and compare are only available via CLI (`releases summary`, `releases compare`). When using typed tools, synthesize manually from raw release data.

package/skills/managing-sources/SKILL.md

@@ -18,7 +18,7 @@ Operations can be performed via CLI commands or typed MCP/agent tools. Use which
 | Edit source | `releases admin source edit <identifier> [--primary] [--priority <p>]` | `edit_source` with identifier (ID or slug), is_primary, fetch_priority params |
 | Remove source | `releases admin source remove <slug> [--ignore --reason <reason>]` | `remove_source` with identifier (ID or slug) param |
 | Fetch releases | `releases admin source fetch <slug> [--dry-run] [--max <n>]` | `fetch_source` with identifier (ID or slug) param |
-| Get latest releases | `releases latest [slug] --json [--org <org>]` | `get_latest_releases` with source, organization, limit params |
+| Get latest releases | `releases tail [slug] --json [--org <org>]` | `get_latest_releases` with source, organization, limit params |
 | Search releases | `releases search <query> --json` | `search_releases` with query, limit params |
 | Evaluate URL | `releases admin discovery evaluate <url> --json` | `evaluate_url` with url param |
 | Add org | `releases admin org add <name> [--domain <d>] [--description <t>] [--category <c>] [--tags <t1,t2>]` | `manage_org` action "add" with name, domain, description, category, tags |

package/skills/parsing-changelogs/SKILL.md

@@ -32,7 +32,7 @@ Key CLI flags (not available via typed tool — the typed tool always does a ful
 
 ### Checking results
 
-After fetching, verify releases were persisted. CLI: `releases latest <slug> --json` or `releases admin source fetch-log <slug>`. Typed tool: `get_latest_releases` with source param. Use `get_organization` (or `releases admin org show <slug> --json`) to see the full picture of an org's sources.
+After fetching, verify releases were persisted. CLI: `releases tail <slug> --json` or `releases admin source fetch-log <slug>`. Typed tool: `get_latest_releases` with source param. Use `get_organization` (or `releases admin org show <slug> --json`) to see the full picture of an org's sources.
 
 ## Incremental vs Bulk Parsing
 
@@ -74,7 +74,7 @@ Do NOT fetch release URLs in the parent agent — always delegate to a subagent
 If pages are richer than feed content (more text, images, videos, or code examples):
 1. Record the assessment and enable crawl mode. CLI: `releases admin source edit <identifier> --metadata '{"feedContentDepth":"summary-only","crawlEnabled":true}'`. Typed tool: `edit_source` with the same metadata. Subsequent fetches will follow links to per-release pages and extract full content in one pass.
 2. Re-fetch the source once to backfill. CLI: `releases admin source fetch <slug> --full`. Typed tool: `fetch_source`.
-3. Verify results. CLI: `releases list <slug> --json` or `releases latest <slug>`. Typed tool: `get_latest_releases` — check content is richer after the re-fetch.
+3. Verify results. CLI: `releases list <slug> --json` or `releases tail <slug>`. Typed tool: `get_latest_releases` — check content is richer after the re-fetch.
 
 If feed already provides full content with no meaningful additions on the page:
 1. Record `feedContentDepth: "full"` so future sessions skip the sampling step.
@@ -175,6 +175,6 @@ When you encounter a new rollup source during discovery or fetch, update the pla
 When adding a new source, always validate before committing:
 
 1. **Fetch** — CLI: `releases admin source fetch <slug> --dry-run` then `releases admin source fetch <slug>`. Typed tool: `fetch_source` with identifier (ID or slug).
-2. **Verify** — CLI: `releases latest <slug> --json` or `releases admin source fetch-log <slug>`. Typed tool: `get_latest_releases` with source identifier.
+2. **Verify** — CLI: `releases tail <slug> --json` or `releases admin source fetch-log <slug>`. Typed tool: `get_latest_releases` with source identifier.
 3. **If poor results** — try a different URL or type. CLI: `releases admin source edit <identifier> --type feed`. Typed tool: `edit_source` with identifier.
 4. **If no usable releases** — remove the source. CLI: `releases admin source remove <slug> --ignore --reason "..."`. Typed tool: `remove_source` with identifier, then `exclude_url`.

package/skills/releases-cli/SKILL.md

@@ -32,8 +32,8 @@ The CLI talks to `api.releases.sh` by default — no configuration needed for re
 ```bash
 # Reader (no auth required)
 releases search "breaking change"            # hybrid FTS + semantic search
-releases latest next-js                      # latest releases from one source
-releases latest --org vercel --count 20      # latest from a whole org
+releases tail next-js                      # latest releases from one source
+releases tail --org vercel --count 20      # latest from a whole org
 releases list --category ai                  # browse sources
 releases show vercel                         # dispatch by id or slug
 releases stats                               # registry overview

package/skills/releases-cli/references/reader.md

@@ -27,12 +27,12 @@ Chunk hits carry `sourceSlug`, `chunkOffset`, and `chunkLength` so you can chain
 ## Latest releases
 
 ```bash
-releases latest                          # across all sources
-releases latest next-js                  # one source (by slug)
-releases latest --org vercel --count 20  # whole org
-releases latest --product nextjs         # one product
-releases latest --type feature           # filter by release type
-releases latest --json
+releases tail                          # across all sources
+releases tail next-js                  # one source (by slug)
+releases tail --org vercel --count 20  # whole org
+releases tail --product nextjs         # one product
+releases tail --type feature           # filter by release type
+releases tail --json
 ```
 
 ## List sources