.png)
4 months ago
16
If you're using Large Language Models (LLMs) to generate code, you might want to link your code commits to your conversations so your colleagues (or your future self) can understand the code's conversational context.
To do so, this repository includes a file called CLAUDE.md which provides instructions to Claude Code which kindly ask it to ...
- 🎯 Goal Track: Each conversation goal gets its own GitHub issue
- 📝 Log Conversations to Issues: All prompts and responses are logged with timestamps to the Goal's GitHub issue
- 🚀 Smart Commits: Generate Git commits & link them to their corresponding GitHub issues
The instructions teach Claude Code how to use the GitHub CLI & Git to to do so.
demo.mp4Note
The idea of linking code to its conversation isn't novel -
- Simon Willison has been linking his conversations to his LLM-generated code for some time now at simonw/tools, however, from what I can see (on 20th June 2025) he uses links to his web chats hosted by LLM providers. Ever since reading Simon's blog post The Perfect Commit, I've found it really helpful for my future self to link commits to broader context on GitHub Issues by including issue numbers in my commit messages.
- Simon Wardley has been talking about this style of conversational programming for years, I feel like this is in keeping with the spirit of Why the Fuss About Conversational Programming?
Warning
This tool is both experimental & non-deterministic. It merely asks an LLM to follow instructions, and makes no guarantees that the LLM will do so! However, that doesn't mean it's not useful.
You'll need three tools installed:
Note
If you're into Nix, then you'll just need one tool. Run ...
... & Nix will install the required tools for you by reading flake.nix
Then:
-
Use this repository as a template or Copy CLAUDE.md to your repository Click Use this template & follow the instructions
-
Authenticate with GitHub:
-
Start using Claude Code:
Now Claude Code should be smart enough to log your conversations to GitHub Issues
- Authentication issues: Run gh auth status to check GitHub CLI authentication
- Permission errors: Ensure you have write access to the repository
- Missing logs directory: Create it with mkdir logs
