@defai.digital/cli 13.4.3 → 13.4.5

package/bundled/workflows/analyst.yaml

@@ -0,0 +1,115 @@
+workflowId: analyst
+version: "1.0.0"
+name: Data Analysis Workflow
+description: Comprehensive data analysis and reporting workflow
+
+steps:
+  - stepId: define-questions
+    type: prompt
+    name: Define Analysis Questions
+    timeout: 60000
+    config:
+      agentId: data-scientist
+      prompt: |
+        Define the analysis scope:
+        1. What questions are we answering?
+        2. What metrics are relevant?
+        3. What data sources are needed?
+        4. What time period to analyze?
+
+  - stepId: gather-data
+    type: tool
+    name: Gather Data
+    timeout: 120000
+    config:
+      tool: memory_search
+      args:
+        namespace: analytics
+        includeMetadata: true
+
+  - stepId: clean-data
+    type: prompt
+    name: Data Cleaning
+    timeout: 60000
+    config:
+      agentId: data-scientist
+      prompt: |
+        Clean and prepare data:
+        1. Handle missing values
+        2. Remove outliers
+        3. Normalize formats
+        4. Validate data quality
+
+  - stepId: exploratory-analysis
+    type: prompt
+    name: Exploratory Analysis
+    timeout: 180000
+    config:
+      agentId: data-scientist
+      prompt: |
+        Perform exploratory analysis:
+        1. Calculate summary statistics
+        2. Identify trends and patterns
+        3. Find correlations
+        4. Detect anomalies
+
+  - stepId: statistical-tests
+    type: prompt
+    name: Statistical Testing
+    timeout: 120000
+    config:
+      agentId: data-scientist
+      prompt: |
+        Run statistical tests:
+        1. Choose appropriate tests
+        2. Check assumptions
+        3. Calculate significance
+        4. Interpret results
+
+  - stepId: generate-visualizations
+    type: prompt
+    name: Generate Visualizations
+    timeout: 60000
+    config:
+      agentId: data-scientist
+      prompt: |
+        Create visualizations:
+        1. Charts for key metrics
+        2. Trend visualizations
+        3. Comparison charts
+        4. Distribution plots
+
+  - stepId: write-report
+    type: prompt
+    name: Write Analysis Report
+    timeout: 120000
+    config:
+      agentId: writer
+      prompt: |
+        Write the analysis report:
+        1. Executive summary
+        2. Methodology
+        3. Key findings
+        4. Recommendations
+        5. Appendix with details
+
+  - stepId: store-results
+    type: tool
+    name: Store Results
+    timeout: 30000
+    config:
+      tool: memory_store
+      args:
+        namespace: analysis-reports
+        ttl: 2592000
+
+metadata:
+  category: analytics
+  tags:
+    - data-analysis
+    - reporting
+    - insights
+  requiredAbilities:
+    - data-analysis
+    - statistical-analysis
+    - documentation

package/bundled/workflows/assistant.yaml

@@ -0,0 +1,74 @@
+workflowId: assistant
+version: "1.0.0"
+name: General Assistant Workflow
+description: General-purpose assistance for various tasks
+
+steps:
+  - stepId: understand-request
+    type: prompt
+    name: Understand Request
+    timeout: 30000
+    config:
+      agentId: standard
+      prompt: |
+        Understand the user request:
+        1. Identify the type of task
+        2. Determine required expertise
+        3. Check for ambiguities
+        4. Plan the approach
+
+  - stepId: gather-context
+    type: tool
+    name: Gather Context
+    timeout: 30000
+    config:
+      tool: memory_search
+      args:
+        namespace: conversation
+        limit: 10
+
+  - stepId: execute-task
+    type: prompt
+    name: Execute Task
+    timeout: 300000
+    config:
+      agentId: standard
+      prompt: |
+        Execute the requested task:
+        1. Follow best practices
+        2. Provide clear explanations
+        3. Include examples where helpful
+        4. Anticipate follow-up questions
+
+  - stepId: verify-completeness
+    type: prompt
+    name: Verify Completeness
+    timeout: 30000
+    config:
+      agentId: standard
+      prompt: |
+        Verify the response:
+        1. Does it fully answer the question?
+        2. Is it accurate and up-to-date?
+        3. Is it clear and well-structured?
+        4. Are there any caveats to mention?
+
+  - stepId: store-interaction
+    type: tool
+    name: Store Interaction
+    timeout: 10000
+    config:
+      tool: memory_store
+      args:
+        namespace: conversation
+        ttl: 86400
+
+metadata:
+  category: general
+  tags:
+    - assistant
+    - general-purpose
+    - help
+  requiredAbilities:
+    - communication
+    - problem-solving

package/bundled/workflows/code-review-discussion.yaml

