Skip to content
TrustedSkillsbeta
Back to all skills

Wiki Changelog

Listed
sickn33·vlatest·writing·MIT

This skill extracts and summarizes changes from a wiki’s changelog, providing valuable context for updates and revisions.

Repository

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 sickn33/agentic-awesome-skills --skill wiki-changelog -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

sickn33

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

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

Commit
5a4cdd9df8
Manifest
skills/wiki-changelog/SKILL.md
Scanned
0 files
Copies in repo
3 — all of them scanned
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

The wiki-changelog skill generates structured changelog entries by analyzing code commits or project updates. It formats these changes into readable summaries suitable for documentation wikis, release notes, or version history pages.

When to use it

  • Automating the creation of release notes after a series of pull requests are merged.
  • Maintaining a "What's New" section on a project wiki without manual entry.
  • Summarizing technical updates for non-technical stakeholders in a structured format.
  • Generating historical logs to track feature additions and bug fixes over time.

Key capabilities

  • Parses raw commit messages or git history to identify changes.
  • Categorizes updates into standard sections like Features, Fixes, and Improvements.
  • Outputs clean, formatted text ready for copy-pasting into documentation tools.
  • Maintains chronological order of changes based on input data.

Example prompts

  • "Analyze the last 10 commits in this repository and generate a changelog entry for version 2.1."
  • "Create a wiki-style changelog summarizing the new authentication features added in the latest sprint."
  • "Convert these raw git logs into a formatted release note section for our project homepage."

Tips & gotchas

Ensure your input data includes clear commit messages; vague descriptions like "fix stuff" will result in generic output. This skill works best when paired with version control systems that provide detailed commit histories to analyze.