From 4837b26e5895c8568e0350d6a08df58a5f349857 Mon Sep 17 00:00:00 2001
From: Nicola Zangrandi <wasp@wasp.ovh>
Date: Fri, 21 Feb 2025 08:50:22 +0100
Subject: [PATCH] feat(rules): add error handling standards to command paths

---
 .cursor/rules/command-paths.mdc | 23 +++++++++++++++++++++--
 1 file changed, 21 insertions(+), 2 deletions(-)

diff --git a/.cursor/rules/command-paths.mdc b/.cursor/rules/command-paths.mdc
index 078c935..53e36ac 100644
--- a/.cursor/rules/command-paths.mdc
+++ b/.cursor/rules/command-paths.mdc
@@ -26,6 +26,19 @@ When writing scripts that use external commands:
    - Consider environment-specific paths
    - Use $HOME instead of ~ for home directory paths
 
+4. Error Handling:
+   - Always use `set -euo pipefail`
+   - Wrap critical commands in error handlers:
+     ```bash
+     COMMAND || {
+         echo "Command failed!"
+         exit 1
+     }
+     ```
+   - Add descriptive echo statements before and after important commands
+   - Use meaningful exit codes
+   - Ensure proper cleanup on error
+
 4. Example pattern:
    ```bash
    # Find executable
@@ -58,9 +71,15 @@ examples:
       $GO_CMD build
 
   - input: |
-      # Bad: Using tilde expansion
-      ~/.bun/bin/bun install
+      # Bad: No error handling
+      go build -o app
     output: |
+      # Good: With error handling
+      echo "Building application..."
+      go build -o app || {
+          echo "Build failed!"
+          exit 1
+      }
       # Good: Use $HOME
       if command -v bun >/dev/null 2>&1; then
           BUN_CMD="bun"