@salesforce/afv-skills 1.29.0 → 1.30.0

package/skills/omnistudio-omniscript-generate/SKILL.md

@@ -11,7 +11,7 @@ Expert OmniStudio OmniScript builder for declarative, step-based guided digital
 
 ## Quick Reference
 
-**Scoring**: 120 points across 6 categories. **Thresholds**: ✅ 90+ (Deploy) | ⚠️ 67-89 (Review) | ❌ <67 (Block - fix required)
+**Scoring**: 120 points across 6 categories. **Thresholds**: [PASS] 90+ (Deploy) | [REVIEW] 67-89 (Review) | [BLOCK] <67 (Block - fix required)
 
 ---
 
@@ -168,7 +168,7 @@ Run `scripts/check-duplicate-omniscript.sh <Type> <SubType> <Language> <org>` to
 - **WARN**: Steps with no elements, input elements without validation, missing error handling on actions, unused data paths, deeply nested elements (>4 levels)
 
 **Validation Report Format** (6-Category Scoring 0-120):
-```
+```yaml
 Score: 102/120 ---- Very Good
 -- Design & Structure: 22/25 (88%)
 -- Data Integration: 18/20 (90%)

package/skills/omnistudio-omniscript-generate/references/best-practices.md

@@ -41,7 +41,7 @@ The default and most common pattern. Each Step represents a phase of the process
 - The final Step should be a review/confirmation screen
 
 **Example structure:**
-```
+```text
 Step 1: "Account Selection"    -> Type Ahead (account search) + DataRaptor Extract (prefill)
 Step 2: "Service Details"      -> Select, Text, Date inputs for the request
 Step 3: "Attachments"          -> File upload + Text Area for notes

package/skills/omnistudio-omniscript-generate/scripts/check-duplicate-omniscript.sh

@@ -8,6 +8,14 @@ SUBTYPE="${2:?}"
 LANGUAGE="${3:?}"
 ORG="${4:?}"
 
+# Validate inputs to prevent SOQL injection
+for var in "$TYPE" "$SUBTYPE" "$LANGUAGE"; do
+  if [[ ! "$var" =~ ^[a-zA-Z0-9_\ ]+$ ]]; then
+    echo "ERROR: Invalid input '$var'. Only alphanumeric, underscores, and spaces allowed." >&2
+    exit 1
+  fi
+done
+
 sf data query \
   -q "SELECT Id,Name,Type,SubType,Language,IsActive,VersionNumber FROM OmniProcess WHERE Type='${TYPE}' AND SubType='${SUBTYPE}' AND Language='${LANGUAGE}' AND OmniProcessType='OmniScript' LIMIT 10" \
   -o "${ORG}"

package/skills/omnistudio-omniscript-generate/scripts/deploy-omniscript.sh

@@ -9,6 +9,14 @@ TYPE="${2:?}"
 SUBTYPE="${3:?}"
 ORG="${4:?}"
 
+# Validate inputs to prevent SOQL injection
+for var in "$TYPE" "$SUBTYPE"; do
+  if [[ ! "$var" =~ ^[a-zA-Z0-9_\ ]+$ ]]; then
+    echo "ERROR: Invalid input '$var'. Only alphanumeric, underscores, and spaces allowed." >&2
+    exit 1
+  fi
+done
+
 echo "Step 1: Verify prerequisites — check org auth"
 sf org display -o "${ORG}" || { echo "ERROR: Org '${ORG}' is not authenticated. Run: sf org login web --alias ${ORG}"; exit 1; }
 

package/skills/platform-apex-logs-debug/README.md

@@ -16,7 +16,7 @@ Salesforce debugging and troubleshooting skill with log analysis, governor limit
 
 ### 1. Invoke the skill
 
