GitHub Actions

Claude Code workflow

Minimal workflow using Anthropic’s anthropics/claude-code-action@v1. Boost setup runs before Claude so the agent inherits the binary and hooks.

name: Claude Code with Boost

on:
  issue_comment:
    types: [created]
  pull_request_review_comment:
    types: [created]
  issues:
    types: [opened, assigned]
  pull_request_review:
    types: [submitted]

jobs:
  claude:
    if: |
      (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: ubuntu-latest
    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: Install Boost
        run: |
          set -euo pipefail
          curl -fsSL https://boost.jfrog.com/install.sh | bash
          echo "$HOME/.local/bin" >> "$GITHUB_PATH"
          export PATH="$HOME/.local/bin:$PATH"
          boost init --claude --global --accept-terms

      - name: Verify Boost on PATH
        run: |
          set -euo pipefail
          command -v boost
          boost version

      - name: Run Claude Code
        uses: anthropics/claude-code-action@v1
        with:
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}

What the steps do

• Install Boost — downloads the CLI with install.sh (not jfrog/boost@v0).
• PATH — echo … >> "$GITHUB_PATH" exposes boost to later steps. The same step also exports PATH before boost init, because $GITHUB_PATH only applies to subsequent steps.
• boost init --claude — installs Claude Code hooks on the runner. Without this, Claude will not use Boost rewrite hooks. --global --accept-terms keeps CI non-interactive and records terms in ~/.boost/config.toml.
• Verify — command -v boost and boost version should succeed before Claude starts. Drop this step once the job is stable if you prefer a shorter workflow.
• Run Claude Code — keep this after Boost setup so the agent inherits the installed binary and hooks.

Prerequisites

• A Linux runner (ubuntu-latest or similar).
• Preview terms accepted via boost init … --accept-terms (writes ~/.boost/config.toml). Repo .boost/config.toml does not satisfy the terms gate.
• An Anthropic credential for the job (typically secrets.ANTHROPIC_API_KEY), plus the permissions Claude Code needs (contents, pull-requests, issues, id-token, and usually actions: read).

Authentication

Store your Anthropic API key as a repository secret, then pass it into the Claude Code action (or set it as a job env var):

env:
  ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}

About jfrog/boost@v0

The published jfrog/boost action currently accepts legacy inputs but runs as a no-op — it does not install the CLI. Prefer install.sh when you need boost on the runner.