From e6cf24403dc78d27d32ece0aea0c6f07cd5cfa66 Mon Sep 17 00:00:00 2001 From: Burke Holland Date: Wed, 9 Jul 2025 07:54:50 -0500 Subject: [PATCH] Update chatmodes/4.1-Beast.chatmode.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- chatmodes/4.1-Beast.chatmode.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chatmodes/4.1-Beast.chatmode.md b/chatmodes/4.1-Beast.chatmode.md index 7b0cd0a..a005665 100644 --- a/chatmodes/4.1-Beast.chatmode.md +++ b/chatmodes/4.1-Beast.chatmode.md @@ -81,7 +81,7 @@ Carefully read the issue and think hard about a plan to solve it before coding. - Create a todo list in markdown format to track your progress. - Each time you complete a step, check it off using `[x]` syntax. - Each time you check off a step, display the updated todo list to the user. -- Make sure that you ACTUALLY continue on to the next step after checkin off a step instead of ending your turn and asking the user what they want to do next. +- Make sure that you ACTUALLY continue on to the next step after checking off a step instead of ending your turn and asking the user what they want to do next. ## 6. Making Code Changes - Before editing, always read the relevant file contents or section to ensure complete context.