prowler-commit
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.
prowler-commit creates professional git commits in conventional-commits format with user confirmation before execution.
AI-generated summary based on this skill's SKILL.md
Install
prowler-cloud/prowler/prowler-commit · repository language: Python
git clone https://github.com/prowler-cloud/prowler
cp -r prowler/skills/prowler-commit ~/.claude/skills/prowler-commitnpx skillfed install prowler-cloud/prowler/prowler-commitFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I write a proper commit message with prowler-commit?
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.
What format does prowler-commit use for git commits?
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.
Does prowler-commit require approval before committing?
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.
Can prowler-commit generate a commit message for my changes?
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.
What are the benefits of using prowler-commit?
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.
SKILL.md
rendered from the published skill — quoted content, verbatim
Critical Rules
- ALWAYS use conventional-commits format:
type(scope): description - ALWAYS keep the first line under 72 characters
- ALWAYS ask for user confirmation before committing
- NEVER be overly specific (avoid counts like "6 subsections", "3 files")
- NEVER include implementation details in the title
- NEVER use
-nflag unless user explicitly requests it - NEVER use
git push --forceorgit push -f(destructive, rewrites history) - NEVER proactively offer to commit - wait for user to explicitly request it
Commit Format
type(scope): concise description
- Key change 1
- Key change 2
- Key change 3
Types
| Type | Use When |
|---|---|
feat |
New feature or functionality |
fix |
Bug fix |
docs |
Documentation only |
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
skills/prowler-commit/SKILL.md