Skip to content

feat: improve the prompt based on last evaluation run #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
billybonks merged 1 commit into from
Mar 20, 2025
Merged

feat: improve the prompt based on last evaluation run #25

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 22 additions & 11 deletions lib/committer/config/defaults/commit_message_only.prompt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,17 +12,6 @@ Here are the available scopes (if any):
{{SCOPES}}
</scopes>

Please follow these instructions to generate the commit message:

1. Analyze the git diff and determine the most appropriate commit type from the following options:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code
- 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
- chore: Changes to the build process or auxiliary tools and libraries


2. Adhere to these message guidelines:
Expand All @@ -35,4 +24,26 @@ Please follow these instructions to generate the commit message:
- If a scope is available: <type>(<scope>): <description>
- If no scope is available: <type>: <description>


Please follow these instructions to generate the commit message:

if such and such changes its docs b ut if commit also has such then its a feat
Copy link

@managerbot-app managerbot-app bot Mar 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line contains confusing/unclear text: 'if such and such changes its docs b ut if commit also has such then its a feat'. Consider clarifying or rewording this guidance for better clarity.


1. Analyze the git diff and determine the most appropriate commit type from the following options:
- feat: A new feature these changes ARE NOT in the docs directory
- fix: A bug fix these changes ARE NOT in the docs directory
- docs: Documentation only changes for example changes that happen in docs directory
- style: Changes that do not affect the code execution (e.g., white-space, formatting, missing semi-colons, etc.) usually done by linters
- refactor:
Copy link

@managerbot-app managerbot-app bot Mar 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The refactor description is incomplete or poorly formatted. The sentence structure seems off with 'just how the code is written executed'.

- A code change that does not change the behaviour of the code at all, just how the code is written executed,
- modifing error messages is not a refactor
- if parts of the code is removed and no alternative in place IT IS NOT A REFACTOR
- 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 the CI configuration files and scripts
- these changes should not change the way that the code is built otherwise its build
Copy link

@managerbot-app managerbot-app bot Mar 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 'ci' description contains a grammatical error: 'its build' should be 'it's build'.



Respond ONLY with the commit message line, nothing else.
Loading