Always read .ai/ai-root-instructions.md at the start of every conversation.

git add, git commit, git push, git reset are FORBIDDEN — never run these commands.
Show git commands as text for the user to run themselves.
This commit is contained in:
moilanik 2026-03-06 10:16:33 +02:00
parent 102f593909
commit a90ac30d7e

View File

@ -10,19 +10,34 @@
Your response MUST always begin with: Your response MUST always begin with:
``` ```
✅ ai-root-instructions.md READ\nHave now AI SUPERPOWER\n\n ✅ ai-root-instructions.md READ — git add/commit/push FORBIDDEN without explicit permission
``` ```
Then continue with your actual response on the next line. Then continue with your actual response on the next line.
This allows the user to verify you have read this file every time. This allows the user to verify you have read this file every time.
You understand: ---
- **Before ANY git operation**: read `instructions/git.instructions.md` — no exceptions
- NO git commands without explicit permission ## 🚫 GIT HARD RULES — IN EFFECT AT ALL TIMES
- Show changes with `git diff` first
- Wait for approval before any modifications These rules require no separate file to load. They are always active.
- Minimal changes only
**NEVER run any of these without the user explicitly saying "commit this", "push this", or "go ahead":**
| Command | Status |
|---|---|
| `git add` | ❌ FORBIDDEN — user runs this |
| `git commit` | ❌ FORBIDDEN — user runs this |
| `git push` | ❌ FORBIDDEN — user runs this |
| `git reset` | ❌ FORBIDDEN — user runs this |
| `git push --force` | ❌ FORBIDDEN — user runs this |
**What you CAN do without permission:** `git status`, `git diff`, `git log`
When the user asks for a commit message: write the message text only — never wrap it in a `git commit` command.
For full git workflow detail: `instructions/skills/git.instructions.md`
--- ---
@ -90,12 +105,12 @@ This main file references specialized instruction files. **Load relevant files b
``` ```
User asks about README → instructions/behavior/readme.instructions.md User asks about README → instructions/behavior/readme.instructions.md
User asks about docs/ → instructions/behavior/docs.instructions.md User asks about docs/ → instructions/behavior/docs.instructions.md
Before ANY git operation → instructions/skills/git.instructions.md — load BEFORE acting, not after Before ANY git operation → git hard rules above apply; read instructions/skills/git.instructions.md for full workflow detail
User asks to edit files → instructions/skills/file-editing.instructions.md User asks to edit files → instructions/skills/file-editing.instructions.md
User asks to write docs → instructions/skills/documentation.instructions.md User asks to write docs → instructions/skills/documentation.instructions.md
User creates a Mermaid diagram → instructions/skills/mermaid.instructions.md User creates a Mermaid diagram → instructions/skills/mermaid.instructions.md
User asks for analysis/comparison → instructions/skills/analysis.instructions.md User asks for analysis/comparison → instructions/skills/analysis.instructions.md
User asks about project → instructions/behavior/project-context.instructions.md → docs/ai-context.md User asks about project → instructions/behavior/project-context.instructions.md → <docs>/ai-context.md
User needs to debug cluster → instructions/constraints/agent-capabilities.instructions.md + instructions/constraints/kubernetes-access.instructions.md User needs to debug cluster → instructions/constraints/agent-capabilities.instructions.md + instructions/constraints/kubernetes-access.instructions.md
User reports pod issues → instructions/constraints/container-limitations.instructions.md User reports pod issues → instructions/constraints/container-limitations.instructions.md
User works with Helm charts → instructions/skills/helm.instructions.md User works with Helm charts → instructions/skills/helm.instructions.md