Claude system prompts turned into a browsable git timeline
Anthropic's published Claude system prompts have been transformed into a git repository with per-model files and fake timestamped commits, enabling `git log`, `diff`, and `blame`-based exploration of prompt changes over time.
Score breakdown
Researchers and practitioners tracking Claude's behavior over time can use this git-based structure to precisely diff system prompt changes between model versions without manual parsing.
- 01Anthropic publicly publishes system prompts for Claude chat as a Markdown page.
- 02Claude Code was used to transform the monolithic Markdown source into separate files per model, model family, and revision.
- 03Fake git commit dates were assigned to each entry to enable chronological browsing.
The post outlines a workflow for making Anthropic's published Claude system prompt history more analytically useful. Anthropic makes the system prompts for Claude chat publicly available as a Markdown page, but the monolithic format makes it difficult to track changes across model versions. To address this, Claude Code was used to parse the page and break it into granular files organized by model, model family, and revision, with fake git commit dates applied to each entry.
The project was then applied practically: the author used it to produce detailed notes on the specific changes between Claude Opus 4.6 and 4.7.
By structuring the data this way, the resulting repository can be explored using standard git tooling — `git log` to browse the commit history, `diff` to compare prompt versions side by side, and `blame` to attribute specific lines to particular dates — all through the familiar GitHub commit view interface. The project was then applied practically: the author used it to produce detailed notes on the specific changes between Claude Opus 4.6 and 4.7.
Key facts
- 01Anthropic publicly publishes system prompts for Claude chat as a Markdown page.
- 02Claude Code was used to transform the monolithic Markdown source into separate files per model, model family, and revision.
- 03Fake git commit dates were assigned to each entry to enable chronological browsing.
- 04The repository supports `git log`, `diff`, and `blame` for tracing prompt evolution.
- 05Changes are browsable via the GitHub commit view interface.
- 06The tool was used to write detailed notes on differences between Claude Opus 4.6 and 4.7.
Topics
Summary and scoring are generated automatically from the original article. We always link back to the publisher and never republish images or paywalled content.