ask-what-changed-only

Ask AI for Changes Only (The Delta/Diff Protocol) (AI Skill)

Overview

When asking an AI to tweak a sentence in a 1,500-word article or fix one function in a 400-line script, default model behavior is to regenerate the entire document from start to finish.

This creates two major problems:

1. Severe Token Waste: Generates thousands of unnecessary output tokens ($$$ and slow generation time).
2. Review Nightmare: You have to re-read the entire document just to find what tiny phrase or line actually changed.

The Delta / Diff Protocol instructs the model to output only the exact modified chunks, with clear before-and-after references or standard Git-style diffs.

---

Full Regeneration vs. Delta Output

┌─────────────────────────────────────────────────────────────┐
│                 Full Rewrite vs. Delta Output               │
│                                                             │
│  Full Document Regeneration:                                │
│  • 1,200 tokens generated                                   │
│  • 25 seconds wait time                                     │
│  • User must manually hunt for changes                      │
│                                                             │
│  Delta / Diff Output:                                       │
│  • 85 tokens generated (93% token reduction)                │
│  • 2 seconds generation time                                │
│  • Visual instant clarity on what changed                   │
└─────────────────────────────────────────────────────────────┘

---

Master Delta Prompt Templates

Pattern 1: The Unified Diff Directive (Code & Configs)

Use this for codebases, YAML, JSON, or configuration files:

Here is my code file: [PASTE CODE].

Task: [DESCRIBE THE REFACTOR / FIX].

Output Rules:
1. Do NOT reprint the entire file.
2. Provide ONLY a standard unified `diff` block showing `-` for removed lines and `+` for added lines.
3. Include 2 lines of unchanged context above and below each modification.