Live data from Hacker News

Launch HN: Sweep (YC S23) – A bot to create simple PRs in your codebase

github.com

81–90 of 117 posts

Re: Launch HN: Sweep (YC S23) – A bot to create simple PRs in your codebase

#81
I'm wondering what will happen if we let ChatGPT review these PRs created by ChatGPT.

Yes, We made a small tool to help developer review their PR. Seems a great supplement for Sweep AI.

Build your own PR review bot in 3 minutes here: https://github.com/flows-network/github-pr-summary

Re: Launch HN: Sweep (YC S23) – A bot to create simple PRs in your codebase

#82
post #81

I'm wondering what will happen if we let ChatGPT review these PRs created by ChatGPT. Yes, We made a small tool to help developer review their PR. Seems a great supplement for Sweep AI. Build your own PR review bot in 3 minutes here: https://github.com/flows-network/github-pr-summary

Cool! Sweep actually already does this before the PR is shown to the user. I agree it might help to expose some of the Sweep generated reviews (which we did before)

Re: Launch HN: Sweep (YC S23) – A bot to create simple PRs in your codebase

#84
post #83

So next up, we'll be hiring people to put the bugs into the code base, so AI companies like this can stay in business, right? No bugs means no AI to fix bugs.

Haha, Sweep also handles small features and writing documentation! There's a huge scope of software work besides fixing bugs, and to be fair, most of the work in bug fixing is not in the actual coding but thinking about the problem.

Re: Launch HN: Sweep (YC S23) – A bot to create simple PRs in your codebase

#86

Earlier quoted context omitted.

I just had it fix some outdated copy in a part of the UI. The nice thing is I didn't have to find the file myself, I just described what was wrong like I would a junior eng and let it find and fix it. Worked on the first try!

That's exactly the use case we want. We also let you specify the file path (ex: "main.py"). We noticed that Sweep's search works way better if there are comments, because the comments match up really well with the search queries (language language is easier than language code)

May be rewriting user's description might help you match code better?

Similar to the prompt engineering for previous era GPT completion models.

Re: Launch HN: Sweep (YC S23) – A bot to create simple PRs in your codebase

#87

How do you approach the problem of what files to look into to fix a bug? Just embeddings doesn't seem to cut it.

We use some simple ranking heuristics detailed here: https://docs.sweep.dev/blogs/building-code-search

One thing we also do is match any files mentioned in the issue. So if you mention sweepai/api.py, we'll find that and add it to the fetched files. There's still more work to be done here, so look out for those!

Likely file name based scoring, and other rules + finetuned retrieval models (opt-in of course)

Re: Launch HN: Sweep (YC S23) – A bot to create simple PRs in your codebase

#88

Earlier quoted context omitted.

That's exactly the use case we want. We also let you specify the file path (ex: "main.py"). We noticed that Sweep's search works way better if there are comments, because the comments match up really well with the search queries (language language is easier than language code)

May be rewriting user's description might help you match code better? Similar to the prompt engineering for previous era GPT completion models.

We do end up doing a GPT based rewrite. The initial description is really valuable too though, and we want to keep that throughout the workflow. It's kind of similar to a spelling correction or query intent system. If it's high confidence you can override their query, but ideally you use the original one too.
Post reply on HN