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

feat(harness-ops): on-demand plugin landscape audit (stale plugins and modern alternatives)

Abierto
#6,461 0 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
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
github, shell

Línea de trabajo

Start from harness-ops ownership of plugins sync (#6309) and the existing manual pieces named in the issue: discipline:recheck-against-upstream, docs/upstream/, and dometrain:sync. Done means an on-demand skill that ages installed plugins and marketplaces via batched gh api, groups overlaps, records alternatives with evidence, and files adopt/adapt/drop issues—without scheduling or changing chezmoi apply.

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

Descripción

Problem

Nothing tells the owner when an installed plugin or marketplace has gone stale, or when a better alternative has appeared (e.g. Playwright vs Vercel's agent-browser CLI). On 2026-10-05 a one-off script found:

  • 16 stale third-party plugins (no upstream update in 60+ days)
  • 2 stale marketplaces (karpathy-skills 04-20, openai-codex 07-08)

The existing pieces are all manual or single-purpose: discipline:recheck-against-upstream, docs/upstream/, dometrain:sync.

Proposed: on-demand skill (no schedule for now)

  1. Ages: for every installed plugin and known marketplace, the last upstream commit touching the plugin's source path, via batched gh api. Flag 60+ days, archived, moved, or a source path that no longer exists.
  2. Overlaps: group plugins that do the same job, across marketplaces including melodic-software, and name the one to keep.
  3. Alternatives: for each stale or losing plugin, research current alternatives, official docs first, and record the evidence.
  4. Issues: file one issue per adopt / adapt / drop decision here. Adopt-and-adapt policy: keep an adapted melodic version of an upstream skill until upstream meets Anthropic's skill guidance (frontmatter, description length, body size, progressive disclosure), then drop ours.

Boundary:

  • This repo decides what to adopt.
  • The owner's dotfiles decide what's installed and on per user and machine, and change only after a decision here.
  • chezmoi apply keeps things current (marketplace autoUpdate, tool upgrades, fixing renamed or broken sources). It does no landscape research.

Ownership: harness-ops, which already owns plugins sync (see #6309).

🤖 Generated with Claude Code

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.