synapse-hub 2.2.4 → 2.4.1

package/.agents/skills/github-actions-templates/SKILL.md

@@ -1,41 +1,29 @@
 ---
 name: github-actions-templates
-description: "Create production-ready GitHub Actions workflows for automated test suites and CI/CD."
+description: "Create production-ready GitHub Actions workflows for automated test suites and CI/CD. Use when wiring test pipelines, matrix shards, or quality gates into GitHub Actions."
 ---
 
-# GitHub Actions Templates
+# GitHub Actions CI/CD Patterns for Test Automation
 
-Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications.
+> **Target:** Author secure, performant, and matrix-sharded GitHub Actions workflows for automated test execution, quality gate validation, and Allure reporting.
 
-## Do not use this skill when
-
-- The task is unrelated to github actions templates
-- You need a different domain or tool outside this scope
-
-## Instructions
-
-- Clarify goals, constraints, and required inputs.
-- Apply relevant best practices and validate outcomes.
-- Provide actionable steps and verification.
-
-## Purpose
+---
 
-Create efficient, secure GitHub Actions workflows for continuous integration and deployment across various tech stacks.
+## 1. When to Use
 
-## Use this skill when
+- Configuring continuous integration pipelines for Playwright, Katalon, Pytest, or Newman.
+- Setting up multi-OS and multi-version test execution matrices.
+- Integrating automated Quality Gate DoD (`tools/verify_all.py`).
+- Generating and publishing automated test report artifacts.
 
-- Automate testing and deployment
-- Build Docker images and push to registries
-- Deploy to Kubernetes clusters
-- Run security scans
-- Implement matrix builds for multiple environments
+---
 
-## Common Workflow Patterns
+## 2. Standard Enterprise Test Workflow Template
 
