improved claude commands

Author: leandroberetta

.claude/commands/debug-operator.md

@@ -8,32 +8,34 @@ This command prepares the environment for debugging the operator locally.
 
 ### 1. Scale down the in-cluster operator
 
-To debug locally, scale down the operator running in the cluster:
+Scale down the operator running in the cluster to avoid conflicts:
 
 ```bash
 kubectl scale deployment netobserv-controller-manager -n netobserv --replicas=0
 ```
 
-### 2. Remove the validating webhook for local development
+### 2. Remove the validating webhook
+
+Delete the webhook to allow free modification of the FlowCollector CR during local development:
 
 ```bash
 kubectl delete validatingwebhookconfiguration netobserv-validating-webhook-configuration
 ```
 
-This allows you to freely modify the FlowCollector CR while running the operator locally.
-
 ### 3. Run the operator locally
 
-**Now ask the user which option they prefer:**
+Use the AskUserQuestion tool to ask which debugging method to use:
 
-- **Option A: Run with go run** (simple execution without debugging)
-- **Option B: Run with delve** (interactive debugging in terminal with dlv commands)
-- **Option C: Run with delve headless + VSCode** (debugging with VSCode UI and breakpoints)
+**Question:** "How do you want to run the operator locally?"
+- **Header:** "Debug method"
+- **Options:**
+  1. "go run - Simple execution without debugging"
+  2. "delve interactive - Terminal debugging with dlv commands"
+  3. "delve headless + VSCode - UI debugging with breakpoints"
 
-**After the user responds:**
+**Based on the user's selection, execute the corresponding command:**
 
-#### If Option A (go run):
-Execute this command:
+#### Option 1: go run
 ```bash
 go run ./main.go \
   -ebpf-agent-image=quay.io/netobserv/netobserv-ebpf-agent:main \
@@ -42,8 +44,7 @@ go run ./main.go \
   -namespace=netobserv
 ```
 
-#### If Option B (delve interactive):
-Execute this command:
+#### Option 2: delve interactive
 ```bash
 dlv debug ./main.go -- \
   -ebpf-agent-image=quay.io/netobserv/netobserv-ebpf-agent:main \
@@ -52,14 +53,15 @@ dlv debug ./main.go -- \
   -namespace=netobserv
 ```
 
-This will start an interactive delve session where you can use commands like:
+After starting, inform the user they can use these delve commands:
 - `break main.main` - set breakpoint
 - `continue` - continue execution
 - `next` - step to next line
-- `print variable` - inspect variables
+- `print <variable>` - inspect variables
+
+#### Option 3: delve headless + VSCode
 
-#### If Option C (delve headless + VSCode):
-**Step 1:** Execute this command to start Delve in headless mode:
+**Step 1:** Start Delve in headless mode:
 ```bash
 dlv debug ./main.go --headless --listen=:2345 --api-version=2 --accept-multiclient -- \
   -ebpf-agent-image=quay.io/netobserv/netobserv-ebpf-agent:main \
@@ -68,42 +70,34 @@ dlv debug ./main.go --headless --listen=:2345 --api-version=2 --accept-multiclie
   -namespace=netobserv
 ```
 
-**Step 2:** Then inform the user:
+**Step 2:** Inform the user:
+
 "Delve is now running in headless mode on port 2345. To connect from VSCode:
 1. Open the Debug view (Ctrl+Shift+D / Cmd+Shift+D)
-2. Select 'Connect to Delve (Remote - Port 2345)' from the dropdown
+2. Select 'Connect to Delve (Operator Debug)' from the dropdown
 3. Press F5 or click 'Start Debugging'
 
-You can now set breakpoints in VSCode and debug the operator!"
-
-### 4. Setting your first breakpoint - FlowCollector Reconcile
+You can now set breakpoints in VSCode and debug the operator."
 
-**Example: Set a breakpoint in the FlowCollector reconciler**
+### 4. Example: Debug FlowCollector reconciliation
 
-The FlowCollector reconciliation logic is located in:
-`internal/controller/flowcollector/flowcollector_controller.go`
+**To help the user get started with debugging:**
 
-**In VSCode:**
-1. Open the file `internal/controller/flowcollector/flowcollector_controller.go`
-2. Find the `Reconcile` function (around line 100-150)
-3. Click on the left margin next to the line number where you want to pause (e.g., the first line inside the Reconcile function)
-4. A red dot will appear indicating the breakpoint is set
+The main reconciliation logic is in `internal/controller/flowcollector/flowcollector_controller.go` (look for the `Reconcile` function around line 100-150).
 
