Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#7,281 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
57/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
markdown, shell
Área
documentation, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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).

Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
7 h 42 min
PR fusionados (30 d)
923

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.