feat: add 7 new anchors (Red/Green TDD, 4MAT, Walking Skeleton, Tracer Bullet, Thin Vertical Slice, Spike Solution, MVP)#425
Merged
Conversation
Contributor
WalkthroughDieses PR fügt mehrere neue semantische Anker (engl./deutsch) hinzu und registriert sie in den Site-/Katalog‑Daten (JSON, Sitemap, llms.txt, Changelog, translator‑Katalog) sowie in der Master‑Include‑Datei Changes
Sequence Diagram(s)(Sektionen überspringen — Änderungen sind Dokumentationsergänzungen; kein neues mehrstufiges Feature‑Flow) Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (5)
docs/anchors/spike-solution.de.adoc (1)
5-5: Proponenten-Metadaten an den dokumentierten Inhalt anpassen.Im Text wird Ron Jeffries als Schlüsselvertreter genannt, aber im Metadatenfeld
:proponents:fehlt er. Bitte Metadaten und Inhalt synchron halten, damit Extrakte konsistent bleiben.Vorgeschlagene Anpassung
-:proponents: Kent Beck +:proponents: Kent Beck, Ron JeffriesAs per coding guidelines: „Pflichtfelder: :categories:, :roles:, :proponents:“ und „Zuordenbar: Rückverfolgbar zu Proponenten, Publikationen oder Standards“.
Also applies to: 31-31
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/anchors/spike-solution.de.adoc` at line 5, Die Metadaten-Zeile :proponents: stimmt nicht mit dem Inhalt überein — Ron Jeffries wird im Text als Schlüsselvertreter genannt, fehlt aber in der Proponenten-Metadatenliste; aktualisiere die :proponents:-Feldwert (aktuell "Kent Beck") in der Datei so dass beide Proponenten (z. B. "Kent Beck, Ron Jeffries") enthalten sind und dem erwarteten Format der anderen Dokumente entspricht, damit Pflichtfeld :proponents: rückverfolgbar und konsistent ist.docs/anchors/spike-solution.adoc (1)
5-5::proponents:sollte alle genannten Schlüsselvertreter abbilden.Der Fließtext nennt Kent Beck und Ron Jeffries, die Metadaten aktuell nur Kent Beck. Bitte angleichen, damit Attribuierung in generierten Daten vollständig bleibt.
Vorgeschlagene Anpassung
-:proponents: Kent Beck +:proponents: Kent Beck, Ron JeffriesAs per coding guidelines: „All new semantic anchors must include
:proponents:…“ und „Zuordenbar: Rückverfolgbar zu Proponenten …“.Also applies to: 31-31
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/anchors/spike-solution.adoc` at line 5, The metadata key :proponents: currently lists only "Kent Beck" but the prose names both Kent Beck and Ron Jeffries; update the :proponents: anchor to include both names (Kent Beck and Ron Jeffries) so generated attribution matches the text; ensure the same change is applied to the other occurrence referenced (the second :proponents: entry mentioned) to keep metadata consistent across the document.website/public/llms.txt (2)
3-3: Den Header-Count besser ausanchors.jsonableiten statt hart zu codieren.Die Zahl in
llms.txtdriftet sonst leicht von der tatsächlichen Anchor-Anzahl weg.Based on learnings: In diesem Repository ist
anchors.jsondie maßgebliche Quelle für die exakte Anzahl eindeutiger Anchor-IDs.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@website/public/llms.txt` at line 3, Die feste Zahl in website/public/llms.txt soll nicht manuell stehen; stattdessen die exakte Anzahl eindeutiger Anchor-IDs aus anchors.json ableiten und llms.txt bei Build/Update automatisch aktualisieren (oder ein kurzes Script/Make-Task hinzufügen), sodass der Text "136 well-defined terms..." dynamisch mit der Länge der Anchor-Liste in anchors.json übereinstimmt; referenziere beim Fix die Dateien website/public/llms.txt und anchors.json und implementiere die Ersetzung/Regeneration dort, wo die statische Datei erzeugt oder deployed wird.
5302-5440: Neue Kategorie „Workflow“ klar von „Development Workflow“ abgrenzen.Aktuell ist die Trennlinie semantisch sehr nah; das kann Filterlogik und Kategorieschärfe verwässern. Entweder klar als „Workflow Recipes/Compositions“ benennen oder unter bestehender Kategorie konsolidieren.
Based on learnings: Nach Phase 1 sollen Kategorien MECE-konform sein (Mutually Exclusive, Collectively Exhaustive).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@website/public/llms.txt` around lines 5302 - 5440, The new "## Workflow" section is semantically overlapping with existing "Development Workflow" and should be made MECE; either rename "## Workflow" to "## Workflow Recipes" (and rename each "### Workflow: ..." to "### Recipe: Architecture Documentation", "### Recipe: Structured Code Review", etc.) to clarify it's a composed set of workflows, or merge its items under the existing "Development Workflow" category; update heading tokens ("## Workflow", "### Workflow: Architecture Documentation", "### Workflow: Structured Code Review", etc.) accordingly and ensure filters/metadata use the new unique category name so Phase 1 categories remain mutually exclusive and collectively exhaustive.website/public/data/categories.json (1)
217-226: Kategorie „workflow“ überschneidet sich potenziell mit „development-workflow“.Bitte die Kategoriegrenzen schärfen (z. B. Umbenennung in „workflow-recipes“ inkl. klarer Definition) oder konsolidieren, damit die Taxonomie eindeutig bleibt.
Based on learnings: Nach Phase 1 sollen Kategorien MECE-konform sein (Mutually Exclusive, Collectively Exhaustive).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@website/public/data/categories.json` around lines 217 - 226, Die Kategorie mit id "workflow" / name "Workflow" überschneidet sich mit "development-workflow": either sharpen the boundary by renaming id "workflow" to "workflow-recipes" and update name to "Workflow Recipes" plus add a short definition (description field) clarifying it holds actionable recipes like the anchors ["workflow-architecture-documentation","workflow-code-review","workflow-requirements-to-spec","workflow-strategic-analysis","workflow-tdd-clean-architecture"], or consolidate this entry into the existing "development-workflow" category and remove the duplicate id; update any references to the affected anchors accordingly to keep the taxonomy MECE.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/anchors/tracer-bullet.adoc`:
- Line 5: The :proponents: entry uses inconsistent naming ("Andy Hunt" vs.
"Andrew Hunt"); standardize the proponent name to a single canonical form (use
"Andrew Hunt") in the :proponents: attribute for tracer-bullet.adoc and any
other docs/anchors/*.adoc anchors that reference "Andy Hunt" (also update the
other occurrence referenced in the review). Locate and replace the :proponents:
line(s) containing "Andy Hunt" so all anchors consistently read "Andrew Hunt,
David Thomas".
In `@website/public/data/anchors.json`:
- Around line 3507-3608: Die fünf neuen Anchor-Einträge (ids:
workflow-architecture-documentation, workflow-code-review,
workflow-requirements-to-spec, workflow-strategic-analysis,
workflow-tdd-clean-architecture) verweisen auf nicht existierende Dateien
(filePath: docs/anchors/workflow-*.adoc); entweder create die korrespondierenden
docs/anchors/workflow-*.adoc Dateien mit passende frontmatter/title/content und
korrespondierenden IDs, oder remove diese fünf Einträge aus
website/public/data/anchors.json until the .adoc sources exist; additionally
update skill/semantic-anchor-translator/references/catalog.md to include the new
anchors (or remove their references) so AI discovery remains consistent.
---
Nitpick comments:
In `@docs/anchors/spike-solution.adoc`:
- Line 5: The metadata key :proponents: currently lists only "Kent Beck" but the
prose names both Kent Beck and Ron Jeffries; update the :proponents: anchor to
include both names (Kent Beck and Ron Jeffries) so generated attribution matches
the text; ensure the same change is applied to the other occurrence referenced
(the second :proponents: entry mentioned) to keep metadata consistent across the
document.
In `@docs/anchors/spike-solution.de.adoc`:
- Line 5: Die Metadaten-Zeile :proponents: stimmt nicht mit dem Inhalt überein —
Ron Jeffries wird im Text als Schlüsselvertreter genannt, fehlt aber in der
Proponenten-Metadatenliste; aktualisiere die :proponents:-Feldwert (aktuell
"Kent Beck") in der Datei so dass beide Proponenten (z. B. "Kent Beck, Ron
Jeffries") enthalten sind und dem erwarteten Format der anderen Dokumente
entspricht, damit Pflichtfeld :proponents: rückverfolgbar und konsistent ist.
In `@website/public/data/categories.json`:
- Around line 217-226: Die Kategorie mit id "workflow" / name "Workflow"
überschneidet sich mit "development-workflow": either sharpen the boundary by
renaming id "workflow" to "workflow-recipes" and update name to "Workflow
Recipes" plus add a short definition (description field) clarifying it holds
actionable recipes like the anchors
["workflow-architecture-documentation","workflow-code-review","workflow-requirements-to-spec","workflow-strategic-analysis","workflow-tdd-clean-architecture"],
or consolidate this entry into the existing "development-workflow" category and
remove the duplicate id; update any references to the affected anchors
accordingly to keep the taxonomy MECE.
In `@website/public/llms.txt`:
- Line 3: Die feste Zahl in website/public/llms.txt soll nicht manuell stehen;
stattdessen die exakte Anzahl eindeutiger Anchor-IDs aus anchors.json ableiten
und llms.txt bei Build/Update automatisch aktualisieren (oder ein kurzes
Script/Make-Task hinzufügen), sodass der Text "136 well-defined terms..."
dynamisch mit der Länge der Anchor-Liste in anchors.json übereinstimmt;
referenziere beim Fix die Dateien website/public/llms.txt und anchors.json und
implementiere die Ersetzung/Regeneration dort, wo die statische Datei erzeugt
oder deployed wird.
- Around line 5302-5440: The new "## Workflow" section is semantically
overlapping with existing "Development Workflow" and should be made MECE; either
rename "## Workflow" to "## Workflow Recipes" (and rename each "### Workflow:
..." to "### Recipe: Architecture Documentation", "### Recipe: Structured Code
Review", etc.) to clarify it's a composed set of workflows, or merge its items
under the existing "Development Workflow" category; update heading tokens ("##
Workflow", "### Workflow: Architecture Documentation", "### Workflow: Structured
Code Review", etc.) accordingly and ensure filters/metadata use the new unique
category name so Phase 1 categories remain mutually exclusive and collectively
exhaustive.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: 6a7b9e31-80f8-424a-990e-73ede38c2d76
📒 Files selected for processing (23)
docs/all-anchors.adocdocs/anchors/4mat.adocdocs/anchors/4mat.de.adocdocs/anchors/mvp.adocdocs/anchors/mvp.de.adocdocs/anchors/red-green-tdd.adocdocs/anchors/red-green-tdd.de.adocdocs/anchors/spike-solution.adocdocs/anchors/spike-solution.de.adocdocs/anchors/thin-vertical-slice.adocdocs/anchors/thin-vertical-slice.de.adocdocs/anchors/tracer-bullet.adocdocs/anchors/tracer-bullet.de.adocdocs/anchors/walking-skeleton.adocdocs/anchors/walking-skeleton.de.adocdocs/changelog.adocskill/semantic-anchor-translator/references/catalog.mdwebsite/public/data/anchors.jsonwebsite/public/data/categories.jsonwebsite/public/data/metadata.jsonwebsite/public/data/roles.jsonwebsite/public/llms.txtwebsite/public/sitemap.xml
| :categories: software-architecture | ||
| :roles: software-architect, software-developer | ||
| :related: walking-skeleton, spike-solution, thin-vertical-slice | ||
| :proponents: Andy Hunt, David Thomas |
Contributor
There was a problem hiding this comment.
Proponentenname ist uneinheitlich (Andy vs. Andrew).
Bitte die Schreibweise vereinheitlichen, damit Attribution und spätere Suche konsistent bleiben.
✏️ Vorschlag zur Vereinheitlichung
-:proponents: Andy Hunt, David Thomas
+:proponents: Andrew Hunt, David ThomasAs per coding guidelines docs/anchors/*.adoc: new semantic anchors must include attributable proponents (:proponents:) that are clearly traceable.
Also applies to: 31-31
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/anchors/tracer-bullet.adoc` at line 5, The :proponents: entry uses
inconsistent naming ("Andy Hunt" vs. "Andrew Hunt"); standardize the proponent
name to a single canonical form (use "Andrew Hunt") in the :proponents:
attribute for tracer-bullet.adoc and any other docs/anchors/*.adoc anchors that
reference "Andy Hunt" (also update the other occurrence referenced in the
review). Locate and replace the :proponents: line(s) containing "Andy Hunt" so
all anchors consistently read "Andrew Hunt, David Thomas".
Comment on lines
+3507
to
+3608
| { | ||
| "id": "workflow-architecture-documentation", | ||
| "title": "Workflow: Architecture Documentation", | ||
| "categories": [ | ||
| "workflow" | ||
| ], | ||
| "roles": [ | ||
| "software-architect", | ||
| "technical-writer" | ||
| ], | ||
| "related": [], | ||
| "proponents": [ | ||
| "Ralf D. Müller", | ||
| "Gernot Starke", | ||
| "Michael Nygard" | ||
| ], | ||
| "tags": [], | ||
| "filePath": "docs/anchors/workflow-architecture-documentation.adoc", | ||
| "tier": 3 | ||
| }, | ||
| { | ||
| "id": "workflow-code-review", | ||
| "title": "Workflow: Structured Code Review", | ||
| "categories": [ | ||
| "workflow" | ||
| ], | ||
| "roles": [ | ||
| "software-developer", | ||
| "team-lead", | ||
| "qa-engineer" | ||
| ], | ||
| "related": [], | ||
| "proponents": [ | ||
| "Michael Fagan", | ||
| "Robert C. Martin" | ||
| ], | ||
| "tags": [], | ||
| "filePath": "docs/anchors/workflow-code-review.adoc", | ||
| "tier": 3 | ||
| }, | ||
| { | ||
| "id": "workflow-requirements-to-spec", | ||
| "title": "Workflow: Requirements to Specification", | ||
| "categories": [ | ||
| "workflow" | ||
| ], | ||
| "roles": [ | ||
| "business-analyst", | ||
| "product-owner", | ||
| "qa-engineer" | ||
| ], | ||
| "related": [], | ||
| "proponents": [ | ||
| "Dan North", | ||
| "Jeff Patton", | ||
| "Mike Cohn" | ||
| ], | ||
| "tags": [], | ||
| "filePath": "docs/anchors/workflow-requirements-to-spec.adoc", | ||
| "tier": 3 | ||
| }, | ||
| { | ||
| "id": "workflow-strategic-analysis", | ||
| "title": "Workflow: Strategic Architecture Analysis", | ||
| "categories": [ | ||
| "workflow" | ||
| ], | ||
| "roles": [ | ||
| "software-architect", | ||
| "consultant", | ||
| "team-lead" | ||
| ], | ||
| "related": [], | ||
| "proponents": [ | ||
| "Simon Wardley", | ||
| "Fritz Zwicky", | ||
| "Dave Snowden" | ||
| ], | ||
| "tags": [], | ||
| "filePath": "docs/anchors/workflow-strategic-analysis.adoc", | ||
| "tier": 3 | ||
| }, | ||
| { | ||
| "id": "workflow-tdd-clean-architecture", | ||
| "title": "Workflow: TDD with Clean Architecture", | ||
| "categories": [ | ||
| "workflow" | ||
| ], | ||
| "roles": [ | ||
| "software-developer", | ||
| "software-architect" | ||
| ], | ||
| "related": [], | ||
| "proponents": [ | ||
| "Robert C. Martin", | ||
| "Steve Freeman", | ||
| "Nat Pryce" | ||
| ], | ||
| "tags": [], | ||
| "filePath": "docs/anchors/workflow-tdd-clean-architecture.adoc", | ||
| "tier": 3 | ||
| }, |
Contributor
There was a problem hiding this comment.
Fehlende Quelldateien für Workflow-Anchors führen zu kaputten filePath-Referenzen.
Line 3507–3608: Die fünf neuen Workflow-Einträge referenzieren docs/anchors/workflow-*.adoc, die laut bereitgestelltem Kontext aktuell nicht im Filesystem vorhanden sind. Das verursacht inkonsistente Metadaten und potenziell tote Seiten/Links im Frontend.
Bitte entweder die fünf .adoc-Dateien ergänzen oder die Einträge aus den generierten Daten entfernen, bis die Quellen existieren.
Based on learnings, when adding new semantic anchors, update both docs/anchors/<name>.adoc and skill/semantic-anchor-translator/references/catalog.md to ensure discoverability by AI agents.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@website/public/data/anchors.json` around lines 3507 - 3608, Die fünf neuen
Anchor-Einträge (ids: workflow-architecture-documentation, workflow-code-review,
workflow-requirements-to-spec, workflow-strategic-analysis,
workflow-tdd-clean-architecture) verweisen auf nicht existierende Dateien
(filePath: docs/anchors/workflow-*.adoc); entweder create die korrespondierenden
docs/anchors/workflow-*.adoc Dateien mit passende frontmatter/title/content und
korrespondierenden IDs, oder remove diese fünf Einträge aus
website/public/data/anchors.json until the .adoc sources exist; additionally
update skill/semantic-anchor-translator/references/catalog.md to include the new
anchors (or remove their references) so AI discovery remains consistent.
…-424) - Red/Green TDD → testing-quality (LLM-Coding#412, @petehodgson-tribe) - 4MAT → communication-presentation (LLM-Coding#413, @rweisleder) - Walking Skeleton → software-architecture (LLM-Coding#420, @cpoepke) - Tracer Bullet → software-architecture (LLM-Coding#421, @cpoepke) - Thin Vertical Slice → development-workflow (LLM-Coding#422, @cpoepke) - Spike Solution → development-workflow (LLM-Coding#423, @cpoepke) - Minimum Viable Product (MVP) → strategic-planning (LLM-Coding#424, @cpoepke) All anchors include EN + DE content, catalog entries, changelog, and regenerated metadata. Note: the proposed "System Inception Patterns" category (LLM-Coding#414) was declined in favor of sorting each anchor into existing categories based on its primary concern (architecture validation, delivery workflow, or product-hypothesis validation). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
raifdmueller
force-pushed
the
feat/7-new-anchors
branch
from
bc0b966 to
465983c
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
skill/semantic-anchor-translator/references/catalog.md (1)
1-547:⚠️ Potential issue | 🔴 CriticalKatalog-Synchronisierung mit
docs/anchors/*.adocunvollständig — Semantische Unstimmigkeit gefundenAutomatisierte Überprüfung zeigt 22 Abweichungen zwischen Dokumenttiteln und Katalogeinträgen. Die meisten sind Formatierungsvarianten (z.B.
SOLID-SRPvs.SOLID-Single Responsibility Principle), aber eine semantische Diskrepanz erfordert sofortige Korrektur:
- Katalog:
Problem Space NVC(Needs-Value-Constraints Framework)- Docs:
Nonviolent Communication (Rosenberg)indocs/anchors/problem-space-nvc.adocDiese Konzepte sind nicht identisch. Der Katalog muss entweder korrigiert oder die Dokumentdatei umbenannt werden, um Konsistenz für den Semantic-Anchor-Translator zu gewährleisten.
Zusätzlich sollten Titelformate normalisiert werden (z.B. Entfernung von „according to"/"by"-Zusätzen in verkürzten Katalogversionen), um zukünftige Sync-Fehler zu vermeiden. Template-Datei (
docs/anchors/_template.adoc) aus Vergleichen ausschließen.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skill/semantic-anchor-translator/references/catalog.md` around lines 1 - 547, Die Synchronisation schlägt fehl, weil der Katalogeintrag "Problem Space NVC" nicht mit dem Dokumenttitel "Nonviolent Communication (Rosenberg)" in docs/anchors/problem-space-nvc.adoc übereinstimmt; bitte behebe das, indem du entweder den Katalogeintrag in catalog.md von "Problem Space NVC" (Needs-Value-Constraints Framework) auf "Nonviolent Communication (Rosenberg)" umbenennst oder alternativ die Datei docs/anchors/problem-space-nvc.adoc so umbenennst/umtitelst, dass sie semantisch mit "Problem Space NVC" übereinstimmt; zusätzlich normalisiere ähnliche Titelvarianten im Katalog (z.B. "SOLID-SRP" → "SOLID — Single Responsibility Principle", entferne Anhängsel wie "according to"/"by") und stelle sicher, dass die Template-Datei docs/anchors/_template.adoc von der Synchronisationsprüfung ausgeschlossen ist, damit der Semantic-Anchor-Translator konsistente Ankerpaare findet.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@website/public/llms.txt`:
- Line 3: Header number mismatch: update the header string "131 well-defined
terms, methodologies, and frameworks" in website/public/llms.txt to "130
well-defined terms, methodologies, and frameworks" so it matches the 130 unique
Anchor IDs in website/public/data/anchors.json; verify the exact header text is
replaced and run a quick consistency check against anchors.json to confirm
counts match.
---
Outside diff comments:
In `@skill/semantic-anchor-translator/references/catalog.md`:
- Around line 1-547: Die Synchronisation schlägt fehl, weil der Katalogeintrag
"Problem Space NVC" nicht mit dem Dokumenttitel "Nonviolent Communication
(Rosenberg)" in docs/anchors/problem-space-nvc.adoc übereinstimmt; bitte behebe
das, indem du entweder den Katalogeintrag in catalog.md von "Problem Space NVC"
(Needs-Value-Constraints Framework) auf "Nonviolent Communication (Rosenberg)"
umbenennst oder alternativ die Datei docs/anchors/problem-space-nvc.adoc so
umbenennst/umtitelst, dass sie semantisch mit "Problem Space NVC" übereinstimmt;
zusätzlich normalisiere ähnliche Titelvarianten im Katalog (z.B. "SOLID-SRP" →
"SOLID — Single Responsibility Principle", entferne Anhängsel wie "according
to"/"by") und stelle sicher, dass die Template-Datei docs/anchors/_template.adoc
von der Synchronisationsprüfung ausgeschlossen ist, damit der
Semantic-Anchor-Translator konsistente Ankerpaare findet.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: 1ea9c0ed-2ab8-4b25-bdd6-e34842905d20
📒 Files selected for processing (23)
docs/all-anchors.adocdocs/anchors/4mat.adocdocs/anchors/4mat.de.adocdocs/anchors/mvp.adocdocs/anchors/mvp.de.adocdocs/anchors/red-green-tdd.adocdocs/anchors/red-green-tdd.de.adocdocs/anchors/spike-solution.adocdocs/anchors/spike-solution.de.adocdocs/anchors/thin-vertical-slice.adocdocs/anchors/thin-vertical-slice.de.adocdocs/anchors/tracer-bullet.adocdocs/anchors/tracer-bullet.de.adocdocs/anchors/walking-skeleton.adocdocs/anchors/walking-skeleton.de.adocdocs/changelog.adocskill/semantic-anchor-translator/references/catalog.mdwebsite/public/data/anchors.jsonwebsite/public/data/categories.jsonwebsite/public/data/metadata.jsonwebsite/public/data/roles.jsonwebsite/public/llms.txtwebsite/public/sitemap.xml
✅ Files skipped from review due to trivial changes (18)
- docs/changelog.adoc
- docs/all-anchors.adoc
- docs/anchors/tracer-bullet.adoc
- docs/anchors/red-green-tdd.adoc
- docs/anchors/spike-solution.adoc
- docs/anchors/thin-vertical-slice.de.adoc
- docs/anchors/red-green-tdd.de.adoc
- docs/anchors/4mat.adoc
- website/public/data/metadata.json
- docs/anchors/4mat.de.adoc
- docs/anchors/spike-solution.de.adoc
- docs/anchors/tracer-bullet.de.adoc
- docs/anchors/mvp.adoc
- docs/anchors/walking-skeleton.de.adoc
- docs/anchors/walking-skeleton.adoc
- website/public/data/categories.json
- docs/anchors/mvp.de.adoc
- website/public/data/anchors.json
🚧 Files skipped from review as they are similar to previous changes (3)
- website/public/data/roles.json
- docs/anchors/thin-vertical-slice.adoc
- website/public/sitemap.xml
| # Semantic Anchors — Complete Reference | ||
|
|
||
| > 123 well-defined terms, methodologies, and frameworks | ||
| > 131 well-defined terms, methodologies, and frameworks |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Erwartung:
# - headline_count entspricht der Anzahl eindeutiger IDs in website/public/data/anchors.json
headline_count="$(sed -n '3p' website/public/llms.txt | grep -oE '[0-9]+' | head -n1)"
json_count="$(python - <<'PY'
import json
from pathlib import Path
p = Path("website/public/data/anchors.json")
data = json.loads(p.read_text(encoding="utf-8"))
ids = {item.get("id") for item in data if isinstance(item, dict) and item.get("id")}
print(len(ids))
PY
)"
echo "llms.txt headline count: ${headline_count}"
echo "anchors.json unique id count: ${json_count}"
if [ "${headline_count}" != "${json_count}" ]; then
echo "Mismatch detected"
exit 1
fi
echo "Counts match"Repository: LLM-Coding/Semantic-Anchors
Length of output: 151
Überschrift in Zeile 3 aktualisieren: 131 sollte 130 sein.
Die Überprüfung gegen website/public/data/anchors.json zeigt ein Missverhältnis: Die Kopfzeile listet „131" auf, aber die Datei enthält genau 130 eindeutige Anchor-IDs. Bitte die Zahl auf 130 korrigieren, um Konsistenz mit der autorisierenden Quelle zu wahren.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@website/public/llms.txt` at line 3, Header number mismatch: update the header
string "131 well-defined terms, methodologies, and frameworks" in
website/public/llms.txt to "130 well-defined terms, methodologies, and
frameworks" so it matches the 130 unique Anchor IDs in
website/public/data/anchors.json; verify the exact header text is replaced and
run a quick consistency check against anchors.json to confirm counts match.
This was referenced Apr 12, 2026
Closed
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds 7 new semantic anchors in a single PR, addressing issues #412, #413, and #420–#424.
testing-qualitycommunication-presentationsoftware-architecturesoftware-architecturedevelopment-workflowdevelopment-workflowstrategic-planningEach anchor includes:
skill/semantic-anchor-translator/references/catalog.mdCategory decision for #414
The category proposal "System Inception Patterns" in #414 was declined. Rationale (full reasoning in the #414 comment):
software-architecturedevelopment-workflowstrategic-planningTest plan
semantic-anchor-translatorskill🤖 Generated with Claude Code
Summary by CodeRabbit