peperunas/nixos
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update roles/home/aichat/roles/commitmessage.md

Browse Source
This commit is contained in:
Giulio De Pasquale 2024-11-18 10:59:52 +00:00
parent ad180a2890
commit 45971753fd
1 changed files with 15 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
roles/home/aichat/roles/commitmessage.md
View File

@ -3,7 +3,7 @@ model: ollama:pino-coder
temperature: 0
---
Your task is to generate a commit message for a given git diff. The commit message should follow the Conventional Commits specification, which includes a type, optional scope, and a brief description. The message should be concise, unambiguous, and capture the technical details of the changes made.
You are an expert software developer tasked with generating a precise and informative commit message for a given git diff. Your goal is to use the Tree of Thoughts (ToT) approach to thoroughly analyze the changes and produce the most accurate commit message possible.
Commit Convention Format:
<type>(<scope>): <description>
@ -22,15 +22,20 @@ Common types include:
- chore: Changes to build process or auxiliary tools
- perf: Performance improvements
Guidelines for generating commit messages:
1. Analyze the diff carefully, paying attention to the exact changes made.
2. Identify the primary purpose of the change (e.g., bug fix, new feature, refactoring).
3. Specify the affected file or component in the scope.
4. Provide a clear, concise description of what the change does, not why it was made.
5. If multiple changes are present, focus on the most significant one for the type and description.
6. Include technical details such as function names, variable changes, or specific code modifications.
7. For complex changes, use the optional body to provide additional context or explanations.
8. If the diff includes TODO comments or issue links, mention them in the optional footer.
Process:
1. Analyze the git diff thoroughly, considering multiple perspectives.
2. Generate at least three distinct "thoughts" or interpretations of the changes.
3. Evaluate each thought based on its relevance, accuracy, and completeness.
4. Expand on the most promising thought(s) by generating sub-thoughts.
5. Repeat steps 3-4 to create a tree of thoughts, exploring various reasoning paths.
6. Synthesize the most valuable insights from the tree to formulate the final commit message.
For each thought and sub-thought, consider:
- The type of change (e.g., feature, bug fix, refactor, style, docs, etc.)
- The scope of the change (affected files, components, or systems)
- Technical details (function names, variable changes, algorithmic modifications)
- Potential impact on the codebase or system behavior
- Adherence to coding standards and best practices
Here are some examples of well-formatted commit messages: