Earlier quoted context omitted.
> I am unable to get these things to do anything useful. My experience is widely different than yours. I use Copilot extensively to explain aspects of codebases, generate documentation, and even fill in boilerplate code for automated tests. You need to provide the right context with the right system prompts, which needs some effort from your end, and you cannot expect perfect outputs. In the end it's like any softwar…
These services retain historical records of interactions. Can you show me an example of successfully doing what you claim you do?
https://github.com/williamcotton/search-query-parser-scratch...
Claude, using Projects, wrote perhaps 90% of this project with my detailed guidance.
It does a double pass, the first pass recursive descent to get strings as leaf nodes and then another pass to get multiple errors reported at once.
There's also a React component for a search input box powered by Monaco and complete with completions, error underlines and messaging, and syntax highlighting:
https://github.com/williamcotton/search-query-parser-scratch...
Feel free to browse the commit history to get an idea of how much time this saved me. Spoiler alert: it saved a lot of time. Frankly, I wouldn't have bothered with this project without offloading most of the work to an LLM.
There's a lot more than this and if you want a demo you can:
git clone git@github.com:williamcotton/search-query-parser-scratchpad.git
cd search-input-query-react
npm install
npm run dev
Put something like this into the input: -status:out price:
And then play around with valid and invalid syntax.It has Sqlite WASM running in the browser with demo data so you'll get some actual results.
If you want a guided video chat tour of how I used the tool I'd be happy to arrange that. It takes too much work to get things out of Claude.