talkable-style 1.2024.1101 → 1.2026.0730

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3c91e7099127c140a0343e8144402b3c3baad9d7744155f9ff39ec40b705cfd4
-  data.tar.gz: d178cee0b57a8f8b9b955dd5f67faa21c3307473d9739533ab91f29c272d3365
+  metadata.gz: 79d26ba5c41c3fa1e00856ceea66e97dcfbdee24a6287ce991daf16c04739c71
+  data.tar.gz: 658ee9af66f27ef07fef68b2e08d7597e225a25ae64070bd34c2cd736f553e6d
 SHA512:
-  metadata.gz: 426f0bc807f8e7dcfaccc4263ef70d8e3c81d6a09962b87aec534d3a62e222db3a3f4a8e505d1b8b7f8760cbcf340b7f915343d92db4afb950268a8bf0e05a32
-  data.tar.gz: 256ea1ad0c51c7618872caaba23d13042163ef10f550f296cc14392f7f5acf08701eebd9491f8ec88aa5db65682fac51821e06c0ffd1bd638e6b9e2df9ea4580
+  metadata.gz: f9983b13c949f0bb30d45d49b49ba515326c0244e74b85e64d0bb66cdcb501d098cc5b38e00a15911b3a69fcfa2a828fd6bf185cfe0d3d52d49867c7262441fa
+  data.tar.gz: ad08a2b78a19bd00b92b38858f95b82ecaba4ec75275ffe45af9e354c2192c8b4f67c84bd1aee5b5d3b50cc16ed7a44a3190205429fbb9bb4037e8420a03ebf5

data/.github/actions/setup-apt-packages/action.yml

@@ -0,0 +1,88 @@
+# See https://github.com/actions/runner-images/issues/1120
+name: Setup APT packages
+description: Install APT packages with retry logic to handle lock conflicts
+
+inputs:
+  packages:
+    description: Space-separated list of packages to install
+    required: true
+
+runs:
+  using: composite
+  steps:
+    - name: Install APT packages
+      shell: bash
+      run: |
+        # Stop unattended-upgrades to prevent dpkg lock conflicts
+        sudo systemctl stop unattended-upgrades.service || true
+        sudo systemctl kill --kill-who=all unattended-upgrades.service || true
+
+        # Retry apt-get update up to 3 times to handle lock conflicts and mirror sync issues
+        for i in {1..3}; do
+          echo "Attempt $i: Updating package lists..."
+
+          # Wait for any existing dpkg processes to finish
+          timeout=60
+          elapsed=0
+          while sudo fuser /var/lib/dpkg/lock-frontend >/dev/null 2>&1; do
+            if [ $elapsed -ge $timeout ]; then
+              echo "Timeout waiting for dpkg lock to be released"
+              break
+            fi
+            echo "Waiting for existing dpkg processes to finish..."
+            sleep 2
+            elapsed=$((elapsed + 2))
+          done
+
+          # Run apt-get update and capture output
+          if output=$(sudo apt-get update 2>&1); then
+            echo "Package lists updated successfully"
+            break
+          else
+            echo "Update failed with output:"
+            echo "$output"
+
+            if [ $i -lt 3 ]; then
+              echo "Waiting 10 seconds before retry..."
+              sleep 10
+            else
+              echo "Failed to update package lists after 3 attempts"
+              exit 1
+            fi
+          fi
+        done
+
+        # Retry apt-get install up to 3 times to handle lock conflicts
+        for i in {1..3}; do
+          echo "Attempt $i: Installing packages..."
+
+          # Wait for any existing dpkg processes to finish
+          timeout=60
+          elapsed=0
+          while sudo fuser /var/lib/dpkg/lock-frontend >/dev/null 2>&1; do
+            if [ $elapsed -ge $timeout ]; then
+              echo "Timeout waiting for dpkg lock to be released"
+              break
+            fi
+            echo "Waiting for existing dpkg processes to finish..."
+            sleep 2
+            elapsed=$((elapsed + 2))
+          done
+
+          # Run apt-get install and capture output
+          if output=$(sudo apt-get install -y --no-install-recommends ${{ inputs.packages }} 2>&1); then
+            echo "Packages installed successfully"
+            break
+          else
+            echo "Install failed with output:"
+            echo "$output"
+
+            if [ $i -lt 3 ]; then
+              echo "Waiting 10 seconds before retry..."
+              sleep 10
+            else
+              echo "Failed to install packages after 3 attempts"
+              exit 1
+            fi
+          fi
+        done

