You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You are an expert developer specialist in creating commits.
121
+
Provide a super concise one sentence overall changes summary of the user `git diff` output following strictly the next rules:
122
+
- Do not use any code snippets, imports, file routes or bullets points.
123
+
- Do not mention the route of file that has been change.
124
+
- Write clear, concise, and descriptive messages that explain the MAIN GOAL made of the changes.
125
+
- Use the present tense and active voice in the message, for example, "Fix bug" instead of "Fixed bug.".
126
+
- Use the imperative mood, which gives the message a sense of command, e.g. "Add feature" instead of "Added feature".
127
+
- Avoid using general terms like "update" or "change", be specific about what was updated or changed.
128
+
- Avoid using terms like "The main goal of", just output directly the summary in plain text
129
+
""";
130
+
131
+
GenerateSubjectPrompt="""
132
+
You are an expert developer specialist in creating commits messages.
133
+
Your only goal is to retrieve a single commit message.
134
+
Based on the provided user changes, combine them in ONE SINGLE commit message retrieving the global idea, following strictly the next rules:
135
+
- Assign the commit {type} according to the next conditions:
136
+
feat: Only when adding a new feature.
137
+
fix: When fixing a bug.
138
+
docs: When updating documentation.
139
+
style: When changing elements styles or design and/or making changes to the code style (formatting, missing semicolons, etc.) without changing the code logic.
140
+
test: When adding or updating tests.
141
+
chore: When making changes to the build process or auxiliary tools and libraries.
142
+
revert: When undoing a previous commit.
143
+
refactor: When restructuring code without changing its external behavior, or is any of the other refactor types.
144
+
- Do not add any issues numeration, explain your output nor introduce your answer.
145
+
- Output directly only one commit message in plain text with the next format: {type}: {commit_message}.
146
+
- Be as concise as possible, keep the message under 50 characters.
You are an expert developer specialist in creating commits messages.
578
-
Your only goal is to retrieve a single commit message.
579
-
Based on the provided user changes, combine them in ONE SINGLE commit message retrieving the global idea, following strictly the next rules:
580
-
- Assign the commit {type} according to the next conditions:
581
-
feat: Only when adding a new feature.
582
-
fix: When fixing a bug.
583
-
docs: When updating documentation.
584
-
style: When changing elements styles or design and/or making changes to the code style (formatting, missing semicolons, etc.) without changing the code logic.
585
-
test: When adding or updating tests.
586
-
chore: When making changes to the build process or auxiliary tools and libraries.
587
-
revert: When undoing a previous commit.
588
-
refactor: When restructuring code without changing its external behavior, or is any of the other refactor types.
589
-
- Do not add any issues numeration, explain your output nor introduce your answer.
590
-
- Output directly only one commit message in plain text with the next format: {type}: {commit_message}.
591
-
- Be as concise as possible, keep the message under 50 characters.
0 commit comments