Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

knowledge: docpage-digest collision check can match the checklist's prose line, and no tag-exempt sub-shape fits the Documentation-Index banner

Aperta
  • Qualcosa non va?
#7,281 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
57/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
markdown, shell
Ambito
documentation, tooling

Direzione di ricerca

Read plugins/knowledge/skills/docpage-digest/SKILL.md, templates/checklist.md, and context/anthropic-docs-profile.md. Check how the collision check selects the Canonical URL value and how the profile categorizes the raw-md Documentation-Index banner. Update those instructions so the check reads the value line and the banner has one consistent disposition; verify both against the reproduction steps in the issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

priority: medium

Summary

Two small gaps in /knowledge:docpage-digest's template and publisher profile:

  1. The run-start collision check reads "the Canonical URL line" of an existing checklist, but the checklist template has the words Canonical URL in instructional prose three lines above the value line. A first-match read picks up the prose, finds no URL, and refuses a legitimate resume.
  2. The code.claude.com raw-md channel prepends a Documentation-Index banner to every page, but none of the profile's five tag-exempt sub-shapes fits it, so each digest improvises a tag for it.

Affected area / component

plugins/knowledge/skills/docpage-digest (templates/checklist.md, SKILL.md, context/anthropic-docs-profile.md)

Steps to reproduce

Gap 1:

  1. plugins/knowledge/skills/docpage-digest/templates/checklist.md:8 says "Fill Canonical URL and the resolved work root at run start"; the value line is - Canonical URL: at :11.
  2. SKILL.md:79 tells the collision check to "read the Canonical URL line" from an existing checklist.
  3. Run grep -m1 'Canonical URL' <work-root>/<slug>/docpage-digest-checklist.md on any filled checklist. It returns line 8's prose, not the value.

Gap 2:

  1. context/anthropic-docs-profile.md:29-31 says the channel prepends a Documentation-Index banner (verified on 187/187 pages) whose embedded fetch imperative is quoted data.
  2. context/anthropic-docs-profile.md:197-205 lists five tag-exempt sub-shapes: consumer-surface, archive-descriptive, metadata, navigation-pointer, blog-apparatus. None names the banner.
  3. context/anthropic-docs-profile.md:227-229 (pointer convention) says a directive pointer takes a vocabulary tag, not the exempt disposition. The banner directs the reader to fetch the index, so navigation-pointer conflicts with that rule.
  4. Digest any code.claude.com page and look at how its intro unit tags the banner row.

Expected behavior

The collision check reads the value line only, and the profile names one disposition for the channel banner.

Actual behavior

  • Gap 1: a naive first match reads the prose line and refuses the resume.
  • Gap 2: across 22 slices from one run, the banner row was tagged three different ways: 17 as tag-exempt (navigation-pointer), 4 as metadata, and 1 as cc-applicable.

Suggested fix

  • Anchor the collision check to ^- Canonical URL: in SKILL.md, or reword the template prose so it does not contain the literal label.
  • Name a single disposition for the raw-md channel banner in the profile's raw-md artifact list.

Environment

knowledge plugin 0.21.1 (line numbers from main on 2026-10-12).

Found during the upstream-pointer sweep (PRs #7061-#7274).

Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
8h 27m
PR unite (30g)
957

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di melodic-software/claude-code-plugins

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.