roast-ai 0.3.1 → 0.4.1

data/examples/mcp/README.md

@@ -44,7 +44,7 @@ tools:
         - --rm
         - ghcr.io/example/mcp-server
       env:
-        API_KEY: "{{env.API_KEY}}"
+        API_KEY: "{{ENV['API_KEY']}}"
       except:
         - dangerous_function
 ```
@@ -116,7 +116,7 @@ tools:
       command: npx
       args: ["-y", "@modelcontextprotocol/server-github"]
       env:
-        GITHUB_PERSONAL_ACCESS_TOKEN: "{{env.GITHUB_TOKEN}}"
+        GITHUB_PERSONAL_ACCESS_TOKEN: "{{ENV['GITHUB_TOKEN']}}"
       only:
         - search_repositories
         - get_issue
@@ -131,7 +131,7 @@ tools:
       command: npx
       args: ["-y", "@modelcontextprotocol/server-postgres"]
       env:
-        DATABASE_URL: "{{env.DATABASE_URL}}"
+        DATABASE_URL: "{{ENV['DATABASE_URL']}}"
       only:
         - query
         - list_tables

data/examples/mcp/analyze_changes/prompt.md

@@ -1,4 +1,4 @@
-For the file {{resource.target}}:
+For the file <%= resource.target %>:
 1. Read the file contents using read_file
 2. Use the Linter tool to analyze code quality
 3. Check for common issues:

data/examples/mcp/database_workflow.yml

@@ -12,7 +12,7 @@ tools:
         - "-y"
         - "@modelcontextprotocol/server-postgres"
       env:
-        DATABASE_URL: "{{env.DATABASE_URL}}"
+        DATABASE_URL: "{{ENV['DATABASE_URL']}}"
       only:
         - query
         - list_tables

data/examples/mcp/fetch_pr_context/prompt.md

@@ -1,4 +1,4 @@
-Using the GitHub tool, fetch details about PR #{{env.PR_NUMBER}}:
+Using the GitHub tool, fetch details about PR #<%= ENV['PR_NUMBER'] %>:
 1. Get the PR description and title
 2. List all changed files
 3. Identify the type of changes (feature, bugfix, refactor)

data/examples/mcp/github_workflow.yml

@@ -15,7 +15,7 @@ tools:
         - "-y"
         - "@modelcontextprotocol/server-github"
       env:
-        GITHUB_PERSONAL_ACCESS_TOKEN: "{{env.GITHUB_TOKEN}}"
+        GITHUB_PERSONAL_ACCESS_TOKEN: "{{ENV['GITHUB_TOKEN']}}"
       only:
         - search_repositories
         - get_repository

data/examples/mcp/post_review/prompt.md

@@ -1,3 +1,3 @@
-Using the GitHub tool, post the code review as a comment on PR #{{env.PR_NUMBER}}.
+Using the GitHub tool, post the code review as a comment on PR #<%= ENV['PR_NUMBER'] %>.
 Format the review in a friendly, constructive manner.
 Include specific line-by-line suggestions where appropriate.

data/examples/no_model_fallback/README.md

@@ -0,0 +1,17 @@
+# No Model Fallback Example
+
+This example demonstrates the issue where workflows without explicit model specification do not properly fall back to a default model.
+
+## Purpose
+
+This workflow is based on the interpolation example but intentionally omits the `model` field to test the fallback behavior.
+
+## Expected Behavior
+
+The workflow should fall back to a default model when no model is specified at the workflow level.
+
+## Usage
+
+```bash
+bin/roast examples/no_model_fallback/workflow.yml --file examples/no_model_fallback/sample.rb
+```

data/examples/no_model_fallback/analyze_file/prompt.md

@@ -0,0 +1 @@
+Analyze the file at: <%= workflow.file %>

data/examples/no_model_fallback/analyze_patterns/prompt.md

@@ -0,0 +1,27 @@
+Extract some patterns about this file and return in json format like this:
+
+<json>
+{
+  "code_patterns": {
+    "class_structure": {
+      "name": "Calculator",
+      "instance_variables": ["@memory"],
+      "method_count": 7,
+      "method_types": {
+        "constructor": ["initialize"],
+        "operations": ["add", "subtract", "multiply", "divide"],
+        "accessors": ["memory"],
+        "utility": ["clear"]
+      }
+    },
+    "error_handling": {
+      "techniques": ["conditional raise", "zero check"],
+      "examples": ["raise \"Division by zero!\" if number.zero?"]
+    },
+    "design_patterns": {
+      "state": "Uses instance variable to maintain calculator state",
+      "command": "Each operation method modifies the internal state"
+    }
+  }
+}
+</json>

data/examples/no_model_fallback/generate_report_for_md/prompt.md

@@ -0,0 +1,10 @@
+Generate a comprehensive report for the markdown file.
+
+File content: {{steps.analyze_file}}
+
+Patterns found: {{steps.analyze_patterns}}
+
+Please create a detailed report that includes:
+1. Summary of the file content
+2. Key patterns identified
+3. Any recommendations or observations

data/examples/no_model_fallback/generate_report_for_rb/prompt.md

@@ -0,0 +1,3 @@
+Generate a nicely formatted report based on the following metadata:
+
+<%= workflow.output[:analyze_patterns] %>

data/examples/no_model_fallback/sample.rb

@@ -0,0 +1,42 @@
+# frozen_string_literal: true
+
+# Sample Ruby file for testing interpolation in workflows
+
+class Calculator
+  def initialize
+    @memory = 0
+  end
+
+  def add(number)
+    @memory += number
+  end
+
+  def subtract(number)
+    @memory -= number
+  end
+
+  def multiply(number)
+    @memory *= number
+  end
+
+  def divide(number)
+    raise "Division by zero!" if number.zero?
+
+    @memory /= number
+  end
+
+  attr_reader :memory
+
+  def clear
+    @memory = 0
+  end
+end
+
+# Example usage
+if __FILE__ == $PROGRAM_NAME
+  calc = Calculator.new
+  calc.add(10)
+  calc.multiply(2)
+  calc.subtract(5)
+  puts "Result: #{calc.memory}"
+end

data/examples/no_model_fallback/workflow.yml

@@ -0,0 +1,19 @@
+name: no_model_fallback_example
+
+tools:
+  - Roast::Tools::ReadFile
+
+steps:
+  - analyze_file
+  - analyze_patterns
+  - generate_report_for_{{File.extname(workflow.file).sub('.', '')}}
+  - '$(echo "Processing completed for file: {{File.basename(workflow.file)}}")'
+
+analyze_patterns:
+  json: true
+
+generate_report_for_rb:
+  print_response: true
+
+generate_report_for_md:
+  print_response: true

data/examples/pre_post_processing/analyze_test_file/prompt.md

@@ -1,6 +1,6 @@
 # Analyze Test File
 
-Current test file: {{file}}
+Current test file: <%= file %>
 
 Please analyze this test file and identify:
 

data/examples/pre_post_processing/improve_test_coverage/prompt.md

@@ -1,6 +1,6 @@
 # Improve Test Coverage
 
-Based on the analysis of {{file}}, implement the following improvements:
+Based on the analysis of <%= file %>, implement the following improvements:
 
 1. **Add Missing Test Cases**: Write tests for uncovered code paths, edge cases, and error conditions
 2. **Improve Test Descriptions**: Make test names more descriptive and follow consistent naming conventions

data/examples/pre_post_processing/optimize_test_performance/prompt.md

@@ -1,6 +1,6 @@
 # Optimize Test Performance
 
-Optimize the performance of {{file}} by:
+Optimize the performance of <%= file %> by:
 
 1. **Reduce Setup Overhead**:
    - Move expensive operations out of individual test setup

data/examples/pre_post_processing/post_processing/aggregate_metrics/prompt.md

@@ -3,8 +3,8 @@
 Aggregate all the metrics collected during the workflow execution:
 
 Available data:
-- Pre-processing baseline metrics: {{pre_processing.gather_baseline_metrics}}
-- Results from all processed test files: {{output.targets}}
+- Pre-processing baseline metrics: <%= pre_processing.gather_baseline_metrics %>
+- Results from all processed test files: <%= output.targets %>
 
 Please calculate and provide:
 

data/examples/pre_post_processing/post_processing/generate_summary_report/prompt.md

@@ -9,7 +9,7 @@ Provide a high-level overview of the optimization results, key achievements, and
 
 ### Metrics Summary
 Include the aggregated metrics from the previous step:
-{{aggregate_metrics}}
+<%= aggregate_metrics %>
 
 ### Detailed Results by File
 For each processed test file, include:

data/examples/pre_post_processing/pre_processing/setup_test_environment/prompt.md

@@ -3,7 +3,7 @@
 Prepare the test environment for optimization. Please:
 
 1. Ensure all test dependencies are installed
-2. Create a backup branch for safety: `test-optimization-backup-{{timestamp}}`
+2. Create a backup branch for safety: `test-optimization-backup-<%= timestamp %>`
 3. Set up any necessary test databases or fixtures
 4. Configure test parallelization settings if available
 5. Clear any test caches that might affect benchmarking

data/examples/pre_post_processing/validate_changes/prompt.md

@@ -1,6 +1,6 @@
 # Validate Changes
 
-Validate the changes made to {{file}}:
+Validate the changes made to <%= file %>:
 
 1. **Run the updated tests** and ensure they all pass
 2. **Check coverage metrics** to verify improvements
@@ -11,7 +11,7 @@ Validate the changes made to {{file}}:
 Store the validation results in the workflow state:
 ```json
 {
-  "file": "{{file}}",
+  "file": "<%= file %>",
   "tests_passed": true,
   "coverage_before": 0.0,
   "coverage_after": 0.0,

data/examples/swarm_example.yml

@@ -0,0 +1,25 @@
+name: Swarm Example Workflow
+
+# Example workflow demonstrating Roast's integration with Claude Swarm
+# The Swarm tool is available to the LLM, which can choose to use it when appropriate
+
+tools:
+  - Roast::Tools::Swarm:
+      path: ".swarm.yml"  # Optional - will use default locations if not specified
+
+steps:
+  - orchestrate_refactoring: |
+      Help me refactor this codebase for better performance. Coordinate multiple 
+      Claude agents using the swarm configuration to:
+      1. Analyze the current code structure
+      2. Identify performance bottlenecks
+      3. Implement optimizations
+      4. Ensure backward compatibility
+      
+  - specialized_analysis: |
+      Now use the specialized swarm configuration at ./specialized-swarm.yml to run 
+      a comprehensive code analysis that includes:
+      - Architecture review
+      - Security audit  
+      - Documentation generation
+      - Test coverage analysis

data/examples/user_input/README.md

@@ -0,0 +1,90 @@
+# User Input Example
+
+This example demonstrates how to use the `input` step type in Roast workflows to collect information from users during workflow execution.
+
+## Overview
+
+The `input` step type allows workflows to:
+- Collect text input from users
+- Ask yes/no questions (boolean)
+- Present multiple choice options
+- Securely collect passwords (hidden input)
+- Store collected values in workflow state for later use
+
+## Running the Example
+
+```bash
+# Run the interactive deployment workflow
+roast execute examples/user_input/workflow.yml
+
+# Run a simple survey workflow
+roast execute examples/user_input/survey_workflow.yml
+```
+
+## Input Step Configuration
+
+### Basic Text Input
+```yaml
+- input:
+    prompt: "Enter your name:"
+    name: user_name
+```
+
+### Boolean (Yes/No) Input
+```yaml
+- input:
+    prompt: "Do you want to continue?"
+    type: boolean
+    default: true
+    name: should_continue
+```
+
+### Choice Selection
+```yaml
+- input:
+    prompt: "Select environment:"
+    type: choice
+    options:
+      - development
+      - staging
+      - production
+    name: environment
+```
+
+### Password Input
+```yaml
+- input:
+    prompt: "Enter password:"
+    type: password
+    required: true
+    name: user_password
+```
+
+## Configuration Options
+
+- `prompt` (required): The question or message to display to the user
+- `name` (optional): Variable name to store the input value in workflow state
+- `type` (optional): Type of input - `text` (default), `boolean`, `choice`, or `password`
+- `required` (optional): Whether the input is required (default: false)
+- `default` (optional): Default value if user presses enter without input
+- `timeout` (optional): Timeout in seconds for user input
+- `options` (required for choice type): Array of options for choice selection
+
+## Accessing Input Values
+
+Input values stored with a `name` can be accessed in subsequent steps using interpolation:
+
+```yaml
+- input:
+    prompt: "Enter project name:"
+    name: project_name
+
+- prompt: "Creating project: #{state.project_name}"
+```
+
+## Non-TTY Environments
+
+When running in non-TTY environments (e.g., CI/CD pipelines), input steps will:
+- Use default values if provided
+- Fail if required inputs have no default
+- Skip optional inputs without defaults

data/examples/user_input/funny_name/create_backstory/prompt.md

@@ -0,0 +1,10 @@
+Create a hilarious and absurd backstory for someone named <%= workflow.output.user_name %> as a <%= workflow.output.genre %>.
+
+Make it funny, creative, and include:
+- A ridiculous origin story
+- An absurd special ability or talent related to their name
+- A nemesis with an equally silly name
+- Their greatest achievement (make it hilariously mundane yet epic)
+- A catchphrase that makes no sense
+
+Keep it fun and family-friendly! Format it as an entertaining narrative.

data/examples/user_input/funny_name/workflow.yml

@@ -0,0 +1,26 @@
+name: funny_name_backstory
+description: Create a humorous backstory based on your name
+model: anthropic:claude-3-5-sonnet
+
+steps:
+  # Collect user's name
+  - input:
+      prompt: "What's your name?"
+      name: user_name
+      required: true
+  
+  # Ask for preferences
+  - input:
+      prompt: "Pick a genre for your backstory:"
+      type: choice
+      options:
+        - "Epic Fantasy Adventure"
+        - "Cyberpunk Hacker"
+        - "Time-Traveling Detective"
+        - "Intergalactic Pizza Delivery"
+        - "Victorian-Era Vampire Hunter"
+        - "Professional Cat Whisperer"
+      name: genre
+  
+  # Generate the backstory
+  - create_backstory

data/examples/user_input/generate_summary/prompt.md

@@ -0,0 +1,11 @@
+Please generate a nicely formatted survey summary based on the following information:
+
+Survey Participant: <%= workflow.output.developer_name %>
+Usage Duration: <%= workflow.output.usage_duration %>
+Experience Rating: <%= workflow.output.experience_rating %>
+Primary Feature Used: <%= workflow.output.primary_feature %>
+Additional Feedback Provided: <%= workflow.output.user_feedback %>
+Contact Permission: <%= workflow.output.allow_contact %>
+Email (if provided): <%= workflow.output.user_email %>
+
+Format this as a professional survey summary report with proper headings and thank the participant for their time.

data/examples/user_input/simple_input_demo/workflow.yml

@@ -0,0 +1,35 @@
+name: simple_input_demo
+description: Simple demonstration of input step functionality
+model: gpt-4o
+
+steps:
+  # Text input
+  - input:
+      prompt: "What's your name?"
+      name: user_name
+      required: true
+  
+  - input:
+      prompt: "Are you enjoying Roast?"
+      type: boolean
+      default: true
+      name: enjoying_roast
+  
+  - input:
+      prompt: "What's your favorite programming language?"
+      type: choice
+      options:
+        - Ruby
+        - Python
+        - JavaScript
+        - Go
+        - Other
+      name: favorite_language
+  
+  - input:
+      prompt: "Create a secret password (won't be displayed):"
+      type: password
+      required: true
+      name: secret_password
+  
+  - "Summarize the following inputs: {{workflow.output}}"

data/examples/user_input/survey_workflow.yml

@@ -0,0 +1,71 @@
+name: developer_survey
+description: Collect developer feedback through an interactive survey
+model: anthropic:claude-3-5-sonnet
+
+steps:
+  - welcome_message
+  
+  # Basic information
+  - input:
+      prompt: "What's your name?"
+      name: developer_name
+      required: true
+  
+  - input:
+      prompt: "How long have you been using Roast? (e.g., '2 weeks', '3 months')"
+      name: usage_duration
+  
+  # Experience rating
+  - input:
+      prompt: "How would you rate your experience with Roast?"
+      type: choice
+      options:
+        - "⭐ Poor"
+        - "⭐⭐ Below Average"
+        - "⭐⭐⭐ Average"
+        - "⭐⭐⭐⭐ Good"
+        - "⭐⭐⭐⭐⭐ Excellent"
+      name: experience_rating
+      required: true
+  
+  # Feature usage
+  - input:
+      prompt: "Which Roast features do you use most? (select primary feature)"
+      type: choice
+      options:
+        - "AI-powered workflows"
+        - "File processing and manipulation"
+        - "Conditional execution (if/case)"
+        - "Iteration features (each/repeat)"
+        - "Tool integrations"
+        - "Other"
+      name: primary_feature
+  
+  # Feedback collection
+  - input:
+      prompt: "Would you like to provide additional feedback?"
+      type: boolean
+      default: true
+      name: wants_feedback
+  
+  - if: "{{workflow.output.wants_feedback}}"
+    then:
+      - input:
+          prompt: "Please share your feedback (press Enter twice when done):"
+          name: user_feedback
+      
+      - input:
+          prompt: "May we contact you about your feedback?"
+          type: boolean
+          default: false
+          name: allow_contact
+      
+      - if: "{{workflow.output.allow_contact}}"
+        then:
+          - input:
+              prompt: "Please enter your email:"
+              name: user_email
+              required: true
+  
+  # Generate summary
+  - generate_summary

data/examples/user_input/welcome_message/prompt.md

@@ -0,0 +1,3 @@
+Welcome to the Roast Developer Survey! 🎯
+
+You don't need to do anything here - just acknowledge this message and we'll proceed with collecting your feedback.