Run any Skill in Manus with one click

release-notes

Stars443

Forks83

UpdatedJuly 12, 2026 at 08:33

Bump the version and write a CHANGELOG.md release-notes entry after a user-facing change ships. Use when asked to "bump the version", "cut a release", "add a changelog entry", or "write release notes". Produces one minimal, user-facing, technical bullet per change.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

bagofwords1

bagofwords1/bagofwords

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	release-notes
description	Bump the version and write a CHANGELOG.md release-notes entry after a user-facing change ships. Use when asked to "bump the version", "cut a release", "add a changelog entry", or "write release notes". Produces one minimal, user-facing, technical bullet per change.

Release notes & version bump

Two files, one commit. VERSION drives the release; CHANGELOG.md is the human-readable history.

VERSION — a single line, MAJOR.MINOR.PATCH (e.g. 0.0.448). The Release workflow (.github/workflows/release.yml) reads it, tags vX.Y.Z, and extracts the matching CHANGELOG.md section as the GitHub release body.
CHANGELOG.md — newest version first. Served to users at /changelog (parsed by backend/app/routes/changelog.py), so the format is load-bearing.

Steps

Bump VERSION. Increment the patch by one (0.0.448 → 0.0.449) unless told otherwise. No leading spaces, no trailing newline changes — just the number.
Add a section at the top of CHANGELOG.md, directly under # Release Notes:
```
## Version <new-version> (<Month DD, YYYY>)
- **<Title> (#<PR>)** — <one-line description>.
```
Use today's date, format July 12, 2026. One bullet per user-facing change; group the whole release under this single version heading.
Commit both files together: Bump version to <X.Y.Z> with changelog entry.

How to write a bullet

