Verified:GitHub

cp-sat-debugging-and-performance

Diagnose infeasibility, wrong solutions, and slow search in Google OR-Tools CP-SAT scheduling models.

Updated May 6, 2026

Search Tags:#performance #debugging #optimization #scheduling #cp-sat #ortools #solver logs

One-click install

npx skills add https://github.com/Takfes/indie-scaffolder --skill cp-sat-debugging-and-performance

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: cp-sat-debugging-and-performance
Source: https://github.com/Takfes/indie-scaffolder/tree/main/components/agent-skills-commands/.agents/skills/cp-sat-debugging-and-performance
Command: npx skills add https://github.com/Takfes/indie-scaffolder --skill cp-sat-debugging-and-performance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you debug and optimize Google OR-Tools CP-SAT scheduling models when they are infeasible, slow, stuck, or returning solutions that do not match business intent.

Core Features & Use Cases

Infeasibility diagnosis: Isolate conflicting constraints with model validation, assumption-based conflict checks, and manual relaxation when needed.
Wrong-solution debugging: Hard-code the expected solution to determine whether the model is missing a constraint or contains one that blocks the intended answer.
Performance triage: Improve solve times using the recommended order of domain tightening, reformulation, symmetry breaking, redundant constraints, hints, and parameter tuning.
Log interpretation: Read CP-SAT search progress to tell whether the issue is search, proof, thrashing, or presolve behavior.
Regression analysis: Compare exported models to identify what changed when a model worked before and now fails or slows down.
Use Case: A scheduling model suddenly becomes infeasible after a refactor, and this Skill guides you through isolating the conflicting constraints, checking logs, and validating the fix.

Quick Start

Ask me to diagnose or improve your CP-SAT scheduling model, and I will walk you through validation, conflict isolation, log reading, and performance triage.

Frequently Asked Questions about cp-sat-debugging-and-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose infeasibility in my CP-SAT scheduling model?▼

Debug wrong CP-SAT solutions by hard-coding the expected solution to see if the model is missing a constraint or contains one blocking the intended answer. This validates whether the model formulation matches business intent.

Why is my OR-Tools CP-SAT model so slow and how can I optimize it?▼

Speed up slow CP-SAT models through performance triage using domain tightening, reformulation, symmetry breaking, redundant constraints, hints, and parameter tuning. Measurement-driven optimization improves solve times systematically.

How do I read CP-SAT solver logs to troubleshoot search progress?▼

Read CP-SAT solver logs to identify whether slow search, proof, thrashing, or presolve behavior causes performance issues. Log interpretation reveals the exact bottleneck in the solver's search progress.

What is the best way to find what changed when a previously working CP-SAT model breaks?▼

Find CP-SAT regressions by comparing exported models to identify what changed when a model worked before and now fails or slows down. Regression diffing isolates the specific modifications causing the failure.