Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[External Plugin]: oddyssey

Aperta
  • Qualcosa non va?
#3,130 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, grafana, javascript
Ambito
devtools, observability, tooling

Direzione di ricerca

Esamina using-system/oddyssey in marketplace/oddyssey, riferimento v1.12.1 e commit 407c8e2248c12e112098861a9c577027708ba031. Inizia da eng/external-plugin-quality-gates.mjs e scripts/build-marketplace.sh, quindi ispeziona il plugin.json nella root e la struttura dell’estensione Copilot. Il lavoro è completo quando i quality gate e lo smoke test di installazione hanno esito positivo e la struttura del plugin inviato corrisponde ai requisiti del marketplace indicati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
JavaScript
Stelle
39.2k
Fork
5k
Merge medio
1g 15h
PR unite (30g)
99

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/awesome-copilot

Tutte le issue di github/awesome-copilot

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.