roast-ai 0.4.7 → 0.4.8

data/examples/mcp/fetch_pr_context/prompt.md

@@ -1,4 +0,0 @@
-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/filesystem_demo/create_test_file/prompt.md

@@ -1,2 +0,0 @@
-First, use the read_file Roast tool to read this workflow file itself (examples/mcp/filesystem_demo/workflow.yml).
-This is just to verify traditional tools work and show the content of the workflow.

data/examples/mcp/filesystem_demo/list_files/prompt.md

@@ -1,6 +0,0 @@
-Use the FileSystem MCP tool's list_directory function to list the contents of the /tmp directory.
-
-The function expects these parameters:
-- path: "/tmp"
-
-Show me what files and directories are in /tmp.

data/examples/mcp/filesystem_demo/read_with_mcp/prompt.md

@@ -1,7 +0,0 @@
-If you found any .txt, .md, or .log files in /tmp from the previous step, pick one and read it using the 
-FileSystem MCP tool's read_file function. 
-
-The function expects these parameters:
-- path: (the full path to the file you want to read)
-
-If no suitable text files were found, just say "No text files found in /tmp to read".

data/examples/mcp/filesystem_demo/workflow.yml

@@ -1,38 +0,0 @@
-# Filesystem MCP Example
-# This uses the filesystem MCP server which provides safe file operations
-
-name: Filesystem MCP Example
-model: gpt-4o-mini
-
-tools:
-  # Traditional Roast tools
-  - Roast::Tools::ReadFile
-  
-  # Filesystem MCP server
-  - FileSystem:
-      command: npx
-      args: ["-y", "@modelcontextprotocol/server-filesystem", "/tmp"]
-      only:
-        - read_file
-        - list_directory
-        - get_file_info
-
-steps:
-  - create_test_file
-  - list_files
-  - read_with_mcp
-
-create_test_file:
-  prompt: |
-    First, use the read_file Roast tool to read this workflow file itself (examples/mcp/filesystem_demo/workflow.yml).
-    This is just to verify traditional tools work.
-
-list_files:
-  prompt: |
-    Use the FileSystem MCP tool's list_directory function to list the contents of the /tmp directory.
-    The function expects a "path" parameter with value "/tmp".
-
-read_with_mcp:
-  prompt: |
-    If you see any .txt or .md files in /tmp from the previous step, try reading one with the 
-    FileSystem MCP tool's read_file function. Otherwise, just say "No text files found in /tmp".

data/examples/mcp/generate_insights/prompt.md

@@ -1,4 +0,0 @@
-Based on the schema and data quality analysis:
-1. Identify the most important tables for business operations
-2. Find opportunities for optimization (indexes, denormalization, etc.)
-3. Suggest data cleanup tasks if needed

data/examples/mcp/generate_report/prompt.md

@@ -1,6 +0,0 @@
-Generate a comprehensive bug analysis report that includes:
-- Total number of open bug issues
-- Categorization of bugs by type
-- List of critical issues
-- Recommendations for prioritization
-- Suggested next steps for the development team

data/examples/mcp/generate_review/prompt.md

@@ -1,16 +0,0 @@
-Generate a structured code review with:
-{
-  "summary": "Overall assessment",
-  "approval_status": "approve|request_changes|comment",
-  "issues": [
-    {
-      "severity": "critical|major|minor",
-      "file": "filename",
-      "line": 123,
-      "description": "Issue description",
-      "suggestion": "How to fix"
-    }
-  ],
-  "positive_feedback": ["What was done well"],
-  "documentation_updates": ["Required doc changes"]
-}

data/examples/mcp/github_workflow.yml

@@ -1,32 +0,0 @@
-# MCP GitHub Integration Example
-# This workflow demonstrates using the GitHub MCP server to interact with repositories
-
-name: GitHub Issue Analyzer
-model: gpt-4o-mini
-
-tools:
-  # Traditional Roast tool for writing output
-  - Roast::Tools::WriteFile
-  
-  # GitHub MCP tool - using npx to run the server
-  - GitHub:
-      command: npx
-      args:
-        - "-y"
-        - "@modelcontextprotocol/server-github"
-      env:
-        GITHUB_PERSONAL_ACCESS_TOKEN: "{{ENV['GITHUB_TOKEN']}}"
-      only:
-        - search_repositories
-        - get_repository
-        - get_issue
-        - list_issues
-        - create_issue
-        - create_pull_request
-        - search_code
-
-steps:
-  - search_issues
-  - analyze_issues
-  - generate_report
-  - save_report

