EHeh9·Mar 18, 2023
I think we’re talking about different projects. This one just gives you a text output of an entire repo.
https://github.com/mpoon/gpt-repository-loader
In Stanford Alpaca web demo suspended “until further notice”mpoon
gpt-repository-loader
Python2023–2023
mpoon / gpt-repository-loader
gpt-repository-loader
Convert code repos into an LLM prompt-friendly format. Mostly built by GPT-4.
7Distinct people
8Mentions
0Explicit recommenders
3KGitHub stars
What to know before exploring
What it is
Convert code repos into an LLM prompt-friendly format. Mostly built by GPT-4.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:00:59 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week8 dated mentions
Observed mentions: 2023-03-17 00:59:54 UTC to 2023-05-12 22:13:18 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Mar 13 | 2023-03-13 00:00:00 UTC | 2023-03-20 00:00:00 UTC | 5 | 1 | 4 |
| Mar 20 | 2023-03-20 00:00:00 UTC | 2023-03-27 00:00:00 UTC | 1 | 1 | 0 |
| Mar 27 | 2023-03-27 00:00:00 UTC | 2023-04-03 00:00:00 UTC | 0 | 0 | 0 |
| Apr 3 | 2023-04-03 00:00:00 UTC | 2023-04-10 00:00:00 UTC | 0 | 0 | 0 |
| Apr 10 | 2023-04-10 00:00:00 UTC | 2023-04-17 00:00:00 UTC | 0 | 0 | 0 |
| Apr 17 | 2023-04-17 00:00:00 UTC | 2023-04-24 00:00:00 UTC | 0 | 0 | 0 |
| Apr 24 | 2023-04-24 00:00:00 UTC | 2023-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 1 | 2023-05-01 00:00:00 UTC | 2023-05-08 00:00:00 UTC | 1 | 0 | 1 |
| May 8 | 2023-05-08 00:00:00 UTC | 2023-05-15 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
5 sourcesSo I have been toying with an AutoPR GitHub Action for a bit but seeing this spurred me to actually put it into a format for y'all to try. It uses GPT-4 to automatically generate code based on issues in your repo and opens pull requests for those changes.
https://github.com/irgolic/AutoPR/
What AutoPR can do:
- Automatically generates code based on issues in your repo.
- Opens PRs for the generated code, making it easy to review and merge changes.
By using this GitHub Action, you can skip the manual steps of prompt design, and let the AI handle code generation and PR creation for you.
Here's how I used it to make the license for itself: https://github.com/mpoon/gpt-repository-loader/issues/23
Feel free to give it a try, and I would love to hear your feedback! It's still in alpha and it works for straightforward tasks, but I have a plan to
Read the rest
scale it up. Let's see how far we can push GPT-4 and create a more efficient development process together.
https://github.com/mpoon/gpt-repository-loader/pull/17/ If you look at this PR, he had ChatGPT write the tests for him.
He wrote the issue on https://github.com/mpoon/gpt-repository-loader/issues/16 and summarized https://github.com/mpoon/gpt-repository-loader/discussions/1...
"Open an issue describing the improvement to make
Construct a prompt - start with using gpt_repository_loader.py on this repo to generate the repository context, then append the text of the opened issue after the --END-- line."
Feels like it needs to add a little Github client to be able to automatically append the text of issues at the end of the output. I'm sure ChatGPT can write a Github client in Python no problem.
In Show HN: GPT Repo Loader – load entire code repos into GPT promptsShow HN: GPT Repo Loader – load entire code repos into GPT prompts
I was getting tired of copy/pasting reams of code into GPT-4 to give it context before I asked it to help me, so I started this small tool. In a nutshell, gpt-repository-loader will spit out file paths and file contents in a prompt-friendly format. You can also use .gptignore to ignore files/folders that are irrelevant to your prompt.
gpt-repository-loader as-is works pretty well in helping me achieve better responses. Eventually, I thought it would be cute to load itself into GPT-4 and have GPT-4 improve it. I was honestly surprised by PR#17. GPT-4 was able to write a valid an example repo and an expected output and throw in a small curveball by adjusting .gptignore. I did tell GPT the output file format in two places: 1.) in the preamble when I prompted it to make a PR for issue #16 and 2.) as a string in gpt_repository_loader.py, both
Read the rest
of which are indirect ways to infer how to build a functional test. However, I don't think I explained to GPT in English anywhere on how .gptignore works at all!
I wonder how far GPT-4 can take this repo. Here is the process I'm following for developing:
- Open an issue describing the improvement to make
- Construct a prompt - start with using gpt_repository_loader.py on this repo to generate the repository context, then append the text of the opened issue after the --END-- line.
- Try not to edit any code GPT-4 generates. If there is something wrong, continue to prompt GPT to fix whatever it is.
- Create a feature branch on the issue and create a pull request based on GPT's response.
- Have a maintainer review, approve, and merge.
I am going to try to automate the steps above as much as possible. Really curious how tight the feedback loop will eventually get before something breaks!