Skip to content

Commit bf2fbd0

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

File tree

1 file changed

+13
-2
lines changed

1 file changed

+13
-2
lines changed

docs/other/ai-tools.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,18 @@
11
# AI tools
22
> Recommended tools to use AI to generate your commit message
33
4+
## My own projects
5+
6+
I created this project to use a local LLM or an OpenAI-compatible API to generate commit messages as a CLI tool:
7+
8+
- [MichaelCurrin/llm-commit-msg-py](https://github.com/MichaelCurrin/llm-commit-msg-py)
9+
10+
And as a VS Code extension but still experimental:
11+
12+
- [llm-commit-msg-vs-code](https://github.com/MichaelCurrin/llm-commit-msg-vs-code)
13+
14+
415
## VS Code extensions
5-
> Using AI to generate commit messages
616

717
Search for "gpt commit" in the extensions marketplace and you'll see plenty of extensions that use GPT to write your commit message.
818

@@ -26,6 +36,7 @@ See this Rust-based tool which runs on the command-line.
2636

2737
- [gptcommit](https://github.com/zurawiki/gptcommit)
2838

39+
2940
## Local LLMs
3041

31-
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.
42+
To get around the limitations of the above, especially for private codebases, you could use a locally run LLM (like Ollama) instead of ChatGPT. The VS Code extensions I looked at don't support a custom OpenAI URL like a local URL, but they could be modified for this or maybe so other extensions do cover it.

0 commit comments

Comments
 (0)