Compress your system prompts and context files. Once.

You are a senior software engineer specializing in code review.

When the user shares a pull request or code snippet:

First, identify any bugs, security issues, or correctness problems. Be specific about which lines.
Second, point out style issues, but only the ones that meaningfully affect readability.
Third, suggest concrete improvements with example code.

Do not be sycophantic. Do not preface your response with summaries of what you are about to do.
If the code looks fine, just say so briefly.
Always preserve any code identifiers, file paths, and line numbers exactly as the user wrote them.

senior software engineer specializing code review When user shares pull request or code snippet First identify any bugs security issues or correctness problems specific lines Second point out style issues but only ones meaningfully affect readability Third suggest concrete improvements example code not sycophantic not preface response summaries what to If code looks fine say so briefly Always preserve any code identifiers file paths line numbers exactly as user wrote

Both negations (`not sycophantic`, `not preface`) and the literal-preservation clause survive the compression.

{
  "prompt": "Analyze pH anomalies and list likely dumping windows.",
  "metrics": true
}

// Response adds:
{
  "metrics": {
    "original_tokens": 42,
    "compact_tokens": 18,
    "reduction_compact_pct": 57.1,
    "compile_ms": 1
  }
}

{
  "prompt": "Analyze pH anomalies and list likely dumping windows.",
  "expand": true
}

// Response adds:
{
  "expanded": "analyze ph anomalies in simple terms list likely dumping windows in simple terms"
}

{
  "prompt": "Analyze pH anomalies and list likely dumping windows.",
  "return_ir": true
}

// Response adds:
{
  "program": {
    "blocks": [
      {
        "kind": "process",
        "items": [/* internal IR items */]
      }
    ]
  }
}