-```
+```text
 Skill: platform-apex-logs-debug
 Request: "Analyze debug logs for AccountTrigger performance issues in org dev"
 ```
@@ -58,7 +58,7 @@ sf apex tail log --target-org [alias] --color
 
 | Related Skill | When to Use |
 |---------------|-------------|
-| sf-apex | Fix identified Apex issues |
+| platform-apex-generate | Fix identified Apex issues |
 | platform-soql-query | Optimize slow SOQL queries |
 | platform-apex-test-run | Re-run tests after fixes |
 

package/skills/platform-apex-logs-debug/references/cli-commands.md

@@ -297,7 +297,7 @@ echo "Deleted $COUNT logs"
 Logs over 2MB are truncated. Solutions:
 
 1. **Reduce debug level:**
-   ```
+   ```text
    ApexCode: DEBUG → INFO
    ApexProfiling: FINEST → FINE
    ```
@@ -342,7 +342,7 @@ sf apex list log --target-org my-org --json | \
 ```
 
 The hook will output analysis like:
-```
+```text
 ============================================================
 🔍 DEBUG LOG ANALYSIS
 ============================================================

package/skills/platform-apex-logs-debug/references/debug-log-reference.md

@@ -4,12 +4,12 @@
 ## Log Structure
 
 Debug logs follow a consistent format:
-```
+```text
 TIMESTAMP|EVENT_IDENTIFIER|[PARAMS]|DETAILS
 ```
 
 Example:
-```
+```text
 14:32:54.123 (123456789)|SOQL_EXECUTE_BEGIN|[45]|SELECT Id FROM Account
 ```
 
@@ -34,7 +34,7 @@ Example:
 | `SOQL_EXECUTE_END` | Query ends | Rows returned |
 
 **Analysis Pattern:**
-```
+```text
 |SOQL_EXECUTE_BEGIN|[45]|SELECT Id, Name FROM Account WHERE...
 |SOQL_EXECUTE_END|[3 rows]
 ```
@@ -54,7 +54,7 @@ Example:
 | `DML_END` | DML ends | Rows affected |
 
 **Analysis Pattern:**
-```
+```text
 |DML_BEGIN|[78]|Op:Insert|Type:Contact|
 |DML_END|[200 rows]
 ```
@@ -74,7 +74,7 @@ Example:
 | `CUMULATIVE_LIMIT_USAGE` | End of transaction | Summary of all limits |
 
 **Example:**
-```
+```text
 |LIMIT_USAGE|SOQL_QUERIES|25|100
 |LIMIT_USAGE|DML_STATEMENTS|45|150
 |LIMIT_USAGE|CPU_TIME|3500|10000
@@ -89,7 +89,7 @@ Example:
 | `FATAL_ERROR` | Unhandled exception | Full stack trace |
 
 **Analysis Pattern:**
-```
+```text
 |EXCEPTION_THROWN|[67]|System.NullPointerException|Attempt to de-reference a null object
 |FATAL_ERROR|System.NullPointerException: Attempt to de-reference a null object
   Class.ContactService.processContacts: line 67, column 1
@@ -116,7 +116,7 @@ Example:
 | `ITERATION_END` | Iteration ends | |
 
 **Detection Pattern for SOQL in Loop:**
-```
+```text
 |LOOP_BEGIN|
   |ITERATION_BEGIN|
     |SOQL_EXECUTE_BEGIN|[45]|SELECT...
@@ -137,7 +137,7 @@ Example:
 | `CALLOUT_EXTERNAL_EXIT` | HTTP callout ends | Status code, Duration |
 
 **Example:**
-```
+```text
 |CALLOUT_EXTERNAL_ENTRY|[89]|https://api.example.com/endpoint
 |CALLOUT_EXTERNAL_EXIT|[200]|[1500ms]
 ```
@@ -182,7 +182,7 @@ Example:
 ### Recommended Debug Level Settings
 
 **For Performance Issues:**
-```
+```text
 Apex Code: FINE
 Apex Profiling: FINEST
 Database: FINE
@@ -190,7 +190,7 @@ System: DEBUG
 ```
 
 **For Exception Debugging:**
-```
+```text
 Apex Code: DEBUG
 Apex Profiling: FINE
 Database: INFO
@@ -198,7 +198,7 @@ System: DEBUG
 ```
 
 **For Callout Issues:**
-```
+```text
 Apex Code: DEBUG
 Callout: FINEST
 System: DEBUG
@@ -243,7 +243,7 @@ System: DEBUG
 
 ### Pattern 1: SOQL in Loop
 
