feat: add Bloom's Taxonomy anchor#572
Conversation
Six-level hierarchy of cognitive learning objectives (Remember, Understand, Apply, Analyze, Evaluate, Create), pinned to the Revised 2001 version (Anderson & Krathwohl) with its knowledge dimension. Completes the teaching cluster (4MAT, Feynman, Socratic, ELI5): Bloom grades the cognitive level a step targets, so 'demonstrated understanding' can be set at Apply/Analyze rather than recall. EN + DE content, regenerated metadata (158 to 159), changelog and catalog entries.
|
Warning Ignoring CodeRabbit configuration file changes. For security, only the configuration from the base branch is applied for open source repositories. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughDer PR fügt den neuen Semantic Anchor "Bloom's Taxonomy" inklusive englischer und deutscher AsciiDoc-Dokumentation, Katalog- und Changelog-Einträgen, Website-JSON-Updates (anchors/categories/roles/metadata) und einer AsciiDoc‑Review-Regel hinzu. ChangesBloom's Taxonomy Anchor Integration
Estimated Code Review Effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly Related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/anchors/blooms-taxonomy.adoc`:
- Line 1: The top-level AsciiDoc header currently uses a single '=' ("= Bloom's
Taxonomy"); update that line to start with '==' so the top-level section begins
with "== Bloom's Taxonomy" to comply with the repository guideline that .adoc
top-level headers use '==' and maintain proper nesting.
In `@docs/anchors/blooms-taxonomy.de.adoc`:
- Line 1: The top-level AsciiDoc header currently uses a single equals sign ("=
Bloom's Taxonomy"); update this to use a double-equals top-level header ("==
Bloom's Taxonomy") so it conforms to the repo rule that top-level headers start
with "==", ensuring proper nesting for the rest of the document.
🪄 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: 769f0ecd-12ca-4dbb-aeca-3e0ed1fde4f3
📒 Files selected for processing (9)
docs/anchors/blooms-taxonomy.adocdocs/anchors/blooms-taxonomy.de.adocdocs/changelog.adocplugins/semantic-anchors/skills/semantic-anchor-translator/references/catalog.mdskill/semantic-anchor-translator/references/catalog.mdwebsite/public/data/anchors.jsonwebsite/public/data/categories.jsonwebsite/public/data/metadata.jsonwebsite/public/data/roles.json
| @@ -0,0 +1,62 @@ | |||
| = Bloom's Taxonomy | |||
There was a problem hiding this comment.
Top-Level-Header auf == umstellen.
Der Titel startet mit =, laut Repo-Regel für .adoc sollen Top-Level-Sections mit == beginnen.
As per coding guidelines, "**/*.adoc: ... proper nesting levels starting with == for top-level headers".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/anchors/blooms-taxonomy.adoc` at line 1, The top-level AsciiDoc header
currently uses a single '=' ("= Bloom's Taxonomy"); update that line to start
with '==' so the top-level section begins with "== Bloom's Taxonomy" to comply
with the repository guideline that .adoc top-level headers use '==' and maintain
proper nesting.
| @@ -0,0 +1,62 @@ | |||
| = Bloom's Taxonomy | |||
There was a problem hiding this comment.
Top-Level-Header auf == vereinheitlichen.
Der Dateikopf verwendet =, die AsciiDoc-Regel im Repo fordert für Top-Level ==.
As per coding guidelines, "**/*.adoc: ... proper nesting levels starting with == for top-level headers".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/anchors/blooms-taxonomy.de.adoc` at line 1, The top-level AsciiDoc
header currently uses a single equals sign ("= Bloom's Taxonomy"); update this
to use a double-equals top-level header ("== Bloom's Taxonomy") so it conforms
to the repo rule that top-level headers start with "==", ensuring proper nesting
for the rest of the document.
Re: CodeRabbit's two
|
CodeRabbit repeatedly flags the level-0 AsciiDoc document title (= Title) as a section-header violation and suggests demoting it to '=='. That is a false positive: all 292 anchor files use '=', and extract-metadata.js reads the title via getDocumentTitle(), which only the level-0 '=' populates — '==' would break the build. Add an explicit instruction to the docs/anchors path rule so this stops recurring.
2 participants
Adds Bloom's Taxonomy to the catalog. Verified against the four quality criteria (Precise, Rich, Consistent, Attributable) and the recognition test.
Why this anchor
It completes the teaching/learning cluster — 4MAT (lesson sequence), Feynman Technique (explain-it-back), Socratic Method (questioning), ELI5 (depth) — by adding the one axis they lack: the cognitive level of mastery. That lets "demonstrated understanding" be defined precisely (gate at Apply/Analyze, not Remember) instead of by a vague nod.
Consistency note
"Bloom's Taxonomy" is ambiguous between the 1956 original and the 2001 revision, and people misremember the top of the ladder. The anchor pins the Revised 2001 version (Anderson & Krathwohl) — verb levels ending in Create, plus the knowledge dimension — and explicitly flags that the hierarchy is a design heuristic, not a strict linear ladder. It also bounds scope: cognitive domain only (not affective/psychomotor).
Changes
docs/anchors/blooms-taxonomy.adoc+.de.adoc(EN + DE)website/public/data/*.json(additive — 158 → 159 anchors)docs/changelog.adoc— 2026-06-02 sectionskill/.../catalog.md(+ syncedplugins/copy)Category: Communication & Presentation. Proponents: Benjamin Bloom (1956); Anderson & Krathwohl (2001).
Summary by CodeRabbit
Dokumentation
Chores