Skip to content

Commit f82fa9c

Browse files
committed
docs: update ai-tools.md
1 parent a41e7e2 commit f82fa9c

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

docs/other/ai-tools.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
# AI tools
2-
> Using AI to generate commit messages
2+
> Recommended tools to use AI to generate your commit message
33
4-
## AI-based extensions
4+
## VS Code extensions
5+
> Using AI to generate commit messages
56
67
Search for "gpt commit" in the extensions marketplace and you'll see plenty of extensions that use GPT to write your commit message.
78

@@ -19,6 +20,12 @@ You can also try [Codeium](https://codeium.com/download) extension which has a l
1920
- You need to a ChatGPT API key and to pay for a premium subscription.
2021
- Limited acccuracy - I don't know if GPT is powerful enough to figure out the context of what you are doing and intend to write based on a diff only, as some of the reasoning for a change won't be covered by code itself but by real world events and requirements. You can pass more unchanged files from you codebase in an extension to the AI but this costs more money and won't always help.
2122

23+
## CLI tool
24+
25+
See this Rust-based tool which runs on the command-line.
26+
27+
- [gptcommit](https://github.com/zurawiki/gptcommit)
28+
2229
## Local LLMs
2330

2431
To get around the limitations of the above, especially for private codebases, you could use a locally run LLM (like Ollama) instead of ChatGPT. Perhaps there are extensions which support this.

0 commit comments

Comments
 (0)