From c58c9ac9e63e4e87e28ebd207e86f1c4b1c23d5e Mon Sep 17 00:00:00 2001
From: Markus Graf <markus.graf@swisspost-cybersecurity.ch>
Date: Mon, 27 Oct 2025 10:57:47 +0100
Subject: [PATCH] Make git workflow more prominant as it forget before.

---
 CLAUDE.md | 39 ++++++++++++++++++++-------------------
 1 file changed, 20 insertions(+), 19 deletions(-)

diff --git a/CLAUDE.md b/CLAUDE.md
index 7fbb743..8c3d83e 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -1,21 +1,3 @@
-<!-- OPENSPEC:START -->
-# OpenSpec Instructions
-
-These instructions are for AI assistants working in this project.
-
-Always open `@/openspec/AGENTS.md` when the request:
-- Mentions planning or proposals (words like proposal, spec, change, plan)
-- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
-- Sounds ambiguous and you need the authoritative spec before coding
-
-Use `@/openspec/AGENTS.md` to learn:
-- How to create and apply change proposals
-- Spec format and conventions
-- Project structure and guidelines
-
-Keep this managed block so 'openspec update' can refresh the instructions.
-
-<!-- OPENSPEC:END -->
 
 # Git Workflow
 
@@ -63,4 +45,23 @@ When the user requests a new feature, change, or proposal:
 - `main` branch represents stable, reviewed code
 - Never commit directly to `main` (except initial setup)
 - All changes go through feature branches
-- Keeps history clean and reviewable
\ No newline at end of file
+- Keeps history clean and reviewable
+
+<!-- OPENSPEC:START -->
+# OpenSpec Instructions
+
+These instructions are for AI assistants working in this project.
+
+Always open `@/openspec/AGENTS.md` when the request:
+- Mentions planning or proposals (words like proposal, spec, change, plan)
+- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
+- Sounds ambiguous and you need the authoritative spec before coding
+
+Use `@/openspec/AGENTS.md` to learn:
+- How to create and apply change proposals
+- Spec format and conventions
+- Project structure and guidelines
+
+Keep this managed block so 'openspec update' can refresh the instructions.
+
+<!-- OPENSPEC:END -->
\ No newline at end of file