data/examples/mcp/multi_mcp_workflow.yml

@@ -1,58 +0,0 @@
-# Multi-MCP Integration Example
-# This workflow combines multiple MCP tools with traditional Roast tools
-
-name: Code Review Assistant
-model: gpt-4o-mini
-target: "README.md"  # Use a static file for testing
-
-tools:
-  # Traditional Roast tools
-  - Roast::Tools::ReadFile
-  - Roast::Tools::Grep
-  - Roast::Tools::WriteFile
-  
-  # Multiple MCP tools
-  # - GitDocs:
-  #     url: https://gitmcp.io/{{ENV['REPO_OWNER']}}/{{ENV['REPO_NAME']}}/docs
-  #     env:
-  #       Accept: application/json
-  
-  # GitHub MCP (requires GITHUB_TOKEN environment variable)
-  # Uncomment to use:
-  # - GitHub:
-  #     command: npx
-  #     args: ["-y", "@modelcontextprotocol/server-github"]
-  #     env:
-  #       GITHUB_PERSONAL_ACCESS_TOKEN: "{{ENV['GITHUB_TOKEN']}}"
-  #     only:
-  #       - get_pull_request
-  #       - create_pull_request_comment
-  #       - get_file_content
-  
-  # Filesystem MCP (no auth required)
-  - FileSystem:
-      command: npx
-      args: ["-y", "@modelcontextprotocol/server-filesystem", "."]
-      only:
-        - read_file
-        - list_directory
-  
-  # - Linter:
-  #     command: ./custom-linter-mcp
-  #     env:
-  #       CONFIG_PATH: "{{ENV['LINTER_CONFIG']}}"
-  #     only:
-  #       - analyze_code
-  #       - suggest_fixes
-
-steps:
-  - test_read
-  - test_filesystem
-
-test_read:
-  prompt: Use the ReadFile tool to read the README.md file
-
-test_filesystem:
-  prompt: |
-    Use the FileSystem MCP tool's list_directory function to list the current directory.
-    Then pick an interesting file and read it with the read_file function.

data/examples/mcp/post_review/prompt.md

@@ -1,3 +0,0 @@
-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/mcp/save_report/prompt.md

@@ -1,6 +0,0 @@
-Using the write_file tool, save the bug analysis report to a file named "bug_analysis_report.md".
-
-The report content should be:
-<%= output.generate_report %>
-
-Save this to the file and confirm when complete.

data/examples/mcp/search_issues/prompt.md

@@ -1,2 +0,0 @@
-Using the GitHub tool, search for open issues with the "bug" label in the Shopify/roast repository.
-List the issue titles, numbers, and created dates.

data/examples/mcp/summarize/prompt.md

@@ -1 +0,0 @@
-Generate a brief summary, with one code example, in Markdown format.

data/examples/mcp/test_filesystem/prompt.md

@@ -1,6 +0,0 @@
-Use the FileSystem MCP tool to explore the current directory:
-
-1. First, use the list_directory function with path "." to see what files are here
-2. Then pick one interesting file (like a .yml or .md file) and read it using the read_file function
-
-This demonstrates using MCP tools for filesystem access.

data/examples/mcp/test_github/prompt.md

@@ -1,8 +0,0 @@
-Use the GitHub MCP tool's get_file_content function to fetch the README.md from the Shopify/roast repository.
-
-The function should be called with these parameters:
-- owner: "Shopify" 
-- repo: "roast"
-- path: "README.md"
-
-Then summarize what the README contains.

data/examples/mcp/test_read/prompt.md

@@ -1 +0,0 @@
-Use the read_file function to read the README.md file in the current directory and summarize what it contains.

data/examples/mcp/workflow.yml

@@ -1,35 +0,0 @@
-# usage: roast execute examples/mcp/workflow.yml -o output.md
-
-name: MCP Tools Example
-model: gpt-4o-mini
-tools:
-  # SSE MCP:
-  - Roast Docs:
-      url: https://gitmcp.io/Shopify/roast/docs
-      # Can pass headers for authentication
-      # env:
-      #   - "Authorization: Bearer {{resource.api_token}}"
-  # stdio MCPs are also supported
-  # - GitHub:
-  #     command: "docker",
-  #     args:
-  #       - "run"
-  #       - "-i"
-  #       - "--rm"
-  #       - "-e"
-  #       - "GITHUB_PERSONAL_ACCESS_TOKEN"
-  #       - "ghcr.io/github/github-mcp-server"
-  #     env:
-  #       GITHUB_PERSONAL_ACCESS_TOKEN: "<YOUR_TOKEN>"
-  #     only:
-  #       - get_issue
-  #       - get_issue_comments
-  #     except:
-  #       - create_issue
-
-steps:
-  - get_doc: Read the Roast docs, and tell me how to use MCP tools.
-  - summarize
-
-summarize:
-  print_response: true

