Claude Code Action: Platformizing AI Code

LINE NEXT transformed Claude Code from an individual productivity tool into an organization-wide code review platform integrated with GitHub Actions. The goal was to reduce review-quality variation, standardize policies, and make AI feedback part of the existing pull request workflow. Its central design separates simple repository-level invocation from centrally managed execution, prompts, permissions, and infrastructure.

Why AI Code Review Needed to Be Platformized

• As LINE NEXT’s services and repositories grew, human code review quality varied according to each reviewer’s experience and preferences.
• Developers were already using Claude Code locally, but individual usage created several problems:
  • Inconsistent review criteria and perspectives
  • No organization-wide quality process
  • AI feedback disconnected from pull request workflows
  • Difficulty providing new employees with a consistent review experience
• DevOps therefore treated the issue as a decentralized quality-process problem rather than merely a tooling problem.

Why GitHub Actions and Claude Code

• GitHub Actions was already the foundation for CI/CD and automation across LINE NEXT repositories.
• It allowed the team to:
  • Apply a common workflow repository by repository
  • Centrally manage execution environments and permissions
  • Avoid requiring each service team to build additional infrastructure
• Claude Code Action integrated directly with pull requests:
  • Developers could trigger reviews with an @claude mention.
  • Results appeared as GitHub comments or PR reviews.
  • Developers did not need to learn a separate interface.
• A shared GitHub App Runner environment provided consistent execution and centralized security controls.

Centralized Caller–Executor Architecture

• Service repositories act as callers:
  • They invoke the standard workflow.
  • They provide only basic parameters such as service name and review type.
• A centrally managed DevOps repository acts as the executor:
  • Stores prompts and review personas
  • Defines review policies and priorities
  • Manages permissions and authentication
  • Contains the actual execution logic
• This design makes AI review an organization-wide platform capability rather than a separate configuration maintained by every project.

Benefits of Central Control

• Consistent quality: Central prompts and personas ensure common review depth, tone, security checks, stability checks, and priorities.
• Faster adoption: New repositories need only add the standard workflow and specify a few parameters.
• Improved governance: GitHub Apps, centrally managed secrets, and shared runners make it possible to track who accessed which code and with what permissions.
• Lower operational overhead: Service teams use the platform without managing AI infrastructure themselves.

Handling Fork-Based Pull Requests

• The official Claude Code Action initially assumed that a PR branch existed in the base repository’s origin.
• For pull requests created from forks, this caused failures such as:

couldn't find remote ref

• The original implementation fetched and checked out the branch by name:

git fetch origin <branch>
git checkout <branch>

• This failed because fork branches exist in the external repository, not necessarily in the base repository.
• From a platform perspective, this was a structural limitation because it blocked external contributors and collaboration repositories.
• The proposed direction was to redesign the execution flow rather than simply add an exception, using GitHub’s special pull-request reference:

refs/pull/<PR number>/head

This approach allows the workflow to retrieve the actual pull request head commit regardless of whether the PR originated from the main repository or a fork.