DevDiff

Appearance

The 3-Tap Rule — Why DevDiff Is Designed for Instant Productivity ​

July 6, 2026 · Eldrex Delos Reyes Bula

As developers, we install dozens of tools. Almost all of them follow a similar pattern:

  1. Install package.
  2. Sign up for a cloud account.
  3. Configure API keys, environment variables, and config files.
  4. Debug why the CLI can't connect to the database or find its settings.
  5. Spend an hour reading docs to make the first test request.

We believe that great developer tools should disappear. They should get out of your way, require zero boilerplate configuration, and work instantly.

This is why we built DevDiff around the 3-Tap Rule: a user must be able to go from install to a fully functioning AI-generated changelog in exactly three terminal commands.

🛠️ The 3-Tap Sequence ​

Here is the exact installation flow:

Tap 1: Download the Package ​

bash
npm install -g @eldrex/cli

Tap 2: Initialize DevDiff ​

bash
devdiff init

Tap 3: Generate Changelog ​

bash
devdiff generate

That’s it. You don’t need to write custom rules, copy-paste config keys, or input authorization codes.

💡 How It Works (Behind the Scenes) ​

To make a 3-tap rule possible, the DevDiff CLI does a massive amount of automated work under the hood during those three commands:

  1. Auto-Discovery: DevDiff checks your system for a running instance of Ollama. If found, it automatically queries the local Ollama API to detect which models are already pulled (e.g. llama3.2:3b, qwen2.5-coder:7b). It selects the best available local model automatically.
  2. Context Resolution: The engine inspects your git workspace to detect package managers (npm, pnpm, yarn, bun), languages, monorepo structures, and configuration files, populating default structures.
  3. Smart Defaults: Configuration schemas in .devdiff.config.js have optimized, safe values. Security, privacy filters, and output formats are pre-configured to prioritize privacy and accuracy out of the box.
  4. Resilient Fallbacks: If Ollama or cloud models are completely unavailable, the CLI doesn't crash. It automatically falls back to a JS-only template generator to write your changelog.

🎨 Power Users: Configuration When You Need It ​

Zero-configuration doesn't mean zero-customization. Once DevDiff is running, you can easily customize its behavior using simple CLI flags or configuration parameters:

  • Switch Personas: Want a CEO summary instead of a technical log? Run devdiff generate --persona ceo.
  • Change Format: Output as JSON or PDF: devdiff generate --format json.
  • Workspace Diagnostics: Run devdiff doctor to scan for packaging errors, missing module types, or configuration conflicts, and automatically resolve them with devdiff doctor --fix.

🚀 Experience the 3-Tap Rule ​

Stop spending time configuring release management tools. Open your terminal, type the three commands, and let DevDiff automate the rest.