-### Pattern 1: Test Workflow
+Create in `.github/workflows/e2e_tests.yml`:
 
 ```yaml
-name: Test
+name: Enterprise Automated E2E Test Suite
 
 on:
   push:
@@ -44,291 +32,46 @@ on:
     branches: [ main ]
 
 jobs:
-  test:
-    runs-on: ubuntu-latest
-
-    strategy:
-      matrix:
-        node-version: [18.x, 20.x]
-
-    steps:
-    - uses: actions/checkout@v4
-
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v4
-      with:
-        node-version: ${{ matrix.node-version }}
-        cache: 'npm'
-
-    - name: Install dependencies
-      run: npm ci
-
-    - name: Run linter
-      run: npm run lint
-
-    - name: Run tests
-      run: npm test
-
-    - name: Upload coverage
-      uses: codecov/codecov-action@v3
-      with:
-        files: ./coverage/lcov.info
-```
-
-
-### Pattern 2: Build and Push Docker Image
-
-```yaml
-name: Build and Push
-
-on:
-  push:
-    branches: [ main ]
-    tags: [ 'v*' ]
-
-env:
-  REGISTRY: ghcr.io
-  IMAGE_NAME: ${{ github.repository }}
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
-
-    steps:
-    - uses: actions/checkout@v4
-
-    - name: Log in to Container Registry
-      uses: docker/login-action@v3
-      with:
-        registry: ${{ env.REGISTRY }}
-        username: ${{ github.actor }}
-        password: ${{ secrets.GITHUB_TOKEN }}
-
-    - name: Extract metadata
-      id: meta
-      uses: docker/metadata-action@v5
-      with:
-        images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
-        tags: |
-          type=ref,event=branch
-          type=ref,event=pr
-          type=semver,pattern={{version}}
-          type=semver,pattern={{major}}.{{minor}}
-
-    - name: Build and push
-      uses: docker/build-push-action@v5
-      with:
-        context: .
-        push: true
-        tags: ${{ steps.meta.outputs.tags }}
-        labels: ${{ steps.meta.outputs.labels }}
-        cache-from: type=gha
-        cache-to: type=gha,mode=max
-```
-
-
-### Pattern 3: Deploy to Kubernetes
-
-```yaml
-name: Deploy to Kubernetes
-
-on:
-  push:
-    branches: [ main ]
-
-jobs:
-  deploy:
+  test-matrix:
     runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v4
-
-    - name: Configure AWS credentials
-      uses: aws-actions/configure-aws-credentials@v4
-      with:
-        aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
-        aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-        aws-region: us-west-2
-
-    - name: Update kubeconfig
-      run: |
-        aws eks update-kubeconfig --name production-cluster --region us-west-2
-
-    - name: Deploy to Kubernetes
-      run: |
-        kubectl apply -f k8s/
-        kubectl rollout status deployment/my-app -n production
-        kubectl get services -n production
-
-    - name: Verify deployment
-      run: |
-        kubectl get pods -n production
-        kubectl describe deployment my-app -n production
-```
-
-### Pattern 4: Matrix Build
-
-```yaml
-name: Matrix Build
-
-on: [push, pull_request]
-
-jobs:
-  build:
-    runs-on: ${{ matrix.os }}
-
     strategy:
+      fail-fast: false
       matrix:
-        os: [ubuntu-latest, macos-latest, windows-latest]
-        python-version: ['3.9', '3.10', '3.11', '3.12']
-
-    steps:
-    - uses: actions/checkout@v4
-
-    - name: Set up Python
-      uses: actions/setup-python@v5
-      with:
-        python-version: ${{ matrix.python-version }}
-
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install -r requirements.txt
-
-    - name: Run tests
-      run: pytest
-```
-
-
-## Workflow Best Practices
-
-1. **Use specific action versions** (@v4, not @latest)
-2. **Cache dependencies** to speed up builds
-3. **Use secrets** for sensitive data
-4. **Implement status checks** on PRs
-5. **Use matrix builds** for multi-version testing
-6. **Set appropriate permissions**
-7. **Use reusable workflows** for common patterns
-8. **Implement approval gates** for production
-9. **Add notification steps** for failures
-10. **Use self-hosted runners** for sensitive workloads
-
-## Reusable Workflows
-
-```yaml
-# .github/workflows/reusable-test.yml
-name: Reusable Test Workflow
-
-on:
-  workflow_call:
-    inputs:
-      node-version:
-        required: true
-        type: string
-    secrets:
-      NPM_TOKEN:
-        required: true
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v4
-    - uses: actions/setup-node@v4
-      with:
-        node-version: ${{ inputs.node-version }}
-    - run: npm ci
-    - run: npm test
-```
-
-**Use reusable workflow:**
-```yaml
-jobs:
-  call-test:
-    uses: ./.github/workflows/reusable-test.yml
-    with:
-      node-version: '20.x'
-    secrets:
-      NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
-```
-
-## Security Scanning
-
-```yaml
-name: Security Scan
-
-on:
-  push:
-    branches: [ main ]
-  pull_request:
-    branches: [ main ]
-
-jobs:
-  security:
-    runs-on: ubuntu-latest
+        shard: [1/4, 2/4, 3/4, 4/4]
 
     steps:
-    - uses: actions/checkout@v4
-
-    - name: Run Trivy vulnerability scanner
-      uses: aquasecurity/trivy-action@master
-      with:
-        scan-type: 'fs'
-        scan-ref: '.'
-        format: 'sarif'
-        output: 'trivy-results.sarif'
-
-    - name: Upload Trivy results to GitHub Security
-      uses: github/codeql-action/upload-sarif@v2
-      with:
-        sarif_file: 'trivy-results.sarif'
-
-    - name: Run Snyk Security Scan
-      uses: snyk/actions/node@master
-      env:
-        SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}
+      - name: Checkout Code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: 'npm'
+
+      - name: Install Dependencies
+        run: npm ci
+
+      - name: Install Playwright Browsers
+        run: npx playwright install --with-deps chromium
+
+      - name: Run Sharded Playwright Tests
+        run: npx playwright test --shard=${{ matrix.shard }}
+
+      - name: Upload Test Report & Screenshots
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: playwright-report-shard-${{ strategy.job-index }}
+          path: playwright-report/
+          retention-days: 14
 ```
 
-## Deployment with Approvals
-
-```yaml
-name: Deploy to Production
-
-on:
-  push:
-    tags: [ 'v*' ]
-
-jobs:
-  deploy:
-    runs-on: ubuntu-latest
-    environment:
-      name: production
-      url: https://app.example.com
-
-    steps:
-    - uses: actions/checkout@v4
-
-    - name: Deploy application
-      run: |
-        echo "Deploying to production..."
-        # Deployment commands here
-
-    - name: Notify Slack
-      if: success()
-      uses: slackapi/slack-github-action@v1
-      with:
-        webhook-url: ${{ secrets.SLACK_WEBHOOK }}
-        payload: |
-          {
-            "text": "Deployment to production completed successfully!"
-          }
-```
+---
 
-## Related Skills
+## 3. Best Practices & Security Invariants
 
