Automated code reviews

This workflow is triggered automatically to analyze all opened or updated pull requests and identify issues in them. When done, Junie adds a PR comment with a review summary and posts inline comments with suggestions directly to the PR.

The workflow uses a built-in code review prompt (prompt: "code-review") which sets pre-defined review criteria and output format. If needed, you can write your own review instructions in the prompt field instead of using the "code-review" value.

View the built-in code review prompt

Your task is to:

1. Get the Pull Request diff using \`${diffCommand}\`.
2. Review this diff according to the criteria below.
3. For each specific finding, use the 'post_inline_review_comment' tool (if available) to provide feedback directly on the code.
4. Once all findings are posted (or if the tool is unavailable), call the 'answer' tool with your review as a bullet point list in the 'full_answer' field.

Additional instructions:

1. Review ONLY the changed lines against the Core Review Areas below, prioritizing repository style/guidelines adherence and avoiding overcomplication.
2. You may open files or search the project to understand context. Do NOT run tests, build, or make any modifications.
3. Do NOT call 'submit'.

### Core Review Areas

1. **Adherence with this repository style and guidelines**

- Naming, formatting, and package structure consistency with existing code and modules.
- Reuse of existing utilities/patterns; avoiding introduction of new dependencies.

2. **Avoiding overcomplications**

- Avoid new abstractions, frameworks, premature generalization, or unnecessarily complicated solutions.
- Avoid touching of unrelated files.
- Avoid unnecessary indirection (wrappers, flags, configuration) and ensure straightforward control flow.
- Do not allow duplicate logic.

### If obviously applicable to the CHANGED lines only

- Security: newly introduced unsafe input handling, command execution, or data exposure.
- Performance: unnecessary allocations/loops/heavy work on UI thread introduced by the change.
- Error handling: swallowing exceptions or deviating from existing error-handling patterns.

### Output Format

- If the 'post_inline_review_comment' tool is available, use it for each specific finding.
- **Use the tool parameters correctly**:
    - \`filePath\`: The relative path to the file.
    - \`lineNumber\`: The line (or end of range) where the comment applies.
    - \`startLineNumber\`: Use this for multi-line comments to cover a range.
    - \`commentBody\`: Your explanation. Use the \`\`\`suggestion syntax here for code changes.
- Once all inline comments are posted, call the 'answer' tool with your review as a bullet point list in the 'full_answer' field.
- If the tool is NOT available, use the fallback format in 'full_answer' only: -\`File.ts:Line: Comment\`.
- Comment ONLY on lines added in this diff (\`+\` lines). Do not comment on pre-existing code.
- Keep it concise (15–25 words per comment). No praise, questions, or speculation; omit low-impact nits.
- If unsure whether a comment applies, omit it. If no feedback is warranted, answer \`LGTM\` only.
- For small changes, max 3 comments; medium 6–8; large 8–12.

The use_single_comment: true parameter updates the same comment on subsequent runs of Junie 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 Junie runs instead of adding new comments
          use_single_comment: true
          # Alternatively, write your custom review instructions in the prompt field 
          # instead of using the built-in "code-review" value
          prompt: "code-review"

Trigger code review on demand

You can also trigger the code review workflow by tagging @junie-agent with the code-review instruction in the pull request comment.

In this case, you don't need to add the code-review.yml workflow file: having any other Junie workflow with issue/PR comment triggers configured (for example, basic workflow) will work.

14 March 2026