[config] git_provider = "github" fallback_models = ["gpt-5.4-mini"] publish_output = true publish_output_progress = false response_language = "en-US" max_model_tokens = 131072 custom_model_max_tokens = 131072 large_patch_policy = "clip" temperature = 0.1 [pr_reviewer] require_score_review = true require_tests_review = true require_estimate_effort_to_review = true require_can_be_split_review = true require_security_review = true require_todo_scan = true require_ticket_analysis_review = true publish_output_no_suggestions = true persistent_comment = true num_max_findings = 10 final_update_message = true enable_review_labels_security = false enable_review_labels_effort = false enable_intro_text = true enable_help_text = true extra_instructions = """\ Focus on correctness, security, regressions, and missing verification. Read the full diff before reporting findings, and inspect surrounding code before claiming a bug. Be thorough across the enabled review sections, even when no major defects are found. When a change looks safe, explain why it appears safe and call out any residual assumptions or manual verification gaps. Prefer substantive analysis over generic praise or filler, and keep every claim evidence-based. CCS-specific checks: - CLI output in src/ must stay ASCII-only: [OK], [!], [X], [i] - CCS path access must use getCcsDir(), not os.homedir() plus .ccs - CLI behavior changes require matching --help and docs updates - Terminal color output must respect TTY detection and NO_COLOR - Code must not modify ~/.claude/settings.json without explicit user action Treat the following as high severity: - security issues, data loss, broken install or release flows, or behavior likely wrong in normal use Treat the following as medium severity: - meaningful edge cases, missing guards, or missing tests/docs/help updates that can cause user-facing bugs Use low severity only for small, concrete follow-ups that are worth tracking. """ [github_action_config] pr_actions = ["opened", "reopened", "ready_for_review", "synchronize"]