diffs

To generate a shareable diff, provide the before and after text content to the tool. It creates real diff artifacts that can be viewed interactively or downloaded as files for code reviews and documentation edits.

Yes, you can create a code review diff by inputting a unified patch instead of before/after text. The tool processes the patch to produce auditable diff artifacts suitable for review workflows.

Available output formats for sharing diffs include interactive viewer URLs and downloadable file artifacts. You can select mode=view, mode=file, or mode=both to fit your specific messaging channel.

The diff viewer provides specific guidance on usage and fallback behaviors for complex patches and proxy configurations. This ensures you can handle edge cases when generating your diff artifacts.

The best way to automate documentation edit summaries is to use a diff generator that replaces manual summaries with real, shareable artifacts. It processes before/after content to create auditable records automatically.

You should use file artifacts instead of viewer URLs when your workflow requires downloadable records or your messaging channel does not support interactive links. Use mode=file to generate these outputs directly.