Editing Software Engineering (Fall 2025) (section)

==== Bot Project Task #5 ====
;Task: Identify bugs and technical debt in your assigned bot
;Due: Friday, October 31, 11:59 p.m. Pacific time
;Deliverables: You are done with Task 5 if you have conducted an analysis of limitations and weaknesses in your assigned bot by (1) publishing a report to the main repository and (2) creating user stories drawing from both the problems you've found and any new ideas for improving your bot that arise through this process.
; Turn in: No artifact turn-in required, Professor Champion will grade the state of your repository and project board.

'''Steps'''
# Divide up the different perspectives on code analysis into tasks for each group member, which might include...:
## Run XXXXXXXX on your code.
## Run XXXXXXX on your code.
## Examine your code for evidence of XXXXX from our reading XXXXX.
# Describe your findings in a shared code analysis report in your repo.
# Create user stories associated with your findings.

;Tips:
* Think about how your bot has been used so far. Did anyone try anything that didn't work or wasn't supported? Maybe that's a bug or feature request?
* Think like a bad actor: what happens if you try to break your bot?
* Feel free to use AI tools as a tutor or source for debugging any issues that come up, however you are responsible for the content you turn in.