{"enrichment":{"faq":[{"a":"prowler-commit guides you through creating properly formatted commit messages following the conventional-commits standard. It analyzes your staged changes, generates a message with the correct type (feat, fix, etc.), scope, and description, then presents it for your review before executing the commit.","q":"How do I write a proper commit message with prowler-commit?"},{"a":"prowler-commit enforces the conventional-commits format, which structures messages as: type(scope): description. The type indicates the change category (feat, fix, docs, etc.), scope specifies the affected area, and description concisely explains what changed. This standard ensures consistency across your team's codebase.","q":"What format does prowler-commit use for git commits?"},{"a":"Yes. prowler-commit presents the formatted commit message for your explicit review and approval before executing any git commit operation. This confirmation step ensures you're satisfied with the message structure and content before changes are committed to your repository.","q":"Does prowler-commit require approval before committing?"},{"a":"prowler-commit analyzes your staged changes and automatically generates a commit message following professional standards and conventional-commits conventions. It determines the appropriate type and scope based on your modifications, then creates a properly formatted message ready for your confirmation.","q":"Can prowler-commit generate a commit message for my changes?"},{"a":"prowler-commit ensures all commits follow professional standards and team conventions by enforcing the conventional-commits format. This consistency improves code history readability, enables better automation (like changelog generation), and helps teams maintain uniform commit practices across projects.","q":"What are the benefits of using prowler-commit?"}],"shadow_tags":["git-workflow","commit-automation","code-standards","version-control","message-formatting","developer-tools","best-practices","scm-integration"],"summary_rewrite":"This skill drafts and executes git commits following the conventional-commits standard, enforcing structure with type, scope, and concise descriptions. It analyzes staged changes, presents a formatted message for review, and commits only after explicit user approval."},"files":[{"bytes":4088,"path":"skills/prowler-commit/SKILL.md","sha256":"59528bdd470cdbe593ed7de3bf345b0e4cb0d208f2cd1213f5a05b016a72baf4","url":"https://skillfed.io/files/prowler-cloud/prowler/prowler-commit/40a42d67/SKILL.md"}],"id":"prowler-cloud/prowler/prowler-commit","links":{"html":"https://skillfed.io/prowler-cloud/prowler/prowler-commit","md":"https://skillfed.io/prowler-cloud/prowler/prowler-commit.md","repo":"https://github.com/prowler-cloud/prowler"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":2285,"language":"Python","last_updated":"2026-07-27","license":"Apache-2.0","name":"prowler-commit","publisher":"prowler-cloud","stars":14491},"relations":{"similar":[{"id":"prowler-cloud/prowler/prowler"},{"id":"prowler-cloud/prowler/prowler-pr"},{"id":"prowler-cloud/prowler/prowler-changelog"},{"id":"prowler-cloud/prowler/skill-sync"},{"id":"prowler-cloud/prowler/prowler-mcp"},{"id":"prowler-cloud/prowler/prowler-test-api"},{"id":"prowler-cloud/prowler/prowler-api"},{"id":"patricio0312rev/skills/conventional-commits"},{"id":"bastos/skills/conventional-commits"},{"id":"yonatangross/orchestkit/commit"}]},"slug":{"owner":"prowler-cloud","repo":"prowler","skill":"prowler-commit"},"version":"40a42d67"}