-**To trigger the reconciliation:**
-Execute this command in a terminal to modify the FlowCollector CR:
+**If using VSCode debugging:**
+1. Open `internal/controller/flowcollector/flowcollector_controller.go`
+2. Click the left margin next to the line number inside the `Reconcile` function to set a breakpoint
+3. Trigger a reconciliation by running:
 ```bash
 kubectl patch flowcollector cluster --type=merge -p '{"spec":{"processor":{"logLevel":"debug"}}}'
 ```
 
-This will trigger a reconciliation and the debugger will pause at your breakpoint, allowing you to:
-- Inspect the FlowCollector object
-- Step through the reconciliation logic
-- See how the operator processes changes
-- Debug any issues in the reconciliation loop
+The debugger will pause at your breakpoint, allowing you to inspect the FlowCollector object and step through the reconciliation logic.
 
 ## Cleanup
 
-When you're done debugging:
+When finished debugging:
 
 1. Stop the local operator (Ctrl+C in terminal, or stop debugging in VSCode)
 
@@ -112,4 +106,4 @@ When you're done debugging:
 kubectl scale deployment netobserv-controller-manager -n netobserv --replicas=1
 ```
 
-**Note:** The validating webhook will be automatically recreated by the operator when it starts back up, so you don't need to manually restore it.
+**Note:** The validating webhook will be automatically recreated by the operator.

.claude/commands/setup-dev-env.md

@@ -2,56 +2,59 @@
 
 This command sets up a complete development environment for NetObserv.
 
-**First, check if the user specified custom images:**
-- Did the user provide a **USER** (quay.io username/repo)?
-- Did the user provide a **VERSION** (image tag)?
+## Gather Configuration
 
-If the user specified custom images (e.g., "using the image from my repo, leandroberetta with tag v1.2.3"), extract those values. Otherwise, use the defaults: `USER=netobserv` and `VERSION=main`.
+First, use the AskUserQuestion tool to gather the necessary configuration:
 
-**Next, determine your platform:**
-- Are you using **OpenShift** or **vanilla Kubernetes**?
+**Question 1:** What platform are you using?
+- Options: OpenShift, Kubernetes
+- Header: "Platform"
+- Store the answer to determine if `make set-release-kind-downstream` should be run in step 2.
 
-This will determine whether to run `make set-release-kind-downstream` in step 2.
+**Question 2:** Are you using custom images?
+- Options: "Yes, custom images", "No, use defaults (netobserv/main)"
+- Header: "Images"
+
+**If the user selected custom images**, ask follow-up questions to get:
+- USER (quay.io username/repo, e.g., "leandroberetta")
+- VERSION (image tag, e.g., "v1.2.3" or "main")
+
+Set the variables:
+- If using defaults: `USER=netobserv` and `VERSION=main`
+- If using custom: `USER=<user_value>` and `VERSION=<version_value>`
 
 ## Steps
 
-### 1. Deploy the operator to the cluster
+### 1. Deploy the operator
 
-Deploy the operator with the specified or default images:
+Run the deployment command with the configured values:
 
-**If custom USER and VERSION were provided:**
+**If custom USER and VERSION:**
 ```bash
 USER=<user_value> VERSION=<version_value> make deploy
 ```
 
-**If using defaults (no custom images specified):**
+**If using defaults:**
 ```bash
 USER=netobserv make deploy
 ```
 
-**Note:**
-- Using `USER=netobserv` (default) ensures the operator uses public images from `quay.io/netobserv` without authentication.
-- Custom USER values like `USER=leandroberetta` will use images from `quay.io/leandroberetta/`.
-- The VERSION parameter controls the image tag (e.g., `VERSION=v1.2.3` or `VERSION=main`).
-
 ### 2. Configure for OpenShift (if applicable)
 
-**Only if you're using OpenShift**, run:
+**Only run this if the user selected OpenShift** in the platform question:
 
 ```bash
 make set-release-kind-downstream
 ```
 
-**If you're using vanilla Kubernetes**, skip this step entirely.
+Skip this step for Kubernetes.
 
 ### 3. Deploy Loki
 
 ```bash
 make deploy-loki
 ```
 
-This will deploy Loki and make it available at http://localhost:3100
-
 ### 4. Deploy sample FlowCollector CR
 
 ```bash
@@ -60,7 +63,7 @@ make deploy-sample-cr
 
 ### 5. Verify deployment
 
-Check that all components are running:
+Run these commands to verify all components are running:
 
 ```bash
 kubectl get pods -n netobserv
@@ -69,8 +72,8 @@ kubectl get flowcollector cluster -o yaml
 
 ## Cleanup
 
-To clean up the entire environment:
+To remove the entire environment:
 
 ```bash
 make undeploy
-```
+```