@@ -0,0 +1,166 @@
+# Code Review Discussion Workflow
+#
+# Multiple AI models collaboratively review code using the discuss step.
+# Leverages different model strengths for comprehensive review.
+#
+# Usage:
+#   ax run code-review-discussion --input '{"code": "...", "focus": "security"}'
+#
+# Model Roles:
+#   - Claude: Security and correctness analysis
+#   - Grok: Edge cases and real-time analysis
+#
+# Focus Options: security, performance, maintainability, all
+
+workflowId: code-review-discussion
+version: "1.0.0"
+name: Multi-Model Code Review
+description: >
+  Multiple AI models discuss and critique code, reaching consensus on
+  improvements through structured rounds of review and synthesis.
+
+steps:
+  # Step 1: Initial critique from multiple perspectives
+  - stepId: multi-perspective-review
+    type: discuss
+    name: Multi-Perspective Code Review
+    timeout: 180000
+    config:
+      pattern: critique
+      providers:
+        - claude
+        - grok
+      prompt: |
+        Review this code for {{input.focus | default: "all"}} concerns:
+
+        ```
+        {{input.code}}
+        ```
+
+        Each reviewer should:
+        1. Identify issues from your expertise area
+        2. Rate severity (critical/major/minor)
+        3. Suggest specific fixes with code examples
+        4. Consider edge cases and failure modes
+
+        Expertise areas:
+        - Security vulnerabilities (OWASP top 10, injection, auth)
+        - Performance bottlenecks (O(n), memory, I/O)
+        - Maintainability issues (code smells, complexity)
+        - Type safety and correctness
+      rounds: 3
+      consensus:
+        method: synthesis
+        synthesizer: claude
+        includeDissent: true
+      providerTimeout: 60000
+      continueOnProviderFailure: true
+      minProviders: 2
+
+  # Step 2: Vote on priority of fixes
+  - stepId: prioritize-fixes
+    type: discuss
+    name: Prioritize Fixes
+    timeout: 120000
+    dependencies:
+      - multi-perspective-review
+    config:
+      pattern: voting
+      providers:
+        - claude
+        - grok
+      prompt: |
+        Based on the review synthesis:
+
+        {{steps.multi-perspective-review.output.synthesis}}
+
+        Vote on which category of issues to address FIRST:
+        1. Security vulnerabilities
+        2. Performance issues
+        3. Maintainability improvements
+        4. Type safety fixes
+
+        Consider:
+        - Production impact
+        - Fix complexity
+        - Technical debt
+      rounds: 1
+      consensus:
+        method: voting
+        threshold: 0.5
+        includeDissent: true
+      minProviders: 2
+
+  # Step 3: Generate refactored code
+  - stepId: generate-fix
+    type: discuss
+    name: Generate Fixed Code
+    timeout: 180000
+    dependencies:
+      - prioritize-fixes
+    config:
+      pattern: synthesis
+      providers:
+        - claude
+        - grok
+      prompt: |
+        Generate the improved code based on:
+
+        Priority: {{steps.prioritize-fixes.output.consensus.winner}}
+
+        Review findings:
+        {{steps.multi-perspective-review.output.synthesis}}
+
+        Original code:
+        ```
+        {{input.code}}
+        ```
+
+        Requirements:
+        1. Fix the highest priority issues identified
+        2. Preserve existing functionality
+        3. Add inline comments explaining changes
+        4. Include any necessary type annotations
+        5. Follow existing code style
+      rounds: 2
+      consensus:
+        method: synthesis
+        synthesizer: claude
+        includeDissent: true
+      minProviders: 2
+
+  # Store results
+  - stepId: store-review
+    type: tool
+    name: Store Review Results
+    timeout: 10000
+    dependencies:
+      - generate-fix
+    config:
+      tool: memory_store
+      args:
+        namespace: code-reviews
+        key: "review-{{now | timestamp}}"
+        value:
+          originalCode: "{{input.code}}"
+          focus: "{{input.focus | default: 'all'}}"
+          reviewFindings: "{{steps.multi-perspective-review.output.synthesis}}"
+          prioritizedFocus: "{{steps.prioritize-fixes.output.consensus.winner}}"
+          improvedCode: "{{steps.generate-fix.output.synthesis}}"
+          timestamp: "{{now}}"
+
+metadata:
+  category: code-review
+  tags:
+    - discuss-step
+    - code-review
+    - multi-model
+    - security
+    - quality
+  requiredAbilities:
+    - code-review
+    - security-practices
+  estimatedDuration: 300000
+  providers:
+    - claude
+    - grok

package/bundled/workflows/code-reviewer.yaml

@@ -0,0 +1,94 @@
+workflowId: code-reviewer
+version: "1.0.0"
+name: Code Review Workflow
+description: Automated code review with best practices checks, security analysis, and suggestions
+
+steps:
+  - stepId: analyze-changes
+    type: prompt
+    name: Analyze Code Changes
+    timeout: 60000
+    config:
+      agentId: quality
+      prompt: |
+        Analyze the provided code changes:
+        1. Identify files changed and their types
+        2. Summarize the nature of changes
+        3. List affected components/modules
+
+  - stepId: check-style
+    type: tool
+    name: Style and Lint Check
+    timeout: 30000
+    retryPolicy:
+      maxAttempts: 2
+      backoffMs: 1000
+    config:
+      tool: guard_check
+      args:
+        policyId: code-style
+        categories:
+          - formatting
+          - naming
+          - imports
+
+  - stepId: security-scan
+    type: tool
+    name: Security Analysis
+    timeout: 60000
+    config:
+      tool: bugfix_scan
+      args:
+        categories:
+          - security
+          - injection
+          - authentication
+        minSeverity: medium
+
+  - stepId: review-logic
+    type: prompt
+    name: Logic Review
+    timeout: 120000
+    config:
+      agentId: backend
+      prompt: |
+        Review the code for:
+        1. Logic errors and edge cases
+        2. Error handling completeness
+        3. Performance implications
+        4. Code duplication
+        Provide specific line references for issues.
+
+  - stepId: suggest-improvements
+    type: prompt
+    name: Improvement Suggestions
+    timeout: 60000
+    config:
+      agentId: architecture
+      prompt: |
+        Based on the analysis, suggest:
+        1. Refactoring opportunities
+        2. Design pattern applications
+        3. Test coverage improvements
+        4. Documentation needs
+
+  - stepId: generate-report
+    type: tool
+    name: Generate Review Report
+    timeout: 30000
+    config:
+      tool: memory_store
+      args:
+        namespace: code-reviews
+        format: markdown
+
+metadata:
+  category: quality
+  tags:
+    - code-review
+    - quality
+    - automated
+  requiredAbilities:
+    - code-review
+    - security
+    - clean-code