Do imporve the GEMINI.md

.pre-commit-config.yaml

@@ -2,6 +2,10 @@ repos:
 - repo: https://github.com/pre-commit/pre-commit-hooks
   rev: v6.0.0
   hooks:
+  - id: end-of-file-fixer
+    exclude: (.txt$|.ipynb$|README.md$|readme.mde$)
+  - id: trailing-whitespace
+    exclude: (.txt$|README.md$)
   # - id: check-yaml
   - id: check-json
   - id: check-toml
@@ -24,13 +28,13 @@ repos:
 
 - repo: https://github.com/astral-sh/ruff-pre-commit
     # Ruff version.
-  rev: v0.14.13
+  rev: v0.14.10
   hooks:
   - id: ruff
     args: [--fix, --exit-non-zero-on-fix]
 
 - repo: https://github.com/psf/black
-  rev: 26.1.0
+  rev: 25.12.0
   hooks:
   - id: black
     args: [--config=pyproject.toml]
@@ -39,7 +43,7 @@ repos:
 
 
 - repo: https://github.com/macisamuele/language-formatters-pre-commit-hooks
-  rev: v2.16.0
+  rev: v2.15.0
   hooks:
   - id: pretty-format-ini
     args: [--autofix]
@@ -70,14 +74,6 @@ repos:
   - id: prettier
     types_or: [css, javascript]
 
-- repo: https://github.com/executablebooks/mdformat
-  rev: 1.0.0  # Check for the latest version
-  hooks:
-  - id: mdformat
-    # Important: The GFM plugin is required for table support
-    additional_dependencies:
-    - mdformat-gfm
-
 - repo: https://github.com/python-jsonschema/check-jsonschema
   rev: 0.36.0
   hooks:
@@ -90,7 +86,6 @@ repos:
   - id: check-compose-spec
   - id: check-dependabot
 
-# the following hooks should always be at the end fo the file since they may add to what other hooks do
 - repo: https://github.com/pre-commit/pre-commit-hooks
   rev: v6.0.0
   hooks:
@@ -98,5 +93,3 @@ repos:
     exclude: (.txt$|.ipynb$|README.md$|readme.mde$)
   - id: trailing-whitespace
     exclude: (.txt$|README.md$)
-  - id: mixed-line-ending
-    args: [--fix=lf]

GEMINI.md

@@ -4,20 +4,11 @@ This document outlines some basic rules and guidelines for development within th
 
 ## Development Guidelines
 
-- **Test-Driven Development (TDD):** Wherever possible, Test-Driven Development principles should be followed. Write tests before writing the code they are intended to validate.
+*   **Test-Driven Development (TDD):** Wherever possible, Test-Driven Development principles should be followed. Write tests before writing the code they are intended to validate.
-- **Pre-commit Hooks:** Ensure that `pre-commit` hooks are installed and active before making any commits. This can be done by running `pre-commit install` in your local repository.
+*   **Pre-commit Hooks:** Use pre commit hooks
-
+    * Ensure that `pre-commit` hooks are installed and active before making any commits. This can be done by running `pre-commit install` in your local repository.
-## Issue Management
+    * Do NEVER skip the `pre-commits` via the git argument `-n`
-
-- **Closing Issues:** When a commit fixes or closes an issue, the commit message must include a supported keyword followed by the issue number (e.g., `fixes #123`, `closes #456`).
-  - Supported keywords: `close`, `closes`, `closed`, `fix`, `fixes`, `fixed`, `resolve`, `resolves`, `resolved`.
-  - **Placement:** This pattern should always be placed at the very end of the commit body (not the subject line).
-
-## PRs
-
-Do create PRs only on a specific user request. Do not create them on your own initiative.
-A PR should always contain a note if an issue is closed with it.
 
 ## Repository Comparison
 
-- On request, this repository should be compared against the rules and guidelines specified in the `README.md` of the reference repository: `https://git.horstenkamp.eu/Philipp/template-git`. The comparison should only move fitting changes to the current repo.
+*   On request, this repository should be compared against the rules and guidelines specified in the `README.md` of the reference repository: `https://git.horstenkamp.eu/Philipp/template-git`.

README.md

@@ -1,3 +1,3 @@
 # template-git
 
-A template for git repostories
+A template for git repostories