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

test(source-control): add eval cases for babysit-prs, babysit-loop and setup

Abierto
#7,148 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
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, shell

Línea de trabajo

Read the three skills’ SKILL.md files, the eval cases under plugins/source-control/evals/, the skill criteria at plugins/playbooks/skills/skill-authoring/reference/skill-criteria.md, and the gh/PR fixture work in #6997. Design at least one case for each skill with /evals:design, validate with /evals:validate, then run each case paid with and without the skill. Done when all cases load, avoid real GitHub, and record their with/without results.

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

Descripción

needs-triage priority: medium

Observed

plugins/source-control/evals/ has cases for commit, pull-request, resolve-conflicts and worktree, and none for three of its skills:

  • babysit-prs
  • babysit-loop
  • setup

(check is a read-only prerequisites check and is out of scope here.) Changes to these three skills ship with no behavioral evidence, and the skill criteria (plugins/playbooks/skills/skill-authoring/reference/skill-criteria.md) require eval evidence of no loss before a cut to a skill body, which these skills cannot produce today.

Fix wanted

Design at least one case per skill with /evals:design, covering the behavior each SKILL.md treats as most important, for example:

  • babysit-prs: the safe default tier never resolves threads or merges.
  • babysit-loop: a do-not-merge label or a body hold stops the merge.
  • setup: writes only what the user confirmed.

Both babysit skills read GitHub state, so they need the gh/PR fixture from #6997; build on that rather than calling real GitHub. Validate statically (/evals:validate), then run each case paid with/without and record the delta.

Acceptance: each skill has at least one case that loads, never touches real GitHub, and shows a with/without result.

Depends on: #6997

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.