data/.github/workflows/claude-code-review.yml

@@ -0,0 +1,258 @@
+name: Claude Code Review
+
+on:
+  workflow_call:
+    inputs:
+      runs-on:
+        description: The type of machine to run the job on
+        default: ubuntu-latest
+        type: string
+    secrets:
+      CLAUDE_CODE_OAUTH_TOKEN:
+        required: true
+
+jobs:
+  claude-review:
+    if: |
+      github.event.sender.type != 'Bot' &&
+      github.actor != 'talkable-bot' &&
+      (
+        github.event_name == 'pull_request' ||
+        (
+          github.event_name == 'issue_comment' &&
+          contains(github.event.comment.body, '/claude-review')
+        )
+      )
+
+    runs-on: ${{ inputs.runs-on }}
+    permissions:
+      actions: read
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 1
+
+      # Removes any local .mcp.json file to ensure Claude Code Action uses its built-in GitHub MCP credentials
+      - name: Clean up local MCP configuration
+        run: rm -f .mcp.json
+
+      - name: Run Claude Code Review
+        id: claude-review
+        uses: anthropics/claude-code-action@v1
+        with:
+          use_sticky_comment: true
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          claude_args: |
+            --model claude-opus-5
+            --fallback-model claude-sonnet-5
+            --allowedTools "mcp__github__create_pending_pull_request_review,mcp__github__add_comment_to_pending_review,mcp__github__submit_pending_pull_request_review,mcp__github__get_pull_request_diff"
+
+          prompt: |
+            You are an expert code reviewer specializing in identifying bugs, performance bottlenecks, and logical
+            errors in pull requests. Your task is to perform a thorough, constructive code review of this pull request,
+            focusing on improving code quality.
+
+            REPO: ${{ github.repository }}
+            PR NUMBER: ${{ github.event_name == 'pull_request' && github.event.pull_request.number || github.event.issue.number }}
+
+            Note: The PR branch is already checked out in the current working directory.
+
+            CRITICAL LINE NUMBER GUIDANCE: When using `mcp__github__add_comment_to_pending_review`,
+            the `line` parameter must be the ACTUAL LINE NUMBER in the file, counting from 1 (not 0).
+
+            For NEW FILES (those starting with "new file mode" in the diff):
+            - Line 1 is the first line after "@@ -0,0 +1,XX @@"
+            - Count each subsequent line sequentially: 1, 2, 3, etc.
+            - The line number you specify is the actual line number in the new file
+
+            For MODIFIED FILES:
+            - Use the line number shown on the RIGHT side of the diff (after the + or space)
+            - These represent the line numbers in the new version of the file
+
+            For example, if reviewing a new file with this diff:
+            ```
+            @@ -0,0 +1,29 @@
+            +#!/usr/bin/env bash
+            +
+            +if [ -z "$CIRCLE_PULL_REQUEST" ]; then
+            +  echo "Not a Pull Request, skipping Shippie."
+            +  exit 0
+            +fi
+            +
+            +export PRONTO_GITHUB_SLUG="$CIRCLE_PROJECT_USERNAME/$CIRCLE_PROJECT_REPONAME"
+            +export PRONTO_PULL_REQUEST_ID=$(echo "$CIRCLE_PULL_REQUEST" | grep -o 'pull.*' | cut -f2- -d/)
+            +
+            +url="https://api.github.com/repos/$PRONTO_GITHUB_SLUG/pulls/$PRONTO_PULL_REQUEST_ID"
+            +targetBranch=$(curl -H "Authorization: token $PRONTO_GITHUB_ACCESS_TOKEN" "$url" | jq '.base.ref' | tr -d '"')
+            ```
+
+            The line numbers are:
+            - Line 1: #!/usr/bin/env bash
+            - Line 2: (empty line)
+            - Line 3: if [ -z "$CIRCLE_PULL_REQUEST" ]; then
+            - ...
+            - Line 11: url="https://api.github.com/repos/$PRONTO_GITHUB_SLUG/pulls/$PRONTO_PULL_REQUEST_ID"
+            - Line 12: targetBranch=$(curl -H "Authorization: token $PRONTO_GITHUB_ACCESS_TOKEN" "$url" | jq '.base.ref' | tr -d '"')
+
+            To comment on the line with $PRONTO_GITHUB_ACCESS_TOKEN, use line: 12 (NOT 11).
+
+            Review Process:
+            1. Start a review using the `mcp__github__create_pending_pull_request_review` function.
+            2. Get the pull request diff information using the `mcp__github__get_pull_request_diff` function.
+            3. CAREFULLY note the line numbers shown in the diff for the RIGHT side (new file).
+            4. Analyze each file in the pull request systematically.
+            5. For each file, examine:
+              - The specific changes made
+              - How those changes interact with existing code
+              - Potential side effects or breaking changes
+            6. Identify issues in the following categories:
+              a. Bugs & Logic Errors
+              b. Performance Issues
+              c. Security Vulnerabilities
+              d. Code Quality & Maintainability
+              e. Architecture & Design
+              f. Testing Coverage
+            7. Categorize issues as Critical, Important, or Suggestions
+            8. Provide specific, actionable feedback with code examples using inline comments
+            9. When adding comments, use the EXACT line number shown in the diff for the specific line you're commenting on
+            10. After analyzing all files, submit the review with a summary comment
+            11. REMEMBER: You will submit review as COMMENT only, not approve/request changes
+
+            For each issue category, consider the following:
+
+            a. Bugs & Logic Errors:
+              - Potential null pointer exceptions or undefined behavior
+              - Off-by-one errors, incorrect boolean logic, or state management issues
+              - Error handling and edge case coverage
+              - Race conditions or concurrency issues
+              - Data transformations and type conversions
+
+            b. Performance Issues:
+              - N+1 query problems or inefficient database queries
+              - Unnecessary loops, redundant operations, or algorithmic inefficiencies
+              - Memory leaks or excessive memory allocation
+              - Caching opportunities
+              - Scalability of the solution
+
+            c. Security Vulnerabilities:
+              - SQL injection vulnerabilities
+              - Potential XSS or CSRF issues
+              - Authentication and authorization
+              - Exposed sensitive data (API keys, tokens) or improper sanitization
+              - Timing attacks or resource exhaustion vulnerabilities
+
+            d. Code Quality & Maintainability:
+              - Code readability and clarity
+              - Violations of DRY (Don't Repeat Yourself) principle
+              - Separation of concerns
+              - Consistent error handling patterns
+              - Missing validations or assertions
+
+            e. Architecture & Design:
+              - Alignment with existing patterns in the codebase
+              - Proper use of design patterns
+              - Database schema changes and migrations
+              - API contract changes and backwards compatibility
+              - Coupling and abstractions
+
+            f. Testing Coverage:
+              - Critical business logic test coverage
+              - Spec files for new service objects
+              - Factory definitions for new models
+              - System tests for end-to-end referral flows
+              - Reversible and tested database migrations
+
+            Before providing inline comments and the final review, wrap your analysis inside <file_analysis> tags. For each file:
+
+            1. List the specific changes made WITH THEIR EXACT LINE NUMBERS FROM THE DIFF
+            2. Analyze how these changes interact with existing code
+            3. Identify potential side effects or breaking changes
+            4. List all potential issues found, WITH THE EXACT LINE NUMBER where each issue occurs
+            5. For each potential issue:
+              - Note the EXACT line number from the diff where the issue is located
+              - Consider and note its impact on different aspects of the system (e.g., performance, security, maintainability)
+              - Assign a priority (Critical 🚨, Important ⚠️, or Suggestion 💡) based on its severity and impact
+            6. Prioritize the issues based on their assigned priorities and system impact
+
+            This process will help ensure a thorough interpretation of the code changes.
+            It's OK for this section to be quite long.
+            <file_analysis> tags are only for your analysis, do not include them in your final review.
+
+            Example of internal analysis (DO NOT OUTPUT THIS):
+
+            <file_analysis>
+            File: app/models/user.rb
+            1. Changes:
+              - Added new method `calculate_referral_bonus` (lines 45-52 in diff)
+              - Modified `update_profile` method (lines 78-85 in diff)
+
+            2. Interactions with existing code:
+              - New method called in referral processing workflow
+              - Modified method affects user profile updates
+
+            3. Potential side effects:
+              - Changes to referral bonus calculation may impact existing users
+              - Profile update changes could affect downstream processes
+
+            4. Potential issues:
+              - Performance: `calculate_referral_bonus` uses inefficient query (N+1 problem) - LINE 47 in diff
+              - Security: Referral bonus calculation not properly sanitized - LINE 49 in diff
+              - Testing: Missing unit test for edge cases in `update_profile` - LINE 82 in diff
+              - Code Quality: Duplication in error handling logic - LINES 51 and 84 in diff
+
+            5. System impact:
+              - Performance issue on LINE 47 could slow down referral processing for all users
+              - Security vulnerability on LINE 49 may expose the system to financial exploitation
+              - Lack of testing for changes on LINE 82 increases risk of regressions in user profile management
+              - Code duplication on LINES 51 and 84 may lead to inconsistent error handling across the application
+            ...
+            </file_analysis>
+
+            After your analysis, provide inline comments using the `mcp__github__add_comment_to_pending_review` function. For each issue:
+            - Use the EXACT line number from the diff (not calculated or offset)
+            - Clearly explain the problem
+            - Provide the impact/consequences
+            - Suggest a specific solution with code examples
+            - Double-check that the line number matches where the issue actually appears in the diff
+
+            Remember to:
+            - Be constructive and professional
+            - Provide concrete examples and solutions
+            - Consider the broader system impact
+            - Verify that tests adequately cover the changes
+            - Check that documentation is updated if needed
+            - ALWAYS use the exact line numbers shown in the GitHub diff
+
+            After adding all inline comments, you MUST submit the review using the `mcp__github__submit_pending_pull_request_review` function with:
+            - event: "COMMENT" (MANDATORY - DO NOT USE "APPROVE" OR "REQUEST_CHANGES")
+
+            ⚠️ IMPORTANT: You are providing code review feedback ONLY:
+            - Always use event: "COMMENT" when calling `mcp__github__add_comment_to_pending_review`
+            - NEVER use event: "APPROVE" or event: "REQUEST_CHANGES" (this would approve or block the PR)
+            - This applies regardless of the code quality or number of issues found
+
+            Include a summary review comment with the following structure:
+
+            ```markdown
+            ## Summary
+            [Brief overview of the PR and its purpose]
+
+            ## Key Observations
+            - [List 3-5 main points about the changes]
+
+            ## Recommendations
+            - [List 2-3 high-level recommendations]
+
+            ## Overall Assessment
+            [1-2 sentences on the overall quality and readiness of the PR]
+
+            ---
+            💡 To request another review, post a new comment with "/claude-review".
+            ```

data/.github/workflows/claude.yml

@@ -0,0 +1,53 @@
+name: Claude Tag
+
+on:
+  workflow_call:
+    inputs:
+      runs-on:
+        description: The type of machine to run the job on
+        default: ubuntu-latest
+        type: string
+      allowed-non-write-users:
+        description: Comma-separated list of usernames allowed without write permissions
+        default: ''
+        type: string
+    secrets:
+      CLAUDE_CODE_OAUTH_TOKEN:
+        required: true
+      TALKABLE_BOT_GITHUB_ACCESS_TOKEN:
+        required: false
+
+jobs:
+  claude:
+    if: |
+      github.event.sender.type != 'Bot' &&
+      github.actor != 'talkable-bot' &&
+      (
+        (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
+        (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
+        (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
+        (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
+      )
+
+    runs-on: ${{ inputs.runs-on }}
+    permissions:
+      contents: write
+      pull-requests: write
+      issues: write
+      id-token: write
+      actions: read
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude
+        uses: anthropics/claude-code-action@v1
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          github_token: ${{ secrets.TALKABLE_BOT_GITHUB_ACCESS_TOKEN }}
+          allowed_non_write_users: ${{ inputs.allowed-non-write-users }}
+          additional_permissions: |
+            actions: read

data/.github/workflows/droid.yml

@@ -0,0 +1,43 @@
+name: Droid Tag
+
+on:
+  workflow_call:
+    inputs:
+      runs-on:
+        description: The type of machine to run the job on
+        default: ubuntu-latest
+        type: string
+    secrets:
+      FACTORY_API_KEY:
+        required: true
+
+jobs:
+  droid:
+    if: |
+      github.event.sender.type != 'Bot' &&
+      github.actor != 'talkable-bot' &&
+      (
+        (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@droid')) ||
+        (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@droid')) ||
+        (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@droid')) ||
+        (github.event_name == 'issues' && (contains(github.event.issue.body, '@droid') || contains(github.event.issue.title, '@droid')))
+      )
+
+    runs-on: ${{ inputs.runs-on }}
+    permissions:
+      contents: write
+      pull-requests: write
+      issues: write
+      id-token: write
+      actions: read
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 1
+
+      - name: Run Droid
+        uses: Factory-AI/droid-action@v5
+        with:
+          factory_api_key: ${{ secrets.FACTORY_API_KEY }}

data/.github/workflows/pr-agent.yml

@@ -0,0 +1,51 @@
+name: PR Agent
+
+on:
+  workflow_call:
+    inputs:
+      runs-on:
+        description: The type of machine to run the job on
+        default: ubuntu-latest
+        type: string
+    secrets:
+      OPENAI_KEY:
+        required: true
+      TALKABLE_BOT_GITHUB_ACCESS_TOKEN:
+        required: true
+
+jobs:
+  pr-agent:
+    if: |
+      github.event.sender.type != 'Bot' &&
+      github.actor != 'talkable-bot' &&
+      (
+        github.event_name == 'pull_request' ||
+        (
+          github.event_name == 'issue_comment' &&
+          (
+            contains(github.event.comment.body, '/describe') ||
+            contains(github.event.comment.body, '/improve') ||
+            contains(github.event.comment.body, '/review')
+          )
+        )
+      )
+
+    runs-on: ${{ inputs.runs-on }}
+    permissions:
+      issues: write
+      pull-requests: write
+      contents: write
+
+    steps:
+      - name: PR Agent action step
+        id: pragent
+        uses: the-pr-agent/pr-agent@main
+        env:
+          OPENAI_KEY: ${{ secrets.OPENAI_KEY }}
+          GITHUB_TOKEN: ${{ secrets.TALKABLE_BOT_GITHUB_ACCESS_TOKEN }}
+          github_action_config.auto_review: "true"
+          github_action_config.auto_describe: "true"
+          github_action_config.auto_improve: "false"
+          config.model: "gpt-5.6"
+          config.fallback_models: '["gpt-5.6-terra"]'
+          pr_reviewer.extra_instructions: "Focus on identifying bugs, performance bottlenecks, logical errors and security issues."

data/.github/workflows/pr-review.yml

@@ -0,0 +1,107 @@
+name: PR Review by OpenHands
+
+on:
+  workflow_call:
+    inputs:
+      runs-on:
+        description: The type of machine to run the job on
+        default: ubuntu-latest
+        type: string
+    secrets:
+      OPENAI_KEY:
+        required: true
+      TALKABLE_BOT_GITHUB_ACCESS_TOKEN:
+        required: true
+
+jobs:
+  pr-review:
+    if: |
+      github.event.sender.type != 'Bot' &&
+      github.actor != 'talkable-bot' &&
+      (
+        github.event_name == 'pull_request' ||
+        (
+          github.event_name == 'issue_comment' &&
+          contains(github.event.comment.body, '/pr-review')
+        )
+      )
+
+    runs-on: ${{ inputs.runs-on }}
+    permissions:
+      issues: write
+      pull-requests: write
+      contents: read
+
+    steps:
+      - name: Checkout software-agent-sdk repository
+        uses: actions/checkout@v7
+        with:
+          repository: OpenHands/software-agent-sdk
+          path: software-agent-sdk
+
+      - name: Get PR details
+        id: pr-details
+        env:
+          GH_TOKEN: ${{ secrets.TALKABLE_BOT_GITHUB_ACCESS_TOKEN }}
+        run: |
+          if [[ "${{ github.event_name }}" == "issue_comment" ]]; then
+            PR_NUMBER=${{ github.event.issue.number }}
+            PR_DATA=$(gh api repos/${{ github.repository }}/pulls/$PR_NUMBER)
+            echo "pr_number=$PR_NUMBER" >> $GITHUB_OUTPUT
+            echo "pr_title=$(echo "$PR_DATA" | jq -r '.title')" >> $GITHUB_OUTPUT
+            echo "pr_body<<EOF" >> $GITHUB_OUTPUT
+            echo "$PR_DATA" | jq -r '.body // ""' >> $GITHUB_OUTPUT
+            echo "EOF" >> $GITHUB_OUTPUT
+            echo "pr_head_branch=$(echo "$PR_DATA" | jq -r '.head.ref')" >> $GITHUB_OUTPUT
+            echo "pr_base_branch=$(echo "$PR_DATA" | jq -r '.base.ref')" >> $GITHUB_OUTPUT
+          else
+            echo "pr_number=${{ github.event.pull_request.number }}" >> $GITHUB_OUTPUT
+            echo "pr_title=${{ github.event.pull_request.title }}" >> $GITHUB_OUTPUT
+            echo "pr_body<<EOF" >> $GITHUB_OUTPUT
+            echo "${{ github.event.pull_request.body }}" >> $GITHUB_OUTPUT
+            echo "EOF" >> $GITHUB_OUTPUT
+            echo "pr_head_branch=${{ github.event.pull_request.head.ref }}" >> $GITHUB_OUTPUT
+            echo "pr_base_branch=${{ github.event.pull_request.base.ref }}" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Checkout PR repository
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+          path: pr-repo
+          ref: ${{ steps.pr-details.outputs.pr_head_branch }}
+
+      - name: Set up Python
+        uses: actions/setup-python@v7
+        with:
+          python-version: '3.14'
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        with:
+          enable-cache: true
+
+      - name: Install OpenHands dependencies
+        run: |
+          # Install OpenHands SDK and tools from git repository
+          uv pip install --system "openhands-sdk @ git+https://github.com/OpenHands/software-agent-sdk.git@main#subdirectory=openhands-sdk"
+          uv pip install --system "openhands-tools @ git+https://github.com/OpenHands/software-agent-sdk.git@main#subdirectory=openhands-tools"
+
+      - name: Run PR review
+        env:
+          GITHUB_TOKEN: ${{ secrets.TALKABLE_BOT_GITHUB_ACCESS_TOKEN }}
+          LLM_API_KEY: ${{ secrets.OPENAI_KEY }}
+          LLM_BASE_URL: https://api.openai.com/v1
+          LLM_MODEL: gpt-5.6
+          PR_BASE_BRANCH: ${{ steps.pr-details.outputs.pr_base_branch }}
+          PR_BODY: ${{ steps.pr-details.outputs.pr_body }}
+          PR_HEAD_BRANCH: ${{ steps.pr-details.outputs.pr_head_branch }}
+          PR_NUMBER: ${{ steps.pr-details.outputs.pr_number }}
+          PR_TITLE: ${{ steps.pr-details.outputs.pr_title }}
+          REPO_NAME: ${{ github.repository }}
+        run: |
+          # Change to the PR repository directory so agent can analyze the code
+          cd pr-repo
+
+          # Run the PR review script from the agent-sdk checkout
+          uv run python ../software-agent-sdk/examples/03_github_workflows/02_pr_review/agent_script.py

data/README.md

@@ -21,7 +21,7 @@ spec.add_development_dependency "talkable-style"
 And then run:
 
 ```bash
-$ bundle install
+bundle install
 ```
 
 ## Usage
@@ -37,7 +37,7 @@ inherit_gem:
 Now, run:
 
 ```bash
-$ bundle exec rubocop
+bundle exec rubocop
 ```
 
 You do not need to include rubocop directly in your application's dependencies. Talkable-style will include a specific version of `rubocop` and `rubocop-*` that is shared across all projects.

data/config/capybara.yml

@@ -1,24 +1,32 @@
-require: rubocop-capybara
+plugins: rubocop-capybara
 
-Capybara/ClickLinkOrButtonStyle:
+Capybara/AmbiguousClick:
   Enabled: true
-Capybara/CurrentPathExpectation:
+Capybara/AssertStyle:
   Enabled: true
-Capybara/MatchStyle:
+Capybara/FindAllFirst:
   Enabled: true
-Capybara/NegationMatcher:
+Capybara/RSpec/CurrentPathExpectation:
+  Enabled: true
+Capybara/RSpec/HaveContent:
   Enabled: true
 Capybara/RSpec/HaveSelector:
   Enabled: true
+Capybara/RSpec/MatchStyle:
+  Enabled: true
+Capybara/RSpec/NegationMatcher:
+  Enabled: true
+Capybara/RSpec/NegationMatcherAfterVisit:
+  Enabled: true
 Capybara/RSpec/PredicateMatcher:
   Enabled: true
+Capybara/RSpec/SpecificMatcher:
+  Enabled: true
+Capybara/RSpec/VisibilityMatcher:
+  Enabled: true
 Capybara/RedundantWithinFind:
   Enabled: true
 Capybara/SpecificActions:
   Enabled: true
 Capybara/SpecificFinders:
   Enabled: true
-Capybara/SpecificMatcher:
-  Enabled: true
-Capybara/VisibilityMatcher:
-  Enabled: true

data/config/discourse.yml

@@ -1,4 +1,5 @@
-require: rubocop-discourse
+plugins:
+  - rubocop-discourse
 
 Discourse/NoJsonParseResponse:
   Enabled: true