Automated code reviews

This workflow analyzes all opened or updated pull requests, identifies issues, and posts feedback as comments.
It uses the use_single_comment: true parameter to update the same comment on subsequent runs instead of adding new comments.
# .github/workflows/code-review.yml
name: Code Review

on:
  pull_request:
    types: [opened, synchronize]

jobs:
  review:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
      issues: write
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 1

      - uses: JetBrains/junie-github-action@v0
        with:
          junie_api_key: ${{ secrets.JUNIE_API_KEY }}
          # Update the same comment on subsequent runs instead of adding new comments
          use_single_comment: true
          # Customize the review criteria, summary format, or additional instructions as required
          prompt: |
            Your task is to:
            1. Download the Pull Request diff using `gh pr diff ${{ github.event.pull_request.head.ref }}`
            2. Review the downloaded diff according to the criteria below
            3. Output summary following the template below using `submit` action
            
            ## Review Criteria
            
            ```
            **Security:**
            - SQL injection, XSS, exposed secrets
              - Authentication/authorization issues
              - Input validation vulnerabilities
            
            **Performance:**
            - N+1 queries, memory leaks
              - Inefficient algorithms (nested loops, etc.)
              - Blocking operations
            
            **Code Quality:**
            - Complexity, duplication, naming
              - Missing tests for new logic
              - Undocumented complex logic
            ```
            
            ## Summary template
            
            ```
            ## 🎯 Summary
            [2-3 sentences overall assessment]
            
            ## ⚠️ Issues Found
            [Each issue: File:line, Severity (Critical/High/Medium/Low), Description, Suggested fix with code example]
            
            ## ✨ Highlights
            [1-2 things done well]
            
            ## 📋 Checklist
            - [ ] Security: No vulnerabilities
              - [ ] Tests: Adequate coverage
              - [ ] Performance: No bottlenecks
              - [ ] Documentation: Complex logic explained

            ## Additional instructions
            - Strictly follow the plan above (`Your task is to:` section)
            - You are not expected to explore the repo. Do review solely based on the downloaded diff
            - You are not expected to run any code or any commands except `gh pr diff`
26 January 2026