diff --git a/.checkov.yaml b/.checkov.yaml
new file mode 100644
index 0000000..0cab7b1
--- /dev/null
+++ b/.checkov.yaml
@@ -0,0 +1,4 @@
+quiet: true
+skip-check:
+  - CKV_DOCKER_2
+  - CKV_DOCKER_3
diff --git a/.github/prompts/create-release-notes.prompt.md b/.github/prompts/create-release-notes.prompt.md
index 50c4b84..2be7035 100644
--- a/.github/prompts/create-release-notes.prompt.md
+++ b/.github/prompts/create-release-notes.prompt.md
@@ -10,7 +10,7 @@ Ensure you adhere to the following guidelines when creating release notes:
 
 - Use a clear and consistent format for the release notes
 - Include a summary of the changes made in the release
-- Highlight any new features, improvements, or bug fixes
+- Highlight any new features, improvements, or bugfixes
 - If applicable, include instructions for upgrading or migrating to the new
   version
 - Use technical language that is appropriate for the audience, but avoid jargon
@@ -31,4 +31,4 @@ of the changes, please make sure to adjust the release notes accordingly:
 - For **major** changes, include a detailed description of the breaking changes
   and how users can adapt to them
 - For **minor** changes, highlight new features and improvements
-- For **patch** changes, focus on bug fixes and minor improvements
+- For **patch** changes, focus on bugfixes and minor improvements
diff --git a/.vscode/mcp.json b/.vscode/mcp.json
index 2d34de4..7d7a7c0 100644
--- a/.vscode/mcp.json
+++ b/.vscode/mcp.json
@@ -1,9 +1,9 @@
 {
-	"servers": {
-		"github": {
-			"url": "https://api.githubcopilot.com/mcp/",
-			"type": "http"
-		}
-	},
-	"inputs": []
-}
\ No newline at end of file
+  "servers": {
+    "github": {
+      "url": "https://api.githubcopilot.com/mcp/",
+      "type": "http"
+    }
+  },
+  "inputs": []
+}