-- `gitlab-ci-patterns` - For GitLab CI workflows
-- `deployment-pipeline-design` - For pipeline architecture
-- `secrets-management` - For secrets handling
+1. **Dependency Pinning:** Always pin third-party actions to full commit SHAs or major versions (`actions/checkout@v4`).
+2. **Secret Masking:** Never hardcode credentials in workflow files; inject via `secrets.TEST_USER` and `secrets.TEST_PASS`.
+3. **Artifact Retention:** Cap test video and screenshot artifacts to 7-14 days to prevent storage bloat.
+4. **Concurrency Governance:** Cancel outdated in-flight runs on new PR commits using `concurrency: { group: ${{ github.ref }}, cancel-in-progress: true }`.

package/.agents/skills/github-actions-templates/examples/matrix_test_pipeline.yml

@@ -0,0 +1,8 @@
+name: Automated E2E Matrix
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - run: npx playwright test

package/.agents/skills/graphify-impact-analyzer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: graphify-impact-analyzer
-description: "Analyze code change blast radius and scope impacted test cases via AST."
+description: "Analyze code change blast radius and scope impacted test cases via AST. Use when analyzing the blast radius of code changes via dependency graphs."
 ---
 
 # Graphify Impact Analyzer — AST Knowledge Graph Navigation & Zero-Waste Impact Analysis
@@ -30,7 +30,7 @@ Run impact analysis before dispatching test suites:
 
 ### 2.1. Check Impact of Modified Page Class
 ```bash
-python3 tools/test_impact.py -f Keywords/pages/CategoryPage.groovy
+synapse impact -f Keywords/pages/CategoryPage.groovy
 ```
 *Output:*
 - Target File: `Keywords/pages/CategoryPage.groovy`
@@ -40,12 +40,12 @@ python3 tools/test_impact.py -f Keywords/pages/CategoryPage.groovy
 
 ### 2.2. Automatically Analyze Git Changes
 ```bash
-python3 tools/test_impact.py --git-diff
+synapse impact --git-diff
 ```
 
 ### 2.3. Output Machine-Readable JSON (For CI/CD Pipelines)
 ```bash
-python3 tools/test_impact.py --git-diff --json
+synapse impact --git-diff --json
 ```
 
 ---
@@ -71,6 +71,6 @@ python3 tools/test_impact.py --git-diff --json
 
 ## 5. Agent Operational Guardrails
 
-1. **Before modifying any Page Class:** Run `python3 tools/test_impact.py -f <path>` to identify dependent Test Cases.
+1. **Before modifying any Page Class:** Run `synapse impact -f <path>` to identify dependent Test Cases.
 2. **After modifying code:** Run `graphify update .` to keep the knowledge graph synchronized.
-3. **DoD Compliance:** Always verify that all changes pass `python3 tools/verify_all.py`.
+3. **DoD Compliance:** Always verify that all changes pass `synapse verify`.

package/.agents/skills/graphify-impact-analyzer/examples/dependency_blast_radius.json

@@ -0,0 +1,8 @@
+{
+  "modifiedFile": "src/pages/CheckoutPage.ts",
+  "impactedSuites": [
+    "tests/e2e/checkout.spec.ts",
+    "tests/e2e/payment.spec.ts"
+  ],
+  "blastRadiusScore": "LOW_ISOLATED"
+}

package/.agents/skills/katalon-cli-runner/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: katalon-cli-runner
-description: "Execute headless Katalon and Gradle test runners with automatic driver cleanup."
+description: "Execute headless Katalon and Gradle test runners with automatic driver cleanup. Use when running Katalon suites headless or integrating KRE into CI/CD."
 ---
 
 # Katalon CLI & Enterprise Runner — Dual-Mode Execution Management
@@ -72,5 +72,5 @@ katalonc -noSplash -runMode=console \
 3. **Compile Allure Report:** `allure generate ./allure-results -o ./Reports/allure-report --clean`.
 4. If failures occur, immediately dispatch failure autopsy:
    ```bash
-   python3 tools/pinpoint_failure.py
+   python3 ~/.zcode/synapse-hub/tools/pinpoint_failure.py
    ```

package/.agents/skills/katalon-cli-runner/examples/headless_kre_exec.sh

@@ -0,0 +1,3 @@
+#!/bin/sh
+# Execute headless Katalon suite with automatic process cleanup
+katalonc -noSplash -runMode=console -projectPath="$1" -testSuitePath="Test Suites/SmokeSuite" -browserType="Chrome (headless)"