Developer tools
1 toolsOne tool, for the moment many files need to become one. The File Merger combines text, code, JSON, YAML, XML and Markdown in the browser, with reordering, minification, comment stripping and duplicate-line removal on the way through.
Why merging matters again
The reason this exists in its current shape is context windows. Handing a codebase to a model means concatenating twenty files in a sensible order, dropping comments and blank lines that spend tokens without carrying meaning, and knowing the token count before you hit the limit rather than after. The merger reports that count as it packs, so the trimming decisions happen before the paste, not after a rejection.
It is just as useful for the older version of the same problem: one log out of a rotated set, one script out of a migration folder, one stylesheet out of a partials directory. Files are read in the browser and nothing is uploaded, which is what makes it safe to point at source you are not allowed to send to a service.
How to choose a Developer tool
Set the options by what the merged file is for.
Strip comments, remove duplicate lines and watch the token count. Order the files so entry points come first.
Keep comments and formatting. The merged file has to stay readable by a person later.
Merge both sides in the same order, then diff the two results.