-```
+```text
 |LOOP_BEGIN|
 |ITERATION_BEGIN|
 |SOQL_EXECUTE_BEGIN|[45]|SELECT Id FROM Contact WHERE AccountId = '001xxx'
@@ -260,7 +260,7 @@ System: DEBUG
 
 ### Pattern 2: DML in Loop
 
-```
+```text
 |LOOP_BEGIN|
 |ITERATION_BEGIN|
 |DML_BEGIN|[78]|Op:Insert|Type:Contact|
@@ -273,21 +273,21 @@ System: DEBUG
 
 ### Pattern 3: Non-Selective Query
 
-```
+```text
 |SOQL_EXECUTE_BEGIN|[23]|SELECT Id FROM Lead WHERE Status = 'Open'
 |SOQL_EXECUTE_END|[250000 rows]  ← Large result set!
 ```
 
 ### Pattern 4: CPU Limit Approaching
 
-```
+```text
 |CUMULATIVE_LIMIT_USAGE|
 |CPU_TIME|9500|10000  ← 95% used!
 ```
 
 ### Pattern 5: Null Pointer Exception
 
-```
+```text
 |SOQL_EXECUTE_BEGIN|[45]|SELECT Id FROM Account WHERE Id = '001xxx'
 |SOQL_EXECUTE_END|[0 rows]  ← No results!
 |METHOD_EXIT|getAccount|

package/skills/platform-apex-logs-debug/references/log-analysis-tools.md

@@ -11,7 +11,7 @@ The **Apex Log Analyzer** is a free VS Code extension that provides visual analy
 
 ### Installation
 
-```
+```text
 1. Open VS Code
 2. Go to Extensions (Ctrl+Shift+X / Cmd+Shift+X)
 3. Search "Apex Log Analyzer"
@@ -53,7 +53,7 @@ code --install-extension FinancialForce.lana
 
 ### Reading Flame Charts
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────┐
 │ FLAME CHART INTERPRETATION                                   │
 ├─────────────────────────────────────────────────────────────┤

package/skills/platform-apex-test-run/README.md

@@ -15,7 +15,7 @@ Comprehensive Salesforce testing skill with test execution, code coverage analys
 
 ### 1. Invoke the skill
 
-```
+```yaml
 Skill: platform-apex-test-run
 Request: "Run all tests and show coverage report for org dev"
 ```

package/skills/platform-apex-test-run/references/test-fix-loop.md

@@ -16,7 +16,7 @@ When the agentic loop is enabled, platform-apex-test-run will:
 
 ## Example Agentic Flow
 
-```
+```yaml
 User: "Run tests for AccountService with auto-fix enabled"
 
 Claude:
@@ -44,6 +44,6 @@ Claude:
 
 ## Auto-Fix Command
 
-```
+```text
 Skill(skill="sf-apex", args="Fix failing test [TestClassName].[methodName] - Error: [error message]")
 ```

package/skills/platform-apex-test-run/references/testing-best-practices.md

@@ -7,7 +7,7 @@ This guide covers best practices for writing effective, maintainable Apex tests
 
 ## The Testing Pyramid
 
-```
+```text
                     ╱╲
                    ╱  ╲
                   ╱ E2E╲        Few end-to-end tests
@@ -423,7 +423,7 @@ Fast tests enable continuous integration. Slow tests become barriers to frequent
 
 ### Speed Strategy
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────┐
 │  INTEGRATION TESTS (Few)                                    │
 │  - Real DML, real triggers                                  │
@@ -499,7 +499,7 @@ sf apex get test --test-run-id [id] --code-coverage --result-format json | jq '.
 
 ### Fast Test Checklist
 
-```
+```text
 □ Is there a pure logic portion that can be unit tested?
 □ Can database operations be mocked for edge cases?
 □ Is @TestSetup reused across multiple test methods?

package/skills/platform-data-manage/README.md

@@ -18,7 +18,7 @@ Add the skill to your Cursor project by placing the `platform-data-manage` direc
 ## Usage
 
 Invoke the skill:
