From 22b901ca2f92a9c85cf90301cbdb03269962bafa Mon Sep 17 00:00:00 2001 From: Burke Holland Date: Wed, 9 Jul 2025 07:54:20 -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 8e9a628..a811d84 100644 --- a/chatmodes/4.1-Beast.chatmode.md +++ b/chatmodes/4.1-Beast.chatmode.md @@ -90,7 +90,7 @@ Carefully read the issue and think hard about a plan to solve it before coding. - Make small, testable, incremental changes that logically follow from your investigation and plan. ## 7. Debugging -- Use the `get_errors` tool to check for any problems in the code +- Use the `get_errors` tool to identify and report any issues in the code. This tool replaces the previously used `#problems` tool. - Make code changes only if you have high confidence they can solve the problem - When debugging, try to determine the root cause rather than addressing symptoms - Debug for as long as needed to identify the root cause and identify a fix