mirror of
https://github.com/tiennm99/ccs.git
synced 2026-10-11 03:13:12 +00:00
* fix(cliproxy): migrate deprecated gemini-claude-* model names to upstream claude-* names (#515) * fix(cliproxy): migrate deprecated gemini-claude-* model names to upstream claude-* names CLIProxyAPI registry no longer recognizes the gemini-claude-* prefix convention. Model names in catalog, base config, and user settings are migrated to upstream claude-* names. Auto-migration in env-builder rewrites existing user settings on load and persists the change. Closes #513 * fix: address code review feedback — sync UI layer and add migration tests - Sync UI isNativeGeminiModel() with backend (remove gemini-claude- exclusion) - Update UI model catalog agy entries from gemini-claude-* to claude-* - Update CI/CD workflow and code-reviewer default model names - Add unit tests for migrateDeprecatedModelNames() logic * fix(hooks): isolate image type check before error-prone processing (#514) * fix(hooks): isolate image type check before error-prone processing Restructure processHook() into two phases so non-image Read calls never see hook error messages. Phase 1 defensively checks tool name and file extension, exiting 0 silently on any failure. Phase 2 only runs for confirmed image/PDF files where errors are relevant. Closes #511 * fix(hooks): sync image analyzer hook file on every profile launch Add installImageAnalyzerHook() call to cliproxy executor, matching the existing installWebSearchHook() pattern. This ensures the .cjs file in ~/.ccs/hooks/ gets refreshed from the npm package on every launch, so users receive hook updates after npm update. * chore(release): 7.41.0-dev.1 [skip ci] * fix(cliproxy): add fork:true for Claude model aliases in config generator (#523) Config generator now outputs fork:true for Claude model alias entries, ensuring both upstream (claude-*) and aliased (gemini-claude-*) model names appear in /v1/models listings. Also preserves fork flag when parsing user-added aliases during config regeneration. Bumps config version to v7 to trigger regeneration on next ccs doctor. Closes #522 * chore(release): 7.41.0-dev.2 [skip ci] * feat(cliproxy): add account safety guards to prevent Google account bans (#516) * feat(cliproxy): add account safety guards to prevent Google account bans Implements cross-provider isolation to prevent Google from flagging concurrent OAuth usage across different client IDs (ref: #509, #512). Three pillars: 1. Auto-pause enforcement at session launch — conflicting accounts in other Google OAuth providers are paused so CLIProxyAPI can't use them, restored on session exit with crash recovery via auto-paused.json 2. Ban/disable detection — error responses matching Google ban patterns auto-pause the affected account to prevent further damage 3. Cross-provider conflict warnings during OAuth registration Key design decisions: - PID-based session tracking for crash recovery (dead PID = restore) - Timestamp comparison prevents restoring ban-paused accounts on exit - Schema validation on auto-paused.json prevents corrupted state - Falls back to warn-only when another session is managing isolation * fix(cliproxy): address code review feedback (attempt 1/5) - Re-read auto-paused.json before write in enforceProviderIsolation to reduce concurrent write race window - Use actual email from registry for display instead of raw accountId - Export maskEmail for testability - Add 27 unit tests covering ban detection, email masking, cross-provider duplicate detection, enforcement lifecycle, crash recovery, and timestamp-guarded restore * fix(cliproxy): address remaining review feedback (attempt 2/5) - Add handleBanDetection test verifying account pause on ban error - Add warnCrossProviderDuplicates tests (true/false/non-Google) - Document PID reuse limitation in isPidAlive JSDoc comment * chore(release): 7.41.0-dev.3 [skip ci] * feat(cliproxy): runtime quota monitoring during active sessions (#529) * feat(cliproxy): add runtime quota monitoring during active sessions Adds adaptive background quota polling to detect and respond to quota exhaustion during active CLIProxy sessions. Prevents rate-limit-driven account bans by auto-cooling exhausted accounts and switching defaults. - Adaptive polling: 300s normal, 60s at 20% threshold, stops at 0% - Stderr warnings at 20%, boxed exhaustion alerts at 0% - Cooldown + default switch on exhaustion (existing patterns) - Configurable via quota_management.runtime_monitor in config.yaml - Timer.unref() prevents blocking process exit - monitorStopped guard for in-flight poll safety Closes #524 * fix: address code review feedback (attempt 1/5) - M1: Round quotaPercent display with Math.round() to avoid ugly floats - M2: Rename exhaust_threshold -> exhaustion_threshold for consistency with existing auto.exhaustion_threshold config field - M3: Replace async not.toThrow() with direct await assertion pattern * fix: address code review feedback (attempt 2/5) - Remove .claude/agent-memory/ from tracking and add to .gitignore - Unify cooldown_minutes default to 5 (was 10 in runtime_monitor, 5 in auto) - Add threshold validation in startQuotaMonitor (warn > exhaustion) - Document intentional post-switch monitoring gap in code comment * chore(release): 7.41.0-dev.4 [skip ci] * fix(cliproxy): mask email in ban detection and fix JSDoc default - Use maskEmail() in handleBanDetection output for consistency - Fix cooldown_minutes JSDoc: default is 5, not 10 * chore(release): 7.41.0-dev.5 [skip ci] * fix(cliproxy): address all review feedback (Low + informational) - Add sync constraint comment on process.exit handler (executor) - Add TOCTOU race acceptability comment (account-safety) - Mask email in handleQuotaExhaustion reason string - Use realistic exhaustion_threshold (5) in test configs * chore(release): 7.41.0-dev.6 [skip ci] --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
193 lines
8.0 KiB
YAML
193 lines
8.0 KiB
YAML
# AI Code Review Workflow
|
|
# Uses anthropics/claude-code-action with CLIProxy (localhost:8317)
|
|
# Posts as ccs-agy-reviewer[bot] via GitHub App
|
|
#
|
|
# Triggers:
|
|
# - Automatically when PR is opened, receives new commits, or is reopened
|
|
# - Manually via /review comment on PR
|
|
# - Manually via workflow_dispatch
|
|
#
|
|
# Note: Concurrency group cancels in-progress reviews when new commits arrive.
|
|
# This prevents wasting resources on outdated code reviews.
|
|
|
|
name: AI Code Review
|
|
|
|
on:
|
|
pull_request_target:
|
|
types: [opened, synchronize, reopened]
|
|
issue_comment:
|
|
types: [created]
|
|
workflow_dispatch:
|
|
inputs:
|
|
pr_number:
|
|
description: 'PR number to review'
|
|
required: true
|
|
type: string
|
|
|
|
# Smart concurrency: Prevents self-cancellation when bot posts review comment
|
|
#
|
|
# Problem: When the bot posts a review comment, GitHub fires an issue_comment event.
|
|
# This new workflow run joins the same concurrency group and cancels the in-progress
|
|
# run BEFORE job `if` conditions are evaluated - causing "operation was canceled" error.
|
|
#
|
|
# Solution: Non-actionable triggers (bot comments, comments without /review) get a
|
|
# unique per-run group, while legitimate triggers share the PR-based group for proper
|
|
# cancellation of outdated reviews.
|
|
concurrency:
|
|
group: >-
|
|
ai-review-${{
|
|
github.event_name == 'issue_comment' && (
|
|
github.event.comment.user.type == 'Bot' ||
|
|
!contains(github.event.comment.body, '/review')
|
|
) && format('skip-{0}', github.run_id) ||
|
|
github.event.pull_request.number ||
|
|
github.event.issue.number ||
|
|
github.event.inputs.pr_number
|
|
}}
|
|
cancel-in-progress: true
|
|
|
|
jobs:
|
|
review:
|
|
name: Claude Code Review
|
|
runs-on: [self-hosted, cliproxy]
|
|
permissions:
|
|
contents: read
|
|
pull-requests: write
|
|
issues: write
|
|
id-token: write
|
|
|
|
# Conditions:
|
|
# - PR event: on opened, synchronize (new commits), or reopened
|
|
# - Comment event: only if it's a PR, contains /review, and NOT from a bot
|
|
if: >
|
|
github.event_name == 'pull_request_target' ||
|
|
github.event_name == 'workflow_dispatch' ||
|
|
(github.event_name == 'issue_comment' &&
|
|
github.event.issue.pull_request &&
|
|
contains(github.event.comment.body, '/review') &&
|
|
github.event.comment.user.type != 'Bot')
|
|
|
|
# CLIProxy environment for model routing
|
|
env:
|
|
ANTHROPIC_BASE_URL: http://localhost:8317
|
|
REVIEW_MODEL: claude-opus-4-6-thinking
|
|
ANTHROPIC_AUTH_TOKEN: ccs-internal-managed
|
|
ANTHROPIC_MODEL: claude-opus-4-6-thinking
|
|
ANTHROPIC_DEFAULT_OPUS_MODEL: claude-opus-4-6-thinking
|
|
ANTHROPIC_DEFAULT_SONNET_MODEL: claude-sonnet-4-5-thinking
|
|
ANTHROPIC_DEFAULT_HAIKU_MODEL: claude-sonnet-4-5
|
|
DISABLE_BUG_COMMAND: "1"
|
|
DISABLE_ERROR_REPORTING: "1"
|
|
DISABLE_TELEMETRY: "1"
|
|
CLAUDE_CODE_MAX_OUTPUT_TOKENS: "64000"
|
|
MAX_THINKING_TOKENS: "32000"
|
|
|
|
steps:
|
|
- name: Clear Claude install locks
|
|
run: rm -rf ~/.local/state/claude/locks/* 2>/dev/null || true
|
|
|
|
- name: Generate App Token
|
|
id: app-token
|
|
uses: actions/create-github-app-token@v1
|
|
with:
|
|
app-id: ${{ secrets.CCS_REVIEWER_APP_ID }}
|
|
private-key: ${{ secrets.CCS_REVIEWER_PRIVATE_KEY }}
|
|
|
|
- name: Checkout repository
|
|
uses: actions/checkout@v4
|
|
with:
|
|
fetch-depth: 0
|
|
|
|
- name: Checkout PR code
|
|
env:
|
|
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
run: |
|
|
PR_NUM="${{ github.event.pull_request.number || github.event.issue.number || github.event.inputs.pr_number }}"
|
|
if [ -n "$PR_NUM" ]; then
|
|
gh pr checkout $PR_NUM || git checkout ${{ github.event.pull_request.head.sha }} 2>/dev/null || true
|
|
fi
|
|
|
|
- name: Add reaction to comment
|
|
if: github.event_name == 'issue_comment'
|
|
run: |
|
|
gh api repos/${{ github.repository }}/issues/comments/${{ github.event.comment.id }}/reactions \
|
|
--method POST -f content=eyes
|
|
env:
|
|
GH_TOKEN: ${{ steps.app-token.outputs.token }}
|
|
|
|
- name: Run Claude Code Review
|
|
id: claude-review
|
|
uses: anthropics/claude-code-action@v1
|
|
with:
|
|
anthropic_api_key: ${{ secrets.CLIPROXY_API_KEY }}
|
|
github_token: ${{ steps.app-token.outputs.token }}
|
|
path_to_claude_code_executable: /home/github-runner/.local/bin/claude
|
|
track_progress: false # Disabled - no progress comments, just final review
|
|
prompt: |
|
|
ultrathink
|
|
|
|
REPO: ${{ github.repository }}
|
|
PR NUMBER: ${{ github.event.pull_request.number || github.event.issue.number || github.event.inputs.pr_number }}
|
|
|
|
Perform a comprehensive code review. Follow the repository's CLAUDE.md for project-specific guidelines.
|
|
|
|
## Review Focus Areas
|
|
|
|
1. 🔒 **Security** - OWASP Top 10, injection, auth bypass, secrets exposure
|
|
2. ✅ **Correctness** - Logic errors, edge cases, error handling
|
|
3. 🏗️ **Architecture** - Coupling, cohesion, API contracts, backward compatibility
|
|
4. 🧪 **Testing** - Coverage, edge cases, test quality
|
|
5. ⚡ **Performance** - Algorithm complexity, memory leaks, query efficiency
|
|
6. 📖 **Maintainability** - Naming, complexity, consistency with codebase
|
|
|
|
## Output Structure
|
|
|
|
Use visual hierarchy with emojis and `---` separators between major sections:
|
|
- 📋 **Summary** (2-3 sentences)
|
|
- ✅ **Strengths** (numbered, with file:line references, use ⭐ for exceptional items)
|
|
- 🔍 **Observations & Suggestions** (with code examples, priority tags)
|
|
- 🔒 **Security Considerations** (✅/❌ checklist table)
|
|
- 📊 **Code Quality Checklist** (✅/❌ table format)
|
|
- 💡 **Recommendations** (🔴 High / 🟡 Medium / 🟢 Low priority)
|
|
- 🎯 **Overall Assessment** (✅ APPROVED / ⚠️ APPROVED WITH NOTES / ❌ CHANGES REQUESTED)
|
|
|
|
Be thorough but concise. Skip empty sections. Include code examples for non-trivial suggestions.
|
|
Use tables for checklists. Bold important terms. Make the review visually scannable.
|
|
|
|
End your review with:
|
|
> 🤖 Reviewed by `${{ env.REVIEW_MODEL }}`
|
|
|
|
## IMPORTANT: Posting the Review
|
|
After completing your analysis, post the review as a PR comment.
|
|
|
|
STEP 1: First, use the Read tool to check if pr_review.md exists (it may not exist yet, that's OK)
|
|
STEP 2: Use the Write tool to write your review to pr_review.md in the current working directory
|
|
STEP 3: Post with: gh pr comment ${{ github.event.pull_request.number || github.event.issue.number || github.event.inputs.pr_number }} --body-file pr_review.md
|
|
|
|
IMPORTANT RULES:
|
|
- Write to pr_review.md (in working directory), NOT /tmp/pr_review.md
|
|
- Do NOT use shell operators like || or && in bash commands
|
|
- Do NOT use heredoc (<<) syntax in bash commands
|
|
- Use simple, single-purpose bash commands only
|
|
|
|
claude_args: |
|
|
--model ${{ env.REVIEW_MODEL }}
|
|
--allowedTools "Edit,Glob,Grep,LS,Read,Write,Bash(gh pr comment *),Bash(gh pr diff *),Bash(gh pr view *),Bash(gh issue view *),Bash(gh api *),Bash(git diff *),Bash(git log *),Bash(git status *),Bash(cat *),Bash(ls *),Bash(rm pr_review.md)"
|
|
continue-on-error: true
|
|
|
|
- name: Add success reaction
|
|
if: success() && github.event_name == 'issue_comment'
|
|
run: |
|
|
gh api repos/${{ github.repository }}/issues/comments/${{ github.event.comment.id }}/reactions \
|
|
--method POST -f content=rocket
|
|
env:
|
|
GH_TOKEN: ${{ steps.app-token.outputs.token }}
|
|
|
|
- name: Add failure reaction
|
|
if: failure() && github.event_name == 'issue_comment'
|
|
run: |
|
|
gh api repos/${{ github.repository }}/issues/comments/${{ github.event.comment.id }}/reactions \
|
|
--method POST -f content=confused
|
|
env:
|
|
GH_TOKEN: ${{ steps.app-token.outputs.token }}
|