Currently JACoB works best when given small, discrete, well-defined GitHub issues. However, most real-world scenarios involve multi-step code changes across a wide variety of files. One of the key ways JACoB can be the most helpful given the limitations of the current generation of LLMs is to assist the user in creating tasks that are scoped appropriately to JACoB capabilities.
[ ] Update Task Creation scenario prompt (src/app/api/chat/chat_prompts.ts) to determine if the new issue needs decomposition into todo tasks
[ ] Review potential issue and assess if it can be directly pushed to GitHub or needs to be broken down
[ ] Output "Create new Todos" button if decomposition is needed
[ ] Explicitly ask the user if they want JACoB to try to complete this task, or if they only want to create a normal GitHub Issue
[ ] Add a “Create new Todos” function that will review the recent chat messages and convert them into an array of new Todos -> save to the db (in Dashboard.tsx, similar to the handleCreateNewTask function)
[ ] Wire up the “Create new Todos” button in the Messages.tsx
[ ] Add the new todos to the front end (via a react-query refresh call)
Currently JACoB works best when given small, discrete, well-defined GitHub issues. However, most real-world scenarios involve multi-step code changes across a wide variety of files. One of the key ways JACoB can be the most helpful given the limitations of the current generation of LLMs is to assist the user in creating tasks that are scoped appropriately to JACoB capabilities.
Task Creationscenario prompt (src/app/api/chat/chat_prompts.ts) to determine if the new issue needs decomposition into todo taskshandleCreateNewTaskfunction)refreshcall)