@charliermarsh Honestly I often feel the opposite because our Claude setup with robobun is really good and usually their LLM setup isn’t as good

This pull request could have been a loop into auto review and merged based on an internal slack channel for feedback.

@jarredsumner Oh for contributors yes

@charliermarsh This pull request could have been a force push to main

@charliermarsh This PR could have been the prompt used + model

@charliermarsh this pull request could have been a working microservice.

@charliermarsh This user could’ve been a SKILL.md

@jarredsumner @charliermarsh Is there somewhere to file issues against the claude web UI and claude code so that claude can fix them

@jarredsumner @charliermarsh What if I just use Qwen to get around that problem

@jarredsumner @charliermarsh Blog post my guy

@charliermarsh I know rite??

But unfortunately we live in this world:

> In a SOC 2 audit, every software deployment or modification must have an associated issue ticket and a linked, peer-reviewed Pull Request (PR).

so sometimes... yes I'll take the Issue

@jarredsumner @charliermarsh blog post? 😇

@charliermarsh I would prefer a issue description and a detailed prompt.

Reusing existing knowledge for writing code is so much of an alpha

@charliermarsh This pull request should've been a fork

@zeevoexe @jarredsumner @charliermarsh :D