gannonh/kata-skills

kata-whats-new

Show what's new in Kata since the installed version, displaying changelog entries, checking for Kata updates, or reviewing recent changes. Triggers include "what's new", "whats new", "show changes", "changelog", "recent changes", and "what changed".

First seen Feb 6, 2026

Installation

$ npx skills add gannonh/kata-skills --skill kata-whats-new

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from gannonh/kata-skills · top by installs.

npx skills add gannonh/kata-skills

Browse all from gannonh/kata-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.6.1
More metadata
version
1.6.1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,114 B
  • docs SUMMARY.md 271 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 19 installs

SKILL.md

<objective> Display changes between installed version and latest available version.

Shows version comparison, changelog entries for missed versions, and update instructions. </objective>

<process>

<step name="getinstalledversion"> Read installed version from VERSION file (checking plugin context first):

if [ -n "$CLAUDE_PLUGIN_ROOT" ]; then
  cat "$CLAUDE_PLUGIN_ROOT/VERSION" 2>/dev/null
fi

If VERSION file missing:

## Kata What's New

**Installed version:** Unknown

Your installation doesn't include version tracking.

**To reinstall:**
`/plugin install kata@kata-marketplace`

STOP here if no VERSION file. </step>

<step name="fetchremotechangelog"> Fetch latest CHANGELOG.md from GitHub:

Use WebFetch tool with:

  • URL: https://raw.githubusercontent.com/gannonh/kata/refs/heads/main/CHANGELOG.md
  • Prompt: "Extract all version entries with their dates and changes. Return in Keep-a-Changelog format."

If fetch fails: Fall back to local changelog:

cat "$CLAUDE_PLUGIN_ROOT/CHANGELOG.md" 2>/dev/null

Note to user: "Couldn't check for updates (offline or GitHub unavailable). Showing local changelog." </step>

<step name="parse_versions"> From the remote (or local) changelog:

  1. Extract latest version - First ## [X.Y.Z] line after ## [Unreleased]
  2. Compare with installed - From VERSION file
  3. Extract entries between - All version sections from latest down to (but not including) installed

Version comparison:

  • If installed == latest: "You're on the latest version"
  • If installed < latest: Show changes since installed version
  • If installed > latest: "You're ahead of latest release (development version?)"

</step>

<step name="display_output"> Format output clearly:

If up to date:

## Kata What's New

**Installed:** 1.4.26
**Latest:** 1.4.26

You're on the latest version.

[View full changelog](https://github.com/gannnonh/kata/blob/main/CHANGELOG.md)

If updates available:

## Kata What's New

**Installed:** 1.4.23
**Latest:** 1.4.26

---

### Changes since your version:

## [1.4.26] - 2026-01-20

### Added
- Feature X
- Feature Y

### Changed
- **BREAKING:** Changed Z behavior

## [1.4.25] - 2026-01-18

### Fixed
- Bug in feature A

---

[View full changelog](https://github.com/gannnonh/kata/blob/main/CHANGELOG.md)

**To update:**
`/plugin update kata@kata-marketplace`

Breaking changes: Surface prominently with BREAKING: prefix in the output. </step>

</process>

<success_criteria>

  • Installed version read from VERSION file
  • Remote changelog fetched (or graceful fallback to local)
  • Version comparison displayed clearly
  • Changes since installed version shown (if any)
  • Update instructions provided when behind

</success_criteria>