Replies (1)

• @dain@hachyderm.io 2025-12-14 19:50

  @simon@fedi.simonwillison.net right, so I was thinking the basic / easy option is to brute force skill creation with a skill tuned for this particular task from a given version of a repo (ones with colocated docs would work much better) and then update with the diffs as new versions come out. This could be a bit of a hit and miss though, and seeing how well Coderabbit is doing code review at the line level, I'm sure a bit of scaffolding for this could improve accuracy and decrease token usage, but this would then be a bit more effort to build, that's why I was wondering if you know of any prior art. But maybe a distributed approach like yours could be the best where library authors themselves do the work as they are the best placed doing it. But also, for libraries that already have a good, hierarchical documentation, it would probably just be a matter of transforming it into linked Markdown files and code examples so it's possible for an agent to navigate as a skill.

  Open ##2325972