kit-release-notes

Write release notes or a changelog entry from the commits and merged pull or merge requests since the previous release, grouped for users and following the project's existing changelog format. Use when the user asks for release notes, a changelog entry, a "what changed since vX" summary, or to update CHANGELOG.md before a release. Do not use for tagging, publishing, or creating the release itself, for pull request descriptions (use kit-pull-request), or for general documentation (use kit-documentation).

What does this entry provide?

kit-release-notes is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Release notes ## 1. Find the range and the format - Find the previous release: the latest tag (`git describe --tags --abbrev=0`), the last version in `CHANGEL. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding kit-release-notes to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: GitHub Skill Search
Quality: 58/100
Install method: codex
Repo: zekhoi/claude
Repo updated: Nov 6, 2026

Install command

codex skill install zekhoi/claude

Install method: codex

Review the upstream source before running this command.

GitHub project View SKILL.md

Quality

Repo stars

Repo updated

Unknown

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.

Security signals

Scan coverage: Install metadata and the indexed document body.

Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.

Discovery note

# Release notes ## 1. Find the range and the format - Find the previous release: the latest tag (`git describe --tags --abbrev=0`), the last version in `CHANGELOG.md`, or the versi

Report an issue with this listing