Format: - **Title (#PR)** — description.

Bold title — a short noun phrase for the feature/fix (**Elasticsearch connector**, **Fix SSO login for mismatched email casing**). Prefix fixes with Fix.
(#PR) — the pull request number, if known. Omit the parens entirely if there's no PR.
— (em-dash + spaces) separates title from description.
Description — what the user can now do, or what stopped being broken. Technical but plain. Name the real thing (PromQL, SSE, .xlsx, the org setting, the env var). One sentence. End with a period.

Rules

Minimal. One line per change. If it needs two sentences, the second adds a concrete knob (default value, env var, setting name) — not narration.
User-facing only. Skip pure refactors, test-only changes, CI, and dependency bumps. If a user can't observe it, it's not a release note.
Present tense, user's point of view. "Charts export to Excel" — not "Added the ability to export" or "We changed the exporter".
No filler. Drop "now", "the ability to", "support for", "improved", "various", "enhancements". State the capability directly.
Be specific, not vague. "caps requests per minute/hour/day, enforced as a hard block" beats "better rate limiting".
Never real data. No customer/org names, account identifiers, emails, tokens, connection strings, or any PII — release notes are public. Use generic placeholders (<name>, acme) if an example needs one.

Examples

Feature:

- **Prometheus connector (#595)** — query metrics with PromQL over the Prometheus HTTP API; each metric becomes a table.

Feature with a knob:

- **Concurrent multi-tool execution (#598)** — one planner decision can run its tool calls in parallel, controlled by the `ai_tool_concurrency` org setting (defaults to 4; set to 1 for serial).

Fix:

- **Fix iOS focus-zoom on the report prompt box (#600)** — the mobile prompt field is pinned to 16px so tapping it no longer zooms the viewport.

Fix with cause:

- **Fix profile Usage tab never updating (#576)** — usage counters now record without a hard cap configured, and the tab refreshes the session on open instead of showing stale zeros.

Config/model change (no PR):

- **OpenAI model presets** — add GPT-5.6 Sol, Terra, and Luna; make Terra the default and retire the GPT-5.4/5.2 presets.

A full release section:

## Version 0.0.438 (July 7, 2026)
- **Triggers (#562)** — user-owned webhooks that spawn agent sessions, plus report-per-run routing for scheduled tasks, under a new Automations page.
- **QVD indexing progress (#564)** — real per-file indexing progress with stop, file size, and duration.
- **WhatsApp fixes (#565)** — agent replies (text + data) are delivered back to WhatsApp, and the verification page shows WhatsApp branding instead of Slack.

More from this repository

same repository

security-scan

bagofwords1/bagofwords

Run a Snyk security scan of the repo (frontend npm deps, backend pip deps, Dockerfile/base image, and Snyk Code SAST), triage findings, and remediate the real ones with verified fixes. Use for "scan with Snyk", "resolve the security issues", dependency-CVE cleanup, or a pre-release security pass.

2026-07-12443

add-connection-type

bagofwords1/bagofwords

Add a new data source / connection type (e.g. a SQL Server-like database) end to end — client with get_schemas/execute_query, config + credentials schemas, registry entry, icon, tests — plus the verification steps. Also covers adding or updating an MCP connector (a preset, not a new type). Use when adding or significantly extending a connector.

2026-07-11443

add-llm-provider-or-model

bagofwords1/bagofwords

Add a new LLM model to the preset catalog, or a whole new LLM provider — with the mandatory pre-flight verification of model id, pricing, and context window against the provider's official docs. Use when asked to add/update LLM models, providers, or pricing.

2026-07-04443

sandbox-feedback-loop

bagofwords1/bagofwords

Build a runnable reproduce→fix→verify loop for a bug or feature in a fresh sandbox, and record it as a feedback-loop doc. Use when investigating a reported bug, validating a root cause, or proving a fix works — before and after the change.

2026-07-04443

localization

bagofwords1/bagofwords

The locale/i18n architecture of bagofwords — catalogs, resolution order, RTL, backend contracts — and the procedures for adding strings, adding a locale, or translating UI. Use when adding/changing user-facing strings, working on RTL, emails, localized errors, or anything locale-related.

2026-07-04443

ui-evidence

bagofwords1/bagofwords

Capture mandatory before/after screenshots (and videos/GIFs for flows) for any change touching UI/UX, and attach them to the PR. Use whenever a change touches frontend/pages, components, layouts, or assets.

2026-07-04443

name	release-notes
description	Bump the version and write a CHANGELOG.md release-notes entry after a user-facing change ships. Use when asked to "bump the version", "cut a release", "add a changelog entry", or "write release notes". Produces one minimal, user-facing, technical bullet per change.

Release notes & version bump

Two files, one commit. VERSION drives the release; CHANGELOG.md is the human-readable history.

VERSION — a single line, MAJOR.MINOR.PATCH (e.g. 0.0.448). The Release workflow (.github/workflows/release.yml) reads it, tags vX.Y.Z, and extracts the matching CHANGELOG.md section as the GitHub release body.
CHANGELOG.md — newest version first. Served to users at /changelog (parsed by backend/app/routes/changelog.py), so the format is load-bearing.

Steps

Bump VERSION. Increment the patch by one (0.0.448 → 0.0.449) unless told otherwise. No leading spaces, no trailing newline changes — just the number.
Add a section at the top of CHANGELOG.md, directly under # Release Notes:
```
## Version <new-version> (<Month DD, YYYY>)
- **<Title> (#<PR>)** — <one-line description>.
```
Use today's date, format July 12, 2026. One bullet per user-facing change; group the whole release under this single version heading.
Commit both files together: Bump version to <X.Y.Z> with changelog entry.

How to write a bullet

Format: - **Title (#PR)** — description.

Bold title — a short noun phrase for the feature/fix (**Elasticsearch connector**, **Fix SSO login for mismatched email casing**). Prefix fixes with Fix.
(#PR) — the pull request number, if known. Omit the parens entirely if there's no PR.
— (em-dash + spaces) separates title from description.
Description — what the user can now do, or what stopped being broken. Technical but plain. Name the real thing (PromQL, SSE, .xlsx, the org setting, the env var). One sentence. End with a period.

Rules

Minimal. One line per change. If it needs two sentences, the second adds a concrete knob (default value, env var, setting name) — not narration.
User-facing only. Skip pure refactors, test-only changes, CI, and dependency bumps. If a user can't observe it, it's not a release note.
Present tense, user's point of view. "Charts export to Excel" — not "Added the ability to export" or "We changed the exporter".
No filler. Drop "now", "the ability to", "support for", "improved", "various", "enhancements". State the capability directly.
Be specific, not vague. "caps requests per minute/hour/day, enforced as a hard block" beats "better rate limiting".
Never real data. No customer/org names, account identifiers, emails, tokens, connection strings, or any PII — release notes are public. Use generic placeholders (<name>, acme) if an example needs one.

Examples

Feature:

- **Prometheus connector (#595)** — query metrics with PromQL over the Prometheus HTTP API; each metric becomes a table.

Feature with a knob:

- **Concurrent multi-tool execution (#598)** — one planner decision can run its tool calls in parallel, controlled by the `ai_tool_concurrency` org setting (defaults to 4; set to 1 for serial).

Fix:

- **Fix iOS focus-zoom on the report prompt box (#600)** — the mobile prompt field is pinned to 16px so tapping it no longer zooms the viewport.

Fix with cause:

- **Fix profile Usage tab never updating (#576)** — usage counters now record without a hard cap configured, and the tab refreshes the session on open instead of showing stale zeros.

Config/model change (no PR):

- **OpenAI model presets** — add GPT-5.6 Sol, Terra, and Luna; make Terra the default and retire the GPT-5.4/5.2 presets.

A full release section:

## Version 0.0.438 (July 7, 2026)
- **Triggers (#562)** — user-owned webhooks that spawn agent sessions, plus report-per-run routing for scheduled tasks, under a new Automations page.
- **QVD indexing progress (#564)** — real per-file indexing progress with stop, file size, and duration.
- **WhatsApp fixes (#565)** — agent replies (text + data) are delivered back to WhatsApp, and the verification page shows WhatsApp branding instead of Slack.