From 01b995b793c4039edcd2f98938f856a4c3dc230c Mon Sep 17 00:00:00 2001 From: Luna Date: Thu, 2 Apr 2026 18:52:31 +0200 Subject: [PATCH] Fix file content for project docs --- code-review.md | 4 ++-- micro-stack.md | 4 ++-- rag-hub.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/code-review.md b/code-review.md index 9dd5053..ba5b1c9 100644 --- a/code-review.md +++ b/code-review.md @@ -1,11 +1,11 @@ # Automated Code-Review-Pipeline (The Gatekeeper) ## Problem -Manual code review is tedious and spesso inconsistent. Architectural anti-patterns often slip through PRs. +Manual code review is tedious and often inconsistent. Architectural anti-patterns often slip through PRs. ## Instructions 1. **Webhook Integration:** Set up a Gitea webhook that triggers a function on your VPS when a PR is opened. -2. **Analysis Engine:** Use an LLM (e.g., via Gemini API) to analyze the . +2. **Analysis Engine:** Use an LLM (e.g., via LLM API) to analyze the `git diff`. 3. **Prompt Engineering:** Define a system prompt for the agent to focus on *architectural integrity* and *complexity metrics* rather than just syntax checking. 4. **Feedback Loop:** Have the agent post its review directly back to the PR comments. diff --git a/micro-stack.md b/micro-stack.md index d3b5190..e8b64e1 100644 --- a/micro-stack.md +++ b/micro-stack.md @@ -1,10 +1,10 @@ # Serverless Micro-Stack Manager ## Problem -Managing multiple Docker Compose projects via SSH/CLI is exhausting and error-prone. +Managing multiple `docker-compose` projects via SSH/CLI is exhausting and error-prone. ## Instructions -1. **Abstraction Layer:** Build a thin Go or Python API that wraps commands. +1. **Abstraction Layer:** Build a thin Go or Python API that wraps `docker-compose` commands. 2. **ChatOps Interface:** Connect this API to your chat agent (via Discord/Telegram) so you can issue commands like "Deploy auth-service" or "Restart proxy". 3. **Version Control:** Add logic to pull the latest image/code, backup data volumes, and restart the service atomically. 4. **Health Check:** Ensure the agent verifies the service is actually "up" (HTTP 200) after the restart before confirming. diff --git a/rag-hub.md b/rag-hub.md index 6c5a71e..ef1fd2f 100644 --- a/rag-hub.md +++ b/rag-hub.md @@ -4,10 +4,10 @@ Technical knowledge about personal infrastructure is scattered across config files, chat history, and stale documentation. ## Instructions -1. **Data Collection:** Crawl your , , and project directories for configuration files (, , ). +1. **Data Collection:** Crawl your `/etc/`, `/opt/`, and project directories for configuration files (`.yaml`, `.conf`, `.md`). 2. **Embedding:** Use an embedding pipeline to vectorize this knowledge. 3. **Retrieval:** Set up a web interface or terminal bot that allows querying your "Second Brain". -4. **Sync Mechanism:** Create a task that updates the vector database whenever a config file is modified (using or ). +4. **Sync Mechanism:** Create a task that updates the vector database whenever a config file is modified (using `inotify` or `git hooks`). ## Goal Create an infrastructure-aware assistant that knows your setup intimately.