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

[External Plugin]: oddyssey

Abierto
#3,130 4 comentarios 0 reacciones 0 asignados Ver en GitHub

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
github, grafana, javascript

Línea de trabajo

Revisa using-system/oddyssey en marketplace/oddyssey, referencia v1.12.1 y commit 407c8e2248c12e112098861a9c577027708ba031. Empieza por eng/external-plugin-quality-gates.mjs y scripts/build-marketplace.sh; después, inspecciona el plugin.json de la raíz y la estructura de la extensión de Copilot. Se considera terminado cuando las puertas de calidad y la prueba de humo de instalación pasan, y la estructura del plugin enviado coincide con los requisitos indicados del marketplace.

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

Descripción

external-plugin ready-for-review
Plugin name

oddyssey

Short description

Observability-Driven Development for coding agents: an OpenTelemetry instrumentation expert, a run-observation agent that measures a service through its telemetry on a local Grafana stack or a remote backend (Grafana, Datadog, Dynatrace, Azure Monitor, CloudWatch), a verification pass that replays a stored run, k6 benchmark authoring, and a committed .odd/ memory that carries the loop across runs.

GitHub repository

using-system/oddyssey

Plugin path inside the repository

marketplace/oddyssey

Ref to review

v1.12.1

Commit SHA to review

407c8e2248c12e112098861a9c577027708ba031

Version

1.12.1

License identifier

MIT

Author name

using-system

Author URL

https://github.com/using-system

Homepage URL

https://github.com/using-system/oddyssey#readme

Keywords

observability, opentelemetry, grafana, k6, mcp, ai-agents, developer-tools, performance, telemetry, load-testing

Additional notes for reviewers

Resubmission of #3089 (closed by the submitter after requires-submitter-fixes): the install smoke test and version match failed there because the manifest only existed under .claude-plugin/plugin.json. Since v1.12.0 the build also emits plugin.json at the plugin root in the Agent Plugins v1.0.0 shape ($schema, name, version, description, author, homepage, repository, license, keywords), next to the Claude Code one.

v1.12.1 addresses the review on this issue: the Copilot components now ship under the com.github.copilot/ extension namespace (agents/, commands/, hooks/hooks.json with ${PLUGIN_ROOT} paths and the hook scripts) and the MCP server in a root mcp.json in the spec's shape, beside the Claude Code layout. Verified with Copilot CLI 1.0.83 (--plugin-dir, debug log): 4 agents, the 7 commands translated into skills, the 9 skills, the hooks and the MCP server all load with no warning.

All gates were replayed on this tag/SHA with eng/external-plugin-quality-gates.mjs before the previous edit; on v1.12.1, vally lint (runLint({rootPath})) passes with 9 skills and the install smoke test (ephemeral marketplace, fresh HOME, Copilot CLI 1.0.83) installs the plugin with plugin.json at the installed root at version 1.12.1. The plugin tree is generated from an APM package on every release (scripts/build-marketplace.sh) and is also installable today through copilot plugin marketplace add using-system/oddyssey.

Submission checklist
  • The plugin lives in a public GitHub repository.
  • The ref and/or sha I provided is immutable (release tag and/or full 40-character commit SHA), not a branch.
  • This submission follows this repository's contribution, security, and responsible AI policies.
  • This plugin is not already listed in the Awesome Copilot marketplace.
Lenguaje dominante
JavaScript
Estrellas
39.2k
Forks
5k
Merge medio
1 d 17 h
PR fusionados (30 d)
117

Guía de contribución

Abrir la guía de contribución

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 github/awesome-copilot

Todos los issues de github/awesome-copilot

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.