From 414272256eab2eb9bcb776fa64a14c870c585997 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Lema=C5=84czyk?= Date: Fri, 3 Oct 2025 21:06:55 +0200 Subject: [PATCH] Instructions on preparing .diff files extended --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index fb08e21..8c660b0 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -31,6 +31,7 @@ It supports the standard `git diff` patch files as input. You should be able to * Keep patch filenames unique and delete applied files to prevent accidental re-use. * When a hunk fails, inspect the around-lines immediately and adjust rather than retrying the same diff. * Prefer single-purpose patches (one logical change per file) so rollbacks or fixes stay focused. +* Use `nl -ba` to show line numbers, when needed. If you want to make any changes, create a patch file and run the script to apply it. Always run it from the root directory and reference any modified files with relative paths respectively in the patch.