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

feat(work-items): route an undiagnosed bug through diagnosis on the autonomous path

Abierto
  • ¿Algo no está bien?
#6,314 1 comentario 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
shell
Área
ai-infra-agents, developer-experience, tooling

Línea de trabajo

Start from plugins/work-items/skills/work/ and the triage skill that already documents unknown-root-cause routing after #6279 / PR #6296. Decide a marker (brief text or an existing status label; new labels need the GitHub infrastructure repo) that unattended triage writes when a bug is autonomous-eligible but undiagnosed. Teach /work-items:work to run diagnosis first when that marker is present, then continue to implement; named root causes must still skip diagnosis. Done when the three acceptance bullets hold for unattended triage.

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

Descripción

needs-human priority: medium work-class: structural

Problem

#6279 (PR #6296) taught /work-items:triage that a verified bug is not a diagnosed one: an unknown root cause routes to /debugging:debug (or /testing:diagnose) before any fix.

That routing is prose only. When triage runs unattended and marks a bug autonomous-eligible, /work-items:work never reads it, so the item still goes triage → work → implement and skips diagnosis. plugins/work-items/skills/work/ has no diagnosis route. Codex raised this as a P1 on PR #6296, thread PRRT_kwDOTCGFQM6o0otp.

Proposed fix

  • Triage records the "root cause unknown" state on the item in a form /work-items:work can act on: a marker in the brief, or an existing status label. New labels go through the GitHub infrastructure repository.
  • /work-items:work runs the diagnosis step first when the marker is present, then continues to the fix.

Acceptance

  • An unattended triage of a bug whose root cause is unknown leaves a marker /work-items:work reads.
  • /work-items:work routes that item through diagnosis before implement.
  • A bug whose root cause is already named still goes straight to the fix.
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
5 h 4 min
PR fusionados (30 d)
825

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.