Fix debug-app command and other comments. (#72)

Author: gspencergoog

commands/commit.toml

@@ -2,7 +2,7 @@
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
-# This command will be invoked via: /flutter:commit
+# This command will be invoked via: /commit (or /flutter:commit in the case of collisions)
 
 description = "Ensure your Dart or Flutter project is in a healthy place (analysis warnings and errors are addressed, for example) and prep a descriptive git commit."
 

commands/create-app.toml

@@ -2,7 +2,7 @@
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
-# This command will be invoked via: /flutter:create_app
+# This command will be invoked via: /create-app (or /flutter:create-app in the case of collisions)
 
 description = "Create a new Flutter app, with an opinionated structure."
 

commands/create-package.toml

@@ -2,7 +2,7 @@
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
-# This command will be invoked via: /flutter:create_package
+# This command will be invoked via: /create-package (or /flutter:create-package in the case of collisions)
 
 description = "Create a new Dart or Flutter package, with an opinionated structure."
 

commands/debug_app.toml commands/debug-app.tomlcommands/debug_app.toml renamed to commands/debug-app.toml

@@ -1,4 +1,13 @@
-Your goal is to help a user debug an issue in their Dart or Flutter application. Follow these steps methodically.
+# Copyright 2025 The Flutter Authors.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+# This command will be invoked via: /debug-app (or /flutter:debug-app in the case of collisions)
+
+description = "Do a deep dive to debug a complex issue in a Dart or Flutter app or package."
+
+prompt = """
+We're going to debug a Dart or Flutter application. Your goal is to help the user debug an issue in their Dart or Flutter application. Follow these steps methodically.
 
 ## Problem Specification
 
@@ -97,4 +106,5 @@ Once the bug is confirmed to be fixed and the application is stable:
 - [ ] Remove any temporary debugging code (e.g., logging statements that aren't generally useful).
 - [ ] Run `dart_fix`, `dart_format`, `analyze_files`, and `run_tests` to ensure the codebase is clean and healthy.
 - [ ] Prepare a descriptive commit message for the fix, following the "Conventional Commits" specification. The message should include a subject, an optional body explaining the "why" behind the change, and a footer (e.g., `Fixes: #123`) if the user provides an issue number or link. Present the message to the user for approval before committing the changes.
-  - Do not include the DEBUGGING_PLAN.md file in the commit. When done, ask the user if they would like to remove it.
+  - Do not include the DEBUGGING_PLAN.md file in the commit. When done, ask the user if they would like to remove it.
+"""

commands/modify.toml

@@ -2,12 +2,12 @@
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
-# This command will be invoked via: /flutter:modify
+# This command will be invoked via: /modify (or /flutter:modify in the case of collisions)
 
 description = "Perform a modification of your Flutter or Dart project."
 
 prompt = """
-We're going to modify some code.
+We're going to modify some Dart or Flutter project code.
 
 ## Problem specification