Generate Changelog

code.generate_changelog

ProductionBounded custom (Class B)Deterministicstrictfastv1.0.0

No network

Overview

When you already have structured change entries, we render Markdown release notes with Keep a Changelog headings and grouping rules you control. Every piece of entry text is Markdown-escaped, so a description can never inject a heading, link, or HTML into your changelog. We do not read Git history, summarize prose, or look up issue trackers — do not use this when the entries must be inferred from commit messages alone.

Release notes should be deterministic and injection-safe, not guessed from prose. We render the Markdown you can paste into a changelog file.

Reliability

STRICT and deterministic for identical inputs. Domain errors (not retryable; fix the input — unchanged retry will not succeed): CHANGELOG_ENTRY_INVALID (version, date, or entry shape is invalid — correct the fields); CHANGELOG_DUPLICATE_ENTRY (duplicate entry id when duplicateIdPolicy=reject — dedupe or change policy); CHANGELOG_OUTPUT_TOO_LARGE (too many entries or output exceeds limit — reduce input).

Context footprint

Returns Markdown, structured groups, warnings, contentHash, and _meta. A successful call costs 1 execution credit.

When to use it

When entries are already structured and you need formatted release notes.

When you need to parse Git history or summarize commit messages.

Scope

Note

Renders deterministic Markdown changelog sections from structured entries.

Non-goals

Does not access Git
Does not summarize or invent prose
Does not look up issues
Does not modify repositories

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

formattinggeneration

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input2 MB

How we handle your data

Sensitive output possible

What this means

This skill may receive sensitive content and may return submitted, transformed, extracted, or reformatted content.

Squillify guarantees

Runs inside Squillify
This skill runs inside Squillify.
Payloads are not sent to an external service by this skill.
Squillify does not permanently store submitted payloads.
Telemetry records metadata only, not submitted content.
Submitted payloads are not used for training.
Submitted payloads are not reviewed by humans.
This skill does not target sensitive data.
The response may contain submitted or transformed content.

Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

Field	Type	Required	Description
version	string	Yes	Safe release heading label.
date	string	No	Optional ISO release date; omit it when the heading should have no date.
entries	array	Yes	From 1 through 10,000 structured change entries, each a closed description plus optional type, breaking, id, issues and authors.
profile	string	No	Rendering profile receipt; omit it for keep_a_changelog.
includeCommitIds	boolean	No	Whether commit identifiers are rendered; omit it for true.
emptyGroupPolicy	string	No	Empty-group behavior; omit it for omit.
duplicateIdPolicy	string	No	Duplicate-id behavior; omit it for dedupe.
options	object	No	Closed ordering and inclusion options; omit it to apply every documented default.

Output schema

Field	Type	Required	Description
markdown	string	Yes	Rendered Markdown release section.
groups	array	Yes	From 0 through 7 rendered changelog groups, each a closed group id, title and entries array.
warnings	array	Yes	From 0 through 10,000 bounded warning objects with code, message and severity.
contentHash	string	Yes	SHA-256 digest of rendered Markdown.
_meta	object	Yes	Closed rendering-profile and entry-count receipt with the applied profile label and entriesRendered.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"code.generate_changelog","input":{"version":"1.4.0","entries":[{"type":"fix","description":"x"}]}}'

Integrations

TypeScript SDK

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("code.generate_changelog", {"entries":[{"type":"feat","id":"abc1234","description":"add hourly usage rollups"}],"date":"2026-07-12","version":"1.4.0"});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.
CHANGELOG_ENTRY_INVALID	400	No	The request payload failed this skill's input validation.
CHANGELOG_DUPLICATE_ENTRY	400	No	The request payload failed this skill's input validation.
CHANGELOG_OUTPUT_TOO_LARGE	429	No	A size, quota, rate, or time limit was exceeded.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not access Git
Does not summarize or invent prose
Does not look up issues
Does not modify repositories
Summarizing free-form commit messages
Fetching issue metadata from trackers

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "code.generate_changelog",
  "input": {
    "entries": [
      {
        "type": "feat",
        "id": "abc1234",
        "description": "add hourly usage rollups"
      }
    ],
    "date": "2026-07-12",
    "version": "1.4.0"
  }
}

Examples

Feature entry with commit id

Inputjson

{
  "entries": [
    {
      "type": "feat",
      "id": "abc1234",
      "description": "add hourly usage rollups"
    }
  ],
  "date": "2026-07-12",
  "version": "1.4.0"
}

Expected outputjson

{
  "warnings": [],
  "groups": [
    {
      "group": "feat",
      "title": "Added",
      "entries": [
        {
          "id": "abc1234",
          "type": "feat",
          "scope": null,
          "description": "add hourly usage rollups",
          "breaking": false
        }
      ]
    }
  ],
  "_meta": {
    "entriesRendered": 1,
    "profile": "keep_a_changelog"
  },
  "contentHash": "sha256:bcf15de6ee4d23c265b74dde839a85e6c60a89b067fb0f7fbc1d67a5557bb61b",
  "markdown": "## [1.4.0] - 2026-07-12\n\n### Added\n\n- add hourly usage rollups `abc1234`\n\n"
}

Breaking change routes to Breaking Changes group