Skip to content
TrustedSkillsbeta
Back to all skills

Prowler Changelog

Checked
prowler-cloud·vlatest·writing·Apache-2.0

Generates detailed changelogs from Prowler scans, streamlining documentation and highlighting infrastructure changes for improved transparency.

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 prowler-cloud/prowler --skill prowler-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

prowler-cloud

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 prowler-cloud/prowler at 03502c2426.

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

Commit
03502c2426
Manifest
skills/prowler-changelog/SKILL.md
Scanned
2 files, 233 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 generates detailed changelogs for Prowler, a cloud security auditing framework. It follows specific formatting rules and conventions outlined by keepachangelog.com to ensure consistency and clarity in documenting changes across different components (UI, API, MCP Server, SDK). The generated changelog entries include links to relevant pull requests on GitHub, providing traceability for each modification.

When to use it

  • When releasing a new version of Prowler or any of its core components.
  • To automatically populate the CHANGELOG.md files within various Prowler directories (ui/, api/, mcp_server/, prowler/).
  • For maintaining accurate and up-to-date documentation of infrastructure changes.
  • When needing to adhere to strict changelog formatting guidelines for transparency and collaboration.

Key capabilities

  • Generates changelogs following the keepachangelog.com format.
  • Uses specific emoji prefixes (🚀, 🔄, ⚠️, ❌, 🐞, 🔐) to categorize changes.
  • Includes links to associated GitHub pull requests for each entry.
  • Maintains a defined section order: Added → Changed → Deprecated → Removed → Fixed → Security.
  • Supports semantic versioning (PATCH, MINOR, MAJOR) based on the type of change.

Example prompts

  • "Generate a changelog entry for this pull request: [link to PR]"
  • "Create a 'Fixed' section entry in the SDK changelog for bug fix #1234."
  • "Add a new 'Added' entry at the bottom of the API changelog, linking to pull request #5678."

Tips & gotchas

  • Entries must always be added at the bottom of each section.
  • Preserving the correct section order is critical when generating "UNRELEASED" changelogs.
  • Once a version is released (tagged in Prowler), its corresponding changelog section should not be modified.