data/examples/no_model_fallback/README.md

@@ -1,17 +0,0 @@
-# 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

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

data/examples/no_model_fallback/analyze_patterns/prompt.md

@@ -1,27 +0,0 @@
-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

@@ -1,10 +0,0 @@
-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

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

data/examples/no_model_fallback/sample.rb

@@ -1,42 +0,0 @@
-# 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

@@ -1,19 +0,0 @@
-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/openrouter_example/README.md

@@ -1,48 +0,0 @@
-# OpenRouter Example
-
-This example demonstrates how to use OpenRouter with Roast to access models from different providers through a single API.
-
-## Setup
-
-1. Sign up for an account at [OpenRouter](https://openrouter.ai/)
-2. Get your API key from the OpenRouter dashboard
-3. Set the API key as an environment variable:
-   ```bash
-   export OPENROUTER_API_KEY=your_api_key_here
-   ```
-
-## Running the Example
-
-```bash
-# Run without a specific target (general analysis)
-roast execute workflow.yml
-
-# Run with a specific file to analyze
-roast execute workflow.yml path/to/your/file.txt
-```
-
-## How it Works
-
-This example configures Roast to use OpenRouter as the API provider:
-
-```yaml
-api_provider: openrouter
-api_token: $(echo $OPENROUTER_API_KEY)
-model: anthropic/claude-3-haiku-20240307
-```
-
-The workflow consists of two steps:
-1. `analyze_input`: Analyzes the provided content (or generates general insights if no target is provided)
-2. `generate_response`: Creates a structured response based on the analysis
-
-## Available Models
-
-When using OpenRouter, you can access models from multiple providers by specifying the fully qualified model name, including the provider prefix. Some examples:
-
-- `anthropic/claude-3-opus-20240229`
-- `anthropic/claude-3-sonnet-20240229`
-- `meta/llama-3-70b-instruct`
-- `google/gemini-1.5-pro-latest`
-- `mistral/mistral-large-latest`
-
-Check the [OpenRouter documentation](https://openrouter.ai/docs) for the complete list of supported models.

data/examples/openrouter_example/analyze_input/prompt.md

@@ -1,16 +0,0 @@
-I'd like you to analyze the following input and provide your insights.
-
-<% if workflow.file && workflow.resource.content %>
-Here is the content to analyze:
-
-```
-<%= workflow.resource.content %>
-```
-<% else %>
-The workflow is running without a specific file target. Please provide general insights based on the context.
-<% end %>
-
-Please provide:
-1. A summary of the key points
-2. Any notable patterns or issues
-3. Recommendations based on your analysis

data/examples/openrouter_example/generate_response/prompt.md

@@ -1,9 +0,0 @@
-Based on the analysis from the previous step, please generate a response that addresses the findings.
-
-Your response should be well-structured and include:
-1. An introduction summarizing the analysis
-2. Detailed discussion of key points
-3. Clear recommendations for improvements
-4. A conclusion
-
-Format the response in markdown for better readability.

data/examples/openrouter_example/workflow.yml

@@ -1,12 +0,0 @@
-name: OpenRouter Example
-api_provider: openrouter
-api_token: $(echo $OPENROUTER_API_KEY)
-model: google/gemini-2.0-flash-001
-
-tools:
-  - Roast::Tools::ReadFile
-  - Roast::Tools::WriteFile
-
-steps:
-  - analyze_input
-  - generate_response

data/examples/pre_post_processing/README.md

@@ -1,111 +0,0 @@
-# Pre/Post Processing Example: Test Suite Optimization
-
-This example demonstrates how to use Roast's pre/post processing framework to optimize an entire test suite across multiple files.
-
-## Overview
-
-The workflow processes multiple test files, but performs setup and aggregation tasks only once:
-
-- **Pre-processing**: Runs once before any test files are processed
-  - Gathers baseline metrics for comparison
-  - Sets up the test environment
-  
-- **Main workflow**: Runs for each test file matching the target pattern
-  - Analyzes test quality and coverage
-  - Improves test coverage
-  - Optimizes test performance
-  - Validates changes
-  
-- **Post-processing**: Runs once after all test files have been processed
-  - Aggregates metrics from all files
-  - Generates a comprehensive report
-  - Cleans up the environment
-
-## Workflow Structure
-
-```yaml
-name: test_optimization
-model: gpt-4o
-target: "test/**/*_test.rb"
-
-pre_processing:
-  - gather_baseline_metrics
-  - setup_test_environment
-
-steps:
-  - analyze_test_file
-  - improve_test_coverage
-  - optimize_test_performance
-  - validate_changes
-
-post_processing:
-  - aggregate_metrics
-  - generate_summary_report
-  - cleanup_environment
-```
-
-## Directory Structure
-
-```
-pre_post_processing/
-├── workflow.yml
-├── pre_processing/
-│   ├── gather_baseline_metrics/
-│   │   └── prompt.md
-│   └── setup_test_environment/
-│       └── prompt.md
-├── analyze_test_file/
-│   └── prompt.md
-├── improve_test_coverage/
-│   └── prompt.md
-├── optimize_test_performance/
-│   └── prompt.md
-├── validate_changes/
-│   └── prompt.md
-└── post_processing/
-    ├── aggregate_metrics/
-    │   └── prompt.md
-    ├── generate_summary_report/
-    │   └── prompt.md
-    └── cleanup_environment/
-        └── prompt.md
-```
-
-## Key Features Demonstrated
-
-1. **Shared State**: Pre-processing results are available to all subsequent steps
-2. **Result Aggregation**: Post-processing has access to results from all workflow executions
-3. **One-time Operations**: Setup and cleanup happen only once, regardless of target count
-4. **Metrics Collection**: Each file's results are stored and aggregated for reporting
-
-## Running the Example
-
-```bash
-cd examples/pre_post_processing
-roast workflow.yml
-```
-
-This will:
-1. Run pre-processing steps once
-2. Process each test file matching `test/**/*_test.rb`
-3. Run post-processing steps once with access to all results
-4. Generate a comprehensive optimization report
-
-## Use Cases
-
-This pattern is ideal for:
-- **Code migrations**: Setup migration tools, process files, generate migration report
-- **Performance audits**: Baseline metrics, analyze files, aggregate improvements
-- **Documentation generation**: Analyze codebase, generate docs per file, create index
-- **Dependency updates**: Check current versions, update files, verify compatibility
-- **Security scanning**: Setup scanners, check each file, generate security report
-
-## Customization
-
-To adapt this example for your use case:
-
-1. Update the `target` pattern to match your files
-2. Modify pre-processing steps for your setup needs
-3. Adjust main workflow steps for your processing logic
-4. Customize post-processing for your reporting requirements
-5. Use appropriate AI models for each step type

data/examples/pre_post_processing/analyze_test_file/prompt.md

@@ -1,23 +0,0 @@
-# Analyze Test File
-
-Current test file: <%= file %>
-
-Please analyze this test file and identify:
-
-1. **Test Structure**: Number of test cases, test suites, and overall organization
-2. **Coverage Gaps**: Areas of the code that aren't adequately tested
-3. **Test Quality Issues**:
-   - Tests that are too brittle or implementation-dependent
-   - Missing edge cases
-   - Unclear test descriptions
-   - Excessive mocking that reduces test value
-4. **Performance Issues**:
-   - Slow setup/teardown methods
-   - Inefficient test data generation
-   - Unnecessary database operations
-5. **Opportunities for Improvement**:
-   - Tests that could be parameterized
-   - Common patterns that could be extracted to helpers
-   - Better use of test fixtures or factories
-
-Provide specific, actionable recommendations for each issue found.

data/examples/pre_post_processing/improve_test_coverage/prompt.md

@@ -1,17 +0,0 @@
-# Improve Test Coverage
-
-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
-3. **Enhance Assertions**: Add more specific assertions to catch regressions
-4. **Test Data**: Use more realistic test data that better represents production scenarios
-5. **Remove Redundancy**: Eliminate duplicate tests or merge similar ones
-
-Generate the improved test code and explain the rationale for each change.
-
-Remember to:
-- Maintain backward compatibility with existing test interfaces
-- Follow the project's testing conventions and style guide
-- Ensure new tests are fast and deterministic
-- Add appropriate comments for complex test scenarios