Files
grok-botandCommandCodeBot 2bde15c077 docs: update AGENTS.md, CLAUDE.md, gitignore
AGENTS.md: note C++17 modernization complete.
CLAUDE.md: list all test targets.
.gitignore: add .aider* pattern.

Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
2026-06-13 08:50:50 +02:00

5.0 KiB

CLAUDE.md — Regelwerk

Primäre Verhaltensdefinition: AGENTS.md. Diese Datei ergänzt nur um plattformspezifische Details und verfügbare Skills.

Plattform & Build

  • OS: macOS (Darwin)
  • Compiler: Clang via Xcode CLT
  • Build: CMake 3.16+ + Ninja, Verzeichnis build/
# Konfiguration (einmalig)
cmake -B build -G Ninja -DBUILD_TESTS=ON
cmake --build build -j$(sysctl -n hw.logicalcpu)

# Tests
ctest --test-dir build --output-on-failure           # alle
ctest --test-dir build --output-on-failure -R name   # einzelner Test
./build/datecalc_test                                 # direkt mit Ausgabe

Dateistruktur

  • src/ — Produktionscode (~230 .cpp, ~450 .hpp)
  • tests/ — Unit-Tests (xml, datecalc, tools, menge, bitset, map, leer, list, mstimer, msmem, intmenge, infrastructure, json, json_converter, json_deserialize, jsontools, zlibcompress, bitset_catch, leistungflags, predicates, actions, predicates_batch1, integration)
  • refactorings/ — Ideen-Dokumente und Fortschritts-Tracking
  • docs/ — Fachbeschreibungen (SB414 etc.), Architektur, Domänenmodell

Kontext-Schutz

NIEMALS lesen:

  • src/aktsource/gen_ops*.cpp — auto-generierte OPS-Katalogdaten (~200K Zeilen/Datei)
  • src/aktsource/go*.cpp, src/aktsource/rw*.cpp — generierte Katalogdaten (~100 MB insgesamt)

Bei Katalog-Fragen die entsprechenden .hpp-Header nutzen.

Skills

Verfügbar unter .pi/skills/ und .claude/skills/:

Skill Verwendung
cavecrew Subagent-Delegation (investigator/builder/reviewer)
caveman Ultra-kompakte Kommunikation
caveman-commit Komprimierte Commit-Messages
context-mode Token-optimierte Verarbeitung großer Outputs
grill-with-docs Plan-Review gegen Domänenmodell
karpathy-guidelines LLM-Coding-Fehler vermeiden
review-html Interaktive HTML-Code-Reviews
to-prd PRD aus Konversation generieren
gitnexus-* Code-Intelligence (Impact, Explore, Debug, Refactor) — Details in AGENTS.md

Extensions

Projekt-lokal unter .pi/extensions/, werden beim Start automatisch geladen:

Extension Funktion
protected-paths Blockiert read/write/edit auf auto-generierte Katalogdaten (src/aktsource/)
git-checkpoint Erstellt git stash vor jedem Turn, Restore bei /fork
dirty-repo-guard Blockiert /new, /resume, /fork bei uncommitteten Änderungen

GitNexus — Code Intelligence

This project is indexed by GitNexus as regelwerk (18085 symbols, 41447 relationships, 300 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.

If any GitNexus tool warns the index is stale, run npx gitnexus analyze in terminal first.

Always Do

  • MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run gitnexus_impact({target: "symbolName", direction: "upstream"}) and report the blast radius (direct callers, affected processes, risk level) to the user.
  • MUST run gitnexus_detect_changes() before committing to verify your changes only affect expected symbols and execution flows.
  • MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
  • When exploring unfamiliar code, use gitnexus_query({query: "concept"}) to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
  • When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use gitnexus_context({name: "symbolName"}).

Never Do

  • NEVER edit a function, class, or method without first running gitnexus_impact on it.
  • NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
  • NEVER rename symbols with find-and-replace — use gitnexus_rename which understands the call graph.
  • NEVER commit changes without running gitnexus_detect_changes() to check affected scope.

Resources

Resource Use for
gitnexus://repo/regelwerk/context Codebase overview, check index freshness
gitnexus://repo/regelwerk/clusters All functional areas
gitnexus://repo/regelwerk/processes All execution flows
gitnexus://repo/regelwerk/process/{name} Step-by-step execution trace

CLI

Task Read this skill file
Understand architecture / "How does X work?" .claude/skills/gitnexus/gitnexus-exploring/SKILL.md
Blast radius / "What breaks if I change X?" .claude/skills/gitnexus/gitnexus-impact-analysis/SKILL.md
Trace bugs / "Why is X failing?" .claude/skills/gitnexus/gitnexus-debugging/SKILL.md
Rename / extract / split / refactor .claude/skills/gitnexus/gitnexus-refactoring/SKILL.md
Tools, resources, schema reference .claude/skills/gitnexus/gitnexus-guide/SKILL.md
Index, status, clean, wiki CLI commands .claude/skills/gitnexus/gitnexus-cli/SKILL.md