Skip to content
TrustedSkillsbeta
Back to all skills

Changelog Review

Checked
laurigates·vlatest·writing·MIT

Analyzes changelogs for clarity, completeness, and consistency against specified guidelines, improving release notes quality.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add laurigates/claude-plugins --skill changelog-review -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

laurigates

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned laurigates/claude-plugins at 45d1d7dcf6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
4 files, 843 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill analyzes Claude Code releases to help developers understand their impact on existing plugins. It identifies breaking changes, new features, deprecations, and other updates that may require plugin modifications or enhancements. The analysis is categorized by impact level (High, Medium, Low) and provides specific actions recommended for each category.

When to use it

  • After a Claude Code release when you need to quickly assess the potential impact on your plugins.
  • To proactively identify deprecations before they affect plugin functionality.
  • When developing new plugins that leverage Claude Code features, ensuring alignment with current best practices.
  • To track changes related to specific areas of Claude Code, such as Hooks or Permissions.

Key capabilities

  • Identifies breaking changes requiring immediate updates.
  • Highlights new features that plugins can utilize.
  • Tracks deprecations and suggests removal of deprecated usage.
  • Categorizes changelog entries by impact level (High, Medium, Low).
  • Maps Claude Code areas to affected plugins based on a predefined matrix.
  • Maintains version tracking information in a .claude-code-version-check.json file.

Example prompts

  • "Analyze the latest Claude Code changelog and tell me what actions I need to take regarding my hooks-plugin."
  • "What new features were introduced in the last Claude Code release that could benefit plugins?"
  • "Show me any deprecations listed in the changelog that might affect plugins using hooks."

Tips & gotchas

  • This skill is specifically designed for analyzing Claude Code changelogs.
  • The impact matrix provides a guide, but manual review of changes may still be necessary.
  • The .claude-code-version-check.json file stores version tracking information and should be preserved.