Skip to main content
Integrations and remote

Qoder Action

Qoder Action is a standard GitHub Actions component that brings Qoder CLI CN's powerful capabilities into GitHub workflows, enabling intelligent code collaboration directly in PRs and Issues. With simple configuration, Qoder CLI CN runs on GitHub Actions Runners and provides teams with two out-of-the-box core capabilities: automatic PR review and @qoder interactive collaboration. Visit the Qoder Action repository →

Key features

  • Smart automatic PR review: every Pull Request automatically gets a comprehensive code review that detects code defects, security vulnerabilities, test coverage issues, and more, raising code quality before merge
  • @qoder always responsive: mention @qoder in any comment to get code explanations, implementation suggestions, or direct fixes
  • Deep project understanding: respects the project's code standards, architecture patterns, and business logic
  • Fast setup: configure in minutes and boost team efficiency immediately
  • Secure and reliable: code runs on GitHub Runners, keeping your data safe

Quick start

Manual configuration

1. Install the GitHub App and get an access token

  1. Visit Qoder Integrations
  2. Link your Qoder account with your GitHub account, and install the qoderai GitHub App to the target repository
  3. Generate a Qoder access token (Qoder Personal Access Token)
Note: if you have installed qoderai before, visit your GitHub App installations to check whether qoderai has a pending permission upgrade request, and grant the necessary permissions if so.

2. Add the Qoder access token to repository Secrets

In the repository's Settings > Secrets and variables > Actions, add QODERCN_PERSONAL_ACCESS_TOKEN to store the Qoder personal access token.

3. Choose and install a workflow

Visit Qoder Action examples, pick the workflow that fits your needs, and copy it into the repository's .github/workflows/ directory.
  • Code Review: automatically analyzes Pull Requests for code quality, test coverage, and security issues
  • Assistant: enables interactive conversation (@qoder) in Issues and PRs, explaining code or fixing problems

4. Start using it

  • Code Review: create a new Pull Request and wait for Qoder's feedback
  • Assistant: comment @qoder explain this code or @qoder fix this issue in any Issue or PR

Best practices

Customizing the output language

Specify the output language in the prompt:
- name: Run Qoder Code Review
  uses: QoderAI/qoder-action@v0
  with:
    qoder_personal_access_token: ${{ secrets.QODERCN_PERSONAL_ACCESS_TOKEN }}
    prompt: |
      /review-pr
      REPO:${{ github.repository }} PR_NUMBER:${{ github.event.pull_request.number }}
      OUTPUT_LANGUAGE: Chinese

Defining review rules with AGENTS.md

Create an AGENTS.md file in the repository root, and Qoder CLI CN automatically loads its content as context:
# Project code review guidelines

## Review focus
- All database queries must use parameterized queries; string concatenation is forbidden
- API endpoints must perform permission checks
- Sensitive information (passwords, tokens) must not be hardcoded or written to logs
- All external input must be validated and sanitized

## Checks that can be skipped
- Code duplication checks in test files (`*.test.js`, `*.spec.ts`)
- Code style issues in generated files (`generated/`, `dist/`)
- Complexity warnings in mock data files

## Team conventions
- Use async/await rather than Promise.then()
- Name components in PascalCase
- Name utility functions in camelCase
- Name constants in UPPER_SNAKE_CASE

Skipping reviews based on PR size

For large PRs, add a skip condition to avoid excessive credits consumption:
steps:
  - name: Check PR Size
    id: check_size
    run: |
      # Get the number of added lines in the PR
      LINES_CHANGED=$(jq .pull_request.additions < $GITHUB_EVENT_PATH)
      echo "Lines changed: $LINES_CHANGED"

      # Skip the review if it exceeds 500 lines, to control cost
      if [ "$LINES_CHANGED" -gt 500 ]; then
        echo "skip=true" >> $GITHUB_OUTPUT
      else
        echo "skip=false" >> $GITHUB_OUTPUT
      fi

  - uses: QoderAI/qoder-action@v0
    if: steps.check_size.outputs.skip == 'false'  # Run only when the PR size is under the threshold
    # ... other configuration
More configuration examples: visit the Recipes documentation for complete configuration examples and best practices.

Support