prowler-changelog

Manage changelog entries for Prowler components following keepachangelog.com format.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/brivaro/brivaro-ai-wizard --skill prowler-changelog-brivaro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prowler-changelog
Source: https://github.com/brivaro/brivaro-ai-wizard/tree/main/skills/prowler-changelog
Command: npx skills add https://github.com/brivaro/brivaro-ai-wizard --skill prowler-changelog-brivaro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill standardizes and automates the process of creating and maintaining changelog entries for Prowler components, ensuring consistency and adherence to best practices.

Core Features & Use Cases

  • Changelog Management: Follows the keepachangelog.com format for clear and structured release notes.
  • Component Tracking: Manages changelogs for UI, API, MCP Server, and SDK components.
  • Automated Entry: Provides clear instructions and examples for adding new entries based on PR changes.
  • Use Case: When a new feature is merged via a Pull Request, this Skill guides the developer to add a concise, correctly formatted entry to the appropriate CHANGELOG.md file, ensuring all releases are well-documented.

Quick Start

Add a new changelog entry for a feature merged in the latest PR.

Frequently Asked Questions about prowler-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format changelog entries for Prowler components?

You format Prowler changelog entries using the keepachangelog.com structure, organizing release notes by Added, Changed, Deprecated, Removed, Fixed, and Security categories to maintain clear versioning documentation.

What is the best way to manage release notes for multiple components like UI and API?

Managing release notes for multiple components involves tracking UI, API, MCP Server, and SDK changes separately while enforcing semantic versioning rules and keepachangelog formatting across all documentation files.

How do I add a new changelog entry after merging a feature pull request?

After merging a feature pull request, you add a concise, correctly formatted entry to the appropriate CHANGELOG.md file, placing it under the correct semantic version and keepachangelog category.

Does this changelog management approach enforce semantic versioning rules?

Yes, this changelog management approach enforces semantic versioning rules to ensure proper formatting and versioning consistency across all Prowler component release documentation.

Can I use keepachangelog format for organizing release documentation across different software components?

Yes, the keepachangelog format supports organizing release documentation across different software components by providing structured guidelines for adding, modifying, and organizing entries by specific component types like UI and API.

Why does my changelog entry need to follow a specific format when documenting Prowler releases?

Your changelog entry must follow a specific format when documenting Prowler releases to ensure clarity and consistency, making release notes easier to read, maintain, and parse across all component versions.