ce-release-notes

Summarize compound-engineering plugin releases or answer questions about past releases with version citations.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-release-notes-norfolk-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-release-notes
Source: https://github.com/Norfolk-Group/marcela-norfolk-ai/tree/main/skills/compound-engineering/skills/ce-release-notes
Command: npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-release-notes-norfolk-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Keeping track of what changed across releases of the compound-engineering plugin requires manually browsing GitHub release pages. This Skill fetches release data from the GitHub Releases API and either summarizes the last 5 plugin releases or answers a specific question about a past change with a cited version. ## Core Features & Use Cases - Release Summaries: Bare invocation renders the last 5 plugin releases with dates, bodies (soft-capped at 25 lines), and links to full notes. - Question Answering with Citations: Pass a query like "what happened to deepen-plan?" to search the last 40 releases and get a narrative answer citing the exact version that introduced the change, optionally enriched with linked PR context via gh pr view. - Resilient Fetching: A helper script prefers the authenticated gh CLI and falls back to the anonymous GitHub API, returning structured JSON with clear rate-limit and network error messages. - Use Case: After upgrading the plugin, ask "/ce-release-notes what changed recently?" to see the last 5 releases, or ask "/ce-release-notes when was the review skill renamed?" to pinpoint the exact version. ## Quick Start Ask the assistant to run /ce-release-notes to summarize the last 5 compound-engineering plugin releases, or add a question about a specific past change.

Frequently Asked Questions about ce-release-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I see what changed in recent compound-engineering plugin releases?

Invoke /ce-release-notes with no arguments. It fetches releases from the GitHub Releases API, filters to compound-engineering-v* tags, and renders the last 5 releases with dates, bodies, and links to full notes.

How do I find which release changed a specific skill?

Pass a question as an argument, such as "/ce-release-notes what happened to deepen-plan?". The skill searches the last 40 plugin releases, judges matches by content rather than substring, and answers with an inline version citation like (v2.67.0).

Does ce-release-notes require the gh CLI to work?

No. The helper script prefers the authenticated gh CLI but falls back to the anonymous GitHub API if gh is missing or fails. Anonymous access is rate-limited, so authenticating gh removes that limit.

Why does ce-release-notes say python3 is required?

The skill runs a Python helper script to fetch releases. If python3 is not installed or the script cannot launch, the skill prints an install message and stops. Install Python 3.x or browse the GitHub releases page directly.

What happens when the GitHub API rate limit is hit?

The helper returns a structured error with code rate_limit and a reset-time hint. The skill prints the error message and suggests authenticating gh or opening the releases page directly.

Can I look up a release by version number like 2.65.0?

Version-like inputs are treated as query strings, not a separate lookup mode. The query flows through the same 40-release search window and matches against release bodies and linked PR titles.