Skip to content
TrustedSkillsbeta
Back to all skills

Prowler Commit

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

This skill uses Prowler to identify and report security misconfigurations in your cloud infrastructure commits, proactively safeguarding against vulnerabilities.

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-commit -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-commit/SKILL.md
Scanned
1 file, 167 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

The Prowler Commit skill assists users in crafting well-formatted and secure Git commit messages when working with cloud infrastructure code. It guides the user through a structured workflow, ensuring adherence to conventional commits standards (type(scope): description), limiting line lengths, and requiring explicit confirmation before committing changes. This helps maintain a clear audit trail and proactively prevents potential security misconfigurations introduced via commits.

When to use it

  • When making changes to cloud infrastructure code that need to be committed to version control.
  • To ensure commit messages follow the conventional commits format for improved readability and automation.
  • Before committing significant changes, especially those related to security or critical functionality.
  • When needing a structured approach to documenting the purpose of your code modifications.

Key capabilities

  • Enforces conventional commits formatting (e.g., feat(api): description).
  • Limits commit title line length to 72 characters.
  • Requires user confirmation before committing changes, displaying files and proposed message.
  • Provides guidance on choosing appropriate commit types (feat, fix, docs, chore, etc.) and scopes (api, ui, sdk, mcp, skills, ci, docs).
  • Offers examples of good and bad commit titles and body content.

Example prompts

  • "Analyze my changes and draft a commit message."
  • "Show me the proposed commit message for these modifications."
  • "What type and scope should I use for this change?"

Tips & gotchas

  • The skill relies on you having already made code changes using git status or similar commands.
  • Adherence to the conventional commits format is required for optimal results. Deviations will likely result in warnings or errors.
  • Be mindful of keeping commit titles concise and avoiding overly specific details within them.