@housecor the process shouldn't be any different than it used to be if you're serious about maintaining quality software and products. If you don't review the code, any future work (agents or otherwise) will assume the standard that's been set. Absolutely review code, always.
Spent a week optimizing a RAG pipeline for a support chat agent after reading @jxnlco's RAG series.
recall@1 went from 23% to 50%.
This is just 1 of 6 RAG evals (only retrieval quality C|Q). Faithfulness and answer relevance are still untested.
Plenty of room left to improve.
@mattpocockuk How would you approach an "analyze" type skill that is inherently multi-step? Like, fetch data, check for patterns based on some rules, give conclusion