prowler-commit_skill

Overview

This skill creates professional git commits following the Conventional Commits format and Prowler conventions. It drafts concise commit titles under 72 characters and a focused bullet list of key changes. It always asks for explicit user confirmation before performing the commit.

How this skill works

When you ask to commit after finishing code changes, the skill inspects the working tree and recent commit history to choose an appropriate commit type and scope. It drafts a one-line title in the form type(scope): description and, when needed, a short body with 2–5 high-level bullet points. It shows the files to be committed and the proposed message, then waits for your confirmation before running the git commit commands.

When to use it

• After completing code changes and you want a conventional-commits message
• When you need help selecting type and scope for a commit
• Before committing changes across multiple files or scopes
• When you want a concise, review-friendly commit summary
• When you want to avoid including implementation details in the title

Best practices

• Keep the title under 72 characters and avoid implementation specifics
• Use the recommended type and scope mapping (feat, fix, docs, chore, refactor, test, perf, style)
• Include 2–5 high-level bullet points for multi-file or multi-change commits
• Omit a scope when multiple scopes or root-level files are affected
• Always confirm the proposed message before the skill executes git commit

Example use cases

• Add a retry mechanism in the SDK and produce a feat(sdk) commit
• Fix a dashboard loading bug and draft fix(ui) with key changes
• Update installation docs and generate docs: update installation guide
• Refactor internal modules without claiming a feature using refactor(sdk)
• Bump CI configuration or dependencies with chore(ci) messages