Support for sharing CHANGELOG.MD file with intent skills #216
manish-baghel
started this conversation in
Ideas
Replies: 1 comment
|
Hm, do you mean like a way to keep track of features in general when you upgrade (eg. a way to track what you have vs what has been added)? I worry that a changelog itself could bloat people's context (even if not used frequently, if it's read once and people don't have long context windows, this could eat up the entire one). I like the idea, but I wonder if there's a more efficient way to handle it. Maybe even like an "upgrade" skill that has references to what you're missing out on since the version you had been using? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Having changelog available on package update would make it significantly easy for agents to update and enrich the codebase with bug fixes and new features.
These days, libraries are changing so fast that it's hard to keep up, for eg., tanstack-ai was at 0.5.0 six months ago and now it's at 0.50.0, that's 45 minor versions in 6 months. Anyone, who wrote initial codebase 3 months ago using tanstack-ai must have written several workarounds or patches to get things to work like how they wanted and I am sure most of those are now already built in the library.
Changelogs in Intent packaged skills will make this upgrading process really easy and will also provide proper knowledge to the agents.
All reactions