-```
+```text
 Skill(skill="platform-data-manage")
 Request: "Create 251 test Account records with varying Industries for trigger testing in org dev"
 ```
@@ -56,21 +56,21 @@ Request: "Create 251 test Account records with varying Industries for trigger te
 ## Cross-Skill Integration
 
 ### With platform-metadata-deploy
-```
+```text
 Skill(skill="platform-metadata-deploy")
 Request: "Describe Invoice__c in org dev - show all fields"
 ```
 Then use platform-data-manage with accurate field names and permitted values.
 
 ### From platform-apex-generate / automation-flow-generate
-```
+```text
 Skill(skill="platform-data-manage")
 Request: "Create 251 test Accounts to trigger AccountTrigger bulk testing"
 ```
 
 ## Directory Structure
 
-```
+```text
 platform-data-manage/
 ├── SKILL.md                   # Main skill prompt
 ├── assets/

package/skills/platform-data-manage/references/bulk-testing-example.md

@@ -173,7 +173,7 @@ System.debug('Heap: ' + Limits.getHeapSize() + '/' + Limits.getLimitHeapSize());
 
 ## Validation Score
 
-```
+```text
 Score: 128/130 ⭐⭐⭐⭐⭐ Excellent
 ├─ Query Efficiency: 25/25 (bulk queries)
 ├─ Bulk Safety: 25/25 (251 records, limits monitored)

package/skills/platform-data-manage/references/crud-workflow-example.md

@@ -12,7 +12,7 @@ Create a Deal Desk workflow test environment with:
 
 ## Phase 1: Discovery (sf-metadata)
 
-```
+```text
 Skill(skill="sf-metadata")
 Request: "Describe object Account in org dev - show required fields and picklist values"
 ```
@@ -171,7 +171,7 @@ sf apex run --file create-hierarchy.apex --target-org dev
 
 ## Validation Score
 
-```
+```text
 Score: 125/130 ⭐⭐⭐⭐⭐ Excellent
 ├─ Query Efficiency: 25/25 (indexed fields, no N+1)
 ├─ Bulk Safety: 23/25 (single records OK for demo)

package/skills/platform-data-manage/references/orchestration.md

@@ -7,7 +7,7 @@ This document details how platform-data-manage fits into the multi-skill workflo
 
 ## Standard Orchestration Order
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  STANDARD MULTI-SKILL ORCHESTRATION ORDER                                   │
 ├─────────────────────────────────────────────────────────────────────────────┤
@@ -35,7 +35,7 @@ This document details how platform-data-manage fits into the multi-skill workflo
 - Run test factories
 - Generate bulk test data
 
-```
+```text
 ERROR: "SObject type 'Quote__c' is not supported"
 CAUSE: Quote__c object was never deployed to the org
 FIX:   Run platform-metadata-deploy BEFORE platform-data-manage
@@ -58,7 +58,7 @@ FIX:   Run platform-metadata-deploy BEFORE platform-data-manage
 
 When testing triggers or flows, always create test data AFTER deployment:
 
-```
+```text
 1. sf-apex   → Create trigger handler class
 2. sf-flow   → Create record-triggered flow
 3. platform-metadata-deploy → Deploy trigger + flow + objects
@@ -74,7 +74,7 @@ When testing triggers or flows, always create test data AFTER deployment:
 
 Always test with **251 records** to cross the 200-record batch boundary:
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  BATCH BOUNDARY TESTING                                                     │
 ├─────────────────────────────────────────────────────────────────────────────┤
@@ -129,7 +129,7 @@ sf data query --query "SELECT Id FROM FieldPermissions WHERE SobjectType='MyObje
 
 Test Data Factory classes work with platform-data-manage:
 
-```
+```text
 sf-apex:  Creates TestDataFactory_Account.cls
           ↓
 platform-metadata-deploy: Deploys factory class
@@ -151,7 +151,7 @@ System.debug('Created ' + accounts.size() + ' accounts');
 
 After testing, clean up in reverse order:
 
-```
+```text
 1. platform-data-manage   → Delete test records
 2. platform-metadata-deploy → Deactivate flows (if needed)
 3. platform-metadata-deploy → Remove test metadata (if needed)