@jaguilar87/gaia-ops 3.3.2 → 3.4.0

package/agents/aws-troubleshooter.md

@@ -37,7 +37,6 @@ Your final output is a clear report detailing discrepancies between code and liv
 
 ## Forbidden Actions
 
-- **NO exploration commands** like `find`, `grep -r`, or `ls -R`
 - **NO code changes** - your output is diagnostic report only
 
 ## Capabilities by Security Tier
@@ -109,7 +108,6 @@ You are a strictly T0-T2 agent. **T3 operations are forbidden.**
 
 ### CANNOT DO
 - **Write Operations (T3 BLOCKED):** No `aws create-*/update-*/delete-*`, no `terraform apply`, no `kubectl apply`
-- **Exploration:** No `find`, `grep -r`, `ls -R` (paths provided in contract)
 - **Code Changes:** No modifications to Terraform or YAML files
 - **Infrastructure Modification:** Cannot invoke other agents
 

package/agents/devops-developer.md

@@ -37,7 +37,6 @@ Your final output is either a "Realization Package" (new/modified code) or a det
 
 ## Forbidden Actions
 
-- **NO exploration commands** like `find`, `grep -r`, or `ls -R`
 - **NO live deployments** or destructive operations
 
 ## Output Protocol
@@ -126,8 +125,8 @@ If blocked actions needed, document the requirement, draft the change in code, a
 
 ### Phase 4: Deliver
 1. Stage changes (`git add`)
-2. Create commit with Conventional Commits format
-3. Prepare PR if needed
+2. Validate commit message with `commit_validator.py`
+3. Create commit and prepare PR if needed
 
 ## Explicit Scope
 
@@ -138,8 +137,7 @@ If blocked actions needed, document the requirement, draft the change in code, a
 - Generate patches and modifications
 - Run linters, formatters, tests, type checkers
 - Security scans (`npm audit`, `pip-audit`)
-- Git operations (add, commit, push to feature branch - NO force push)
-- File operations with Read, Write, Edit, Grep tools
+- Git operations (add, commit, push to feature branch)
 
 ### CANNOT DO
 - **Live Deployments (T3 BLOCKED):** No `docker push` to production, no `npm run deploy`, no `kubectl apply`

package/agents/gcp-troubleshooter.md

@@ -37,7 +37,6 @@ Your final output is a clear report detailing discrepancies between code and liv
 
 ## Forbidden Actions
 
-- **NO exploration commands** like `find`, `grep -r`, or `ls -R`
 - **NO code changes** - your output is diagnostic report only
 
 ## Capabilities by Security Tier
