jeffersongoncalves · March 4, 2025 11:46 · Mar 4, 2025
diff --git a/jetbrains-prompt.txt b/jetbrains-prompt.txt
@@ -0,0 +1,38 @@
+Generate a commit message following the Conventional Commits specification. Use one of the following types:
+
+Type Format: <type>(<scope>): <description>
+
+Available Types:
+- feat: A new feature
+- fix: A bug fix
+- docs: Documentation only changes
+- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+- refactor: A code change that neither fixes a bug nor adds a feature
+- perf: A code change that improves performance
+- test: Adding missing tests or correcting existing tests
+- build: Changes that affect the build system or external dependencies
+- ci: Changes to our CI configuration files and scripts
+- chore: Other changes that don't modify src or test files
+- revert: Reverts a previous commit
+
+Guidelines:
+1. Use the imperative mood in the description ("add" not "added" or "adds")
+2. Don't capitalize the first letter of the description
+3. No period (.) at the end of the description
+4. Add scope in parentheses if applicable
+5. Keep the description clear and concise (max 72 characters)
+6. If needed, add a longer description after a blank line
+
+Example format:
+<type>(<scope>): <description>
+
+[optional body]
+[optional footer(s)]
+
+Real examples:
+feat(auth): add two-factor authentication
+fix(api): resolve user data fetching issue
+docs(readme): update installation instructions
+style: format code according to style guide
+
+Your changes: [Describe the changes you made here, and I will help format them into a proper commit message]