foundation of the '/break' command

[jaynopponep]

Please make a new branch for this.

We can break this process down into deliverables:

• [ ] Start writing /break command.
  • Specification:
  • [ ] Takes user prompt/query (e.g. "When is the next break?", "Next Holiday?", "Next College Closing Days", etc.)
  • Parameter wise, it should be something like: "/break [query_message]"
  • [ ] You'll see in the '/class' function in src/index.js that it interacts with our LLM. Your /break command should pass along the query message directly to llm.py, I will assist you with this! Use the child_process tool that's built-in to JS.
  • [ ] This function will ALSO pass along another parameter to assign a context for the LLM. Ask me for a full explanation on this.
  • [ ] Wanted to make unit testing a habit, and I think this would be good here to ensure we catch bugs before they appear on Discord. So write unit tests for the command (although it's not a function, should still be able to do this somehow). We can discuss this more once we're closer to this step.

[jaynopponep]

To keep record, I deleted these tasks: - [ ] Scrape from the CCNY calendar. I recommend BeautifulSoup4. .- [ ] Turn the 's that you scraped, and process them into a DataFrame, then save into CSV. Consider Python datetime format for each date. .- [ ] Make sure the column values are all consistent!!!!! .- Build context based around the CSV built (I will help you with this since I am on the LLM aspect). .- Context should now do something like "Here is the CSV. [User_prompt_here]", and LLM will respond properly based on this context. - [ ] Consider a plan for periodically updating CSV for new updates on the CCNY calendar.<- No Longer Needed!