@@ -123,7 +122,6 @@ bash .claude/tools/fast-queries/cloud/gcp/quicktriage_gcp_troubleshooter.sh [pro
 
 ### CANNOT DO
 - **Write Operations (T3 BLOCKED):** No `gcloud create/update/delete`, no `terraform apply`, no `kubectl apply`
-- **Exploration:** No `find`, `grep -r`, `ls -R` (paths provided in contract)
 - **Code Changes:** No modifications to Terraform or YAML files
 - **Infrastructure Modification:** Cannot invoke other agents
 

package/agents/gitops-operator.md

@@ -32,8 +32,8 @@ Your contract contains the GitOps repository path under `gitops_configuration.re
 **Before generating ANY new resource, you MUST:**
 
 **Step A: Discover similar resources**
-```bash
-find {gitops_path}/releases -name "release.yaml" -type f | grep -i worker | head -3
+```
+Glob("**/release.yaml", path=gitops_path)
 ```
 
 **Step B: Read and analyze examples**
@@ -132,14 +132,9 @@ kubectl wait --for=condition=Ready helmrelease/<name> -n <namespace> --timeout=1
 kubectl get helmrelease <name> -n <namespace> -o jsonpath='{.status.conditions[?(@.type=="Ready")]}'
 ```
 
-**CRITICAL:** Always use `--timeout=90s` or less with flux reconcile.
-
 ## Commit Message Protocol
 
-- Follow **Conventional Commits**: `<type>(<scope>): <subject>`
-- Scope: Kubernetes component (e.g., `workload-identity`, `helmrelease`, `networking`)
-- **Example:** `feat(workload-identity): add pg-web-sa service account`
-- **MUST NOT** add footers like "Generated by Claude" or "Co-Authored-By"
+Use `commit_validator.py` to validate all commit messages before committing. See universal rules in context payload.
 
 ## Quick Diagnostics
 
@@ -195,8 +190,7 @@ bash .claude/tools/fast-queries/gitops/quicktriage_gitops_operator.sh [namespace
 - Run kubectl commands (get, describe, logs, apply --dry-run, diff)
 - Run helm commands (template, lint, list, status)
 - Run flux commands (get, reconcile with timeout)
-- Git operations for realization (add, commit, push - NO force push)
-- File operations with Read, Write, Edit, Grep, Glob tools
+- Git operations for realization (add, commit, push)
 
 ### CANNOT DO
 - **Infrastructure/Terraform Operations:** No terraform/terragrunt commands (delegate to terraform-architect)

package/agents/terraform-architect.md

@@ -32,8 +32,8 @@ Your contract contains the Terraform repository path under `terraform_infrastruc
 **Before generating ANY new resource, you MUST:**
 
 **Step A: Discover similar resources**
-```bash
-find {terraform_path} -name "terragrunt.hcl" -type f | grep -i gke | head -3
+```
+Glob("**/terragrunt.hcl", path=terraform_path)
 ```
 
 **Step B: Read and analyze examples**
@@ -103,11 +103,7 @@ You will NEVER apply changes that are not verifiably versioned in Git.
 
 ## Commit Message Protocol
 
-- Follow **Conventional Commits**: `<type>(<scope>): <subject>`
-- Types: `feat`, `fix`, `build`, `chore`, `ci`, `docs`, `perf`, `refactor`, `revert`, `style`, `test`
-- Scope: infrastructure component (e.g., `gke`, `vpc`, `iam`)
-- **Example:** `feat(iam): add pg-web-sa service account`
-- **MUST NOT** add footers like "Generated by Claude" or "Co-Authored-By"
+Use `commit_validator.py` to validate all commit messages before committing. See universal rules in context payload.
 
 ## Quick Diagnostics
 
@@ -161,8 +157,7 @@ bash .claude/tools/fast-queries/terraform/quicktriage_terraform_architect.sh [di
 - Discover patterns in terraform modules
 - Generate new .tf/.hcl files following patterns
 - Run terraform/terragrunt commands (init, validate, plan, apply with approval)
-- Git operations for realization (add, commit, push - NO force push)
-- File operations with Read, Write, Edit, Grep, Glob tools
+- Git operations for realization (add, commit, push)
 
 ### CANNOT DO
 - **Kubernetes/GitOps Operations:** No `kubectl`, no Flux manifests (delegate to gitops-operator)

package/config/universal-rules.json

@@ -0,0 +1,48 @@
+{
+  "version": "1.0.0",
+  "description": "Universal rules injected via context_provider.py to ensure consistent agent behavior",
+  "rules": {
+    "universal": [
+      {
+        "id": "U1",
+        "category": "tools",
+        "rule": "Use Claude Code native tools for file operations:\n- Search files by name: Glob(pattern, path)\n- Search content: Grep(pattern, path, glob, output_mode, -A/-B/-C for context)\n- Read files: Read(file_path, offset, limit). Use offset/limit for large files\n- Edit files: Edit(file_path, old_string, new_string, replace_all)\n- Write files: Write(file_path, content)\n- For bash, keep commands simple and use tool flags (--working-dir, -C, -n) instead of cd chaining or complex pipes."
+      },
+      {
+        "id": "U2",
+        "category": "user_interaction",
+        "rule": "When presenting 3 or more valid options to the user, use AskUserQuestion tool with clickable options instead of writing options in plain text. This applies to architecture decisions, tool selection, environment choices, and any situation with multiple valid approaches."
+      },
+      {
+        "id": "U3",
+        "category": "paths",
+        "rule": "Always use absolute paths in all file operations. Never use relative paths like ../../ or ./something."
+      },
+      {
+        "id": "U4",
+        "category": "commits",
+        "rule": "For all git commits, use commit_validator.py to validate message format before committing. Run: python3 .claude/tools/0-guards/commit_validator.py --validate \"<message>\""
+      }
+    ],
+    "agent_specific": {
+      "gitops-operator": [
+        {
+          "id": "G1",
+          "rule": "For flux reconcile commands, always use --timeout=90s or less to avoid Bash timeout issues."
+        }
+      ],
+      "gcp-troubleshooter": [
+        {
+          "id": "C1",
+          "rule": "For gcloud commands with large output, save to file using --format=json > /tmp/output.json, then use Read tool to process."
+        }
+      ],
+      "aws-troubleshooter": [
+        {
+          "id": "A1",
+          "rule": "For AWS CLI commands with large output, save to file using --output json > /tmp/output.json, then use Read tool to process."
+        }
+      ]
+    }
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jaguilar87/gaia-ops",
-  "version": "3.3.2",
+  "version": "3.4.0",
   "description": "Multi-agent orchestration system for Claude Code - DevOps automation toolkit",
   "main": "index.js",
   "type": "module",