Sync from fork: XY Problem + Kano + Bausteinsicht example + Rabauer video & footer#461
Merged
Conversation
Communication anti-pattern from technical-support culture: the asker requests help with attempted solution Y while the underlying goal X is hidden. Coined by Mark Jason Dominus (2001 comp.lang.perl.misc), formalised in Eric S. Raymond's 'How To Ask Questions The Smart Way'. Categories: dialogue-interaction, problem-solving. Roles: software-developer, team-lead, consultant, business-analyst. Proposed by @dernerl in LLM-Coding#457.
Bumps three transitive dev dependencies to clear one high and two moderate advisories that were failing the Dependency Security Audit on the test workflow.
feat: add XY Problem anchor (LLM-Coding#457)
Two-hour English live-coding session with Johannes Rabauer (youtu.be/Q_DWMayAQEQ, May 2026). Added to both the EN and DE About pages using the existing GDPR-friendly YouTube facade pattern (no third-party network until the user clicks).
…oding feat(about): embed Rabauer live-coding session video
Mirrors the existing HMZE entry in the footer's 'as seen on' row. The logo was downloaded from rabauer.dev and is stored locally in public/ to keep the footer free of third-party network calls. Links to rabauer.dev (Johannes Rabauer's site) where the live coding session is featured. The PNG is force-added because the repo root .gitignore excludes *.png; hmze-logo.png is tracked the same way.
feat(footer): add 'as seen on rabauer.dev' link with logo
Bausteinsicht (https://doctoolchain.org/Bausteinsicht/) is a bidirectional sync between a structured JSON architecture model and draw.io diagrams — Architecture-as-Code meets draw.io. Built with the spec-driven workflow on this site. Updates 'three open source projects' / 'drei Open-Source-Projekte' counters to four in both EN and DE workflow pages.
…cht-example feat(workflow): add Bausteinsicht as fourth example project
Two-dimensional quality model by Noriaki Kano (1984) classifying features as Must-be (basic), Performance (linear), Attractive (delighter), Indifferent or Reverse. Surveyed via paired functional/dysfunctional questions; categories decay over time (Delighter → Performer → Must-be). Categories: strategic-planning, requirements-engineering. Roles: product-owner, business-analyst, ux-designer, team-lead. Closes LLM-Coding#459.
feat: add Kano Model anchor (LLM-Coding#459)
John P. Kotter's classic transformation framework from 'Leading Change' (HBR 1995, book 1996): urgency, guiding coalition, vision, communication, empowerment, short-term wins, consolidation, anchor in culture. The 8 steps invert the 8 common errors Kotter identified in failed transformations. Categories: strategic-planning. Roles: team-lead, consultant, product-owner, business-analyst. Closes LLM-Coding#460.
feat: add Kotter's 8-Step Change Model anchor (LLM-Coding#460)
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (15)
WalkthroughDas PR führt drei neue Semantic Anchors (XY Problem, Kano Modell, Kotter's 8-Stufen-Änderungsmodell) mit englischer und deutscher Dokumentation ein. Zusätzlich werden Katalogeinträge und Changelog aktualisiert, ein neuer rabauer.dev Footer-Link mit i18n-Unterstützung hinzugefügt, YouTube-Embeds auf der About-Seite aktualisiert und die Workflow-Dokumentation angepasst. ChangesNeue Semantic Anchors
Website und Dokumentation Updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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 |
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
Brings 5 merged features from the development fork (
raifdmueller/Semantic-Anchors) to upstream so they land on the public site (llm-coding.github.io/Semantic-Anchors):Kotter's 8-Step Change Model (#460) is pending in fork PR #24 and will sync in a follow-up.
Closed issues
Test plan
All five PRs passed the fork's CI (lint, format, security audit, E2E, CodeQL) before merge. The fork's GitHub Pages deployment is live at https://raifdmueller.github.io/Semantic-Anchors/ and shows 138 anchors (vs. 136 on upstream).
Summary by CodeRabbit
Neue Funktionen
Dokumentation