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

knowledge: docpage-digest dual verification defines no verdict vocabulary or pass/fail threshold

Abierto Apto para principiantes
  • ¿Algo no está bien?
#7,286 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
78/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
shell
Área
tooling

Línea de trabajo

Lee plugins/knowledge/skills/docpage-digest/context/dual-verification.md y el informe del verificador que define. Sigue el flujo del veredicto de la fase 4 y de los hallazgos aplazados; después, especifica el vocabulario de veredictos, la regla de aprobado/suspenso y si los hallazgos aplazados impiden completar el proceso. La tarea estará terminada cuando ambos documentos establezcan reglas coherentes y aplicables para los casos notificados.

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

Descripción

needs-human

Summary

/knowledge:docpage-digest's context/dual-verification.md owns both verification passes but names no verdict values and no rule for what separates a pass from a fail. Each verifier picks its own vocabulary and threshold, so verdicts are not comparable across arms or runs, and nothing says whether low findings deferred to the interview handoff block Phase 4 completion.

Affected area / component

plugins/knowledge/skills/docpage-digest/context/dual-verification.md and the verifier brief it defines

Steps to reproduce

  1. grep -c "PASS-WITH-FINDINGS\|FAIL" plugins/knowledge/skills/docpage-digest/context/dual-verification.md returns 0.
  2. Run two slices through Phase 4 and compare their verdict headers.

Expected behavior

The skill states the verdict set, the rule that sets it, and whether deferred findings block completion.

Actual behavior

Observed in one multi-page run:

  • On the memory page, both arms returned FAIL with two high findings each. On the skills page, four to five medium findings came back as PASS-WITH-FINDINGS.
  • One orchestrator had to define its own vocabulary in its verifier brief (PASS / ACCEPT-WITH-FIXES / FAIL by highest open severity), and later a re-verify pass rule. Before that rule existed, the hooks page's fourth re-verify held ACCEPT-WITH-FIXES over a single deferred low finding, noting that no ruling said deferred lows don't block.

Suggested fix

State in dual-verification.md and the verifier brief:

  • the verdict set (for example PASS / PASS-WITH-FINDINGS / FAIL);
  • the rule that sets it (for example, any open high finding means FAIL, and FAIL requires a corrections round);
  • whether findings deferred to the interview handoff block Phase 4 completion.

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.