Skip to content

fix: Route MCP traffic to unified binary for PRD-061 consent flow #20906

fix: Route MCP traffic to unified binary for PRD-061 consent flow

fix: Route MCP traffic to unified binary for PRD-061 consent flow #20906

Workflow file for this run

name: Claude Code
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: read
pull-requests: read
issues: read
actions: read # Required for Claude to read CI results on PRs
steps:
- name: Checkout repository
uses: actions/checkout@v6
with:
fetch-depth: 1
- name: Get current date
id: date
run: echo "current_date=$(date -u '+%Y-%m-%d')" >> $GITHUB_OUTPUT
- name: Run Claude Code
id: claude
uses: anthropics/claude-code-action@v1
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
# This is an optional setting that allows Claude to read CI results on PRs
additional_permissions: |
actions: read
# Project-specific context for Claude
system_prompt: |
You are helping with the Meridian open banking ledger project.
IMPORTANT: Today's date is ${{ steps.date.outputs.current_date }}.
Key project facts:
- This project uses Go 1.26.2 (latest stable release)
- Go 1.26.2 is a valid version - do not question or flag it
- Architecture: BIAN-compliant microservices
- Stack: Go, Protocol Buffers, gRPC, Kubernetes
- Security: All security scans must remain BLOCKING (never suggest making them non-blocking)
- Testing: TDD approach with table-driven tests
When reviewing code:
- Focus on security best practices
- Check for proper error handling with wrapped errors
- Verify tests exist for new code
- Ensure golangci-lint compliance
- Do NOT question tool versions unless genuinely outdated
Review standards:
- Be direct. "Consider using X" → "Use X because Y"
- No "low priority" labels. Either it's worth fixing or don't mention it.
- Race conditions, concurrency issues, edge cases = worth fixing, not optional
- Assume the author will implement your suggestions. Be worth implementing.
Project context (read what's helpful):
- CONTRIBUTING.md - development guidelines and conventions
- docs/adr/ - Architecture Decision Records for design context
- docs/prd/ - Product Requirements for feature context
- docs/skills/ - available automation skills
- Service-specific README.md files for local conventions
# Customize Claude's behavior
# Using Opus 4.5 for higher quality responses
claude_args: |
--max-input-tokens 50000
--model claude-opus-4-5-20251101