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

feat: a skill that finds where the session's skills didn't fit and files the gaps

Abierto
  • ¿Algo no está bien?
#6,417 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
shell
Área
ai, developer-experience, tooling

Línea de trabajo

This is a new skill (suggested names /plugin-quality:fit-gaps or /session-flow:skill-fit) that must read on-disk session transcripts and subagent returns, attribute gaps to owning plugins, de-duplicate with gh issue list --search, and only file issues after owner confirmation. Start from the existing skills named in the issue (/discipline:use-your-skills, /plugin-quality:audit, /session-flow:retro) and from session dba79e68-af19-4ecc-a0ce-69d8b1dbefbb plus issues #6412 and #6413 as the intended output. Done means the skill presents a ledger and files evidence-first issues only on yes; this is product design, not a one-file edit.

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

Descripción

needs-human needs-triage

Problem

When a skill doesn't fit the work in front of it, the session quietly works around it. That workaround is the most useful feedback a plugin can get, and today it is lost unless someone notices and files it by hand.

In the 2026-10-04 CI-performance session the owner asked for that by hand twice. Each time the coordinator reconstructed the gaps from memory and filed #6412 and #6413. The gaps it found:

  • implement-dispatch needs a PLAN.md, but the work came as scoped audit output, so workers were hand-dispatched with re-typed lifecycle rules;
  • workers stalled five times waiting on their own background work;
  • a research skill's verifier failed twice on labeling for vendor-documented facts, so the loop was stopped by judgment;
  • workers' classifier denials could not see the owner's approval, so edits were escalated to the main session.

Existing skills cover parts but not this:

  • /discipline:use-your-skills finds a skill that should have fired, not one that fired and didn't fit.
  • /plugin-quality:audit audits one named component after use, not a whole session's fit.
  • /session-flow:retro codifies session learnings, not per-skill gaps routed to their owners.

Ask

A skill the owner can fire at any point (start, middle or end), for example /plugin-quality:fit-gaps or /session-flow:skill-fit. It would:

  1. Read the session's on-disk transcript and its subagents' returns. Find each place where:
    • a skill was invoked and then bypassed or overridden;
    • a coordinator re-typed the same rules into several briefs;
    • a worker stalled, or was nudged or re-briefed for the same reason more than once;
    • a permission or classifier denial forced a workaround;
    • a verifier loop was stopped by judgment;
    • the owner asked "is there a skill for this".
      At session start, with no transcript yet, it instead lists the skills that likely apply to the stated task and their known fit limits, from open issues.
  2. Attribute each gap to its owning plugin or skill, citing transcript evidence.
  3. De-duplicate against that plugin's open issues (gh issue list --search).
  4. Present a ledger of gap, owning skill, evidence, proposed change and existing issue. File the new ones only on the owner's yes, with evidence-first bodies. That fits the org's rule that no automated process opens issues.
  5. Optionally propose a new-skill candidate when no existing skill owns a recurring pattern.

Evidence

Session dba79e68-af19-4ecc-a0ce-69d8b1dbefbb, plus #6412 and #6413, which this skill would have produced.

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.