TypeSpec remediation skill for Java

Aperta
  • Qualcosa non va?
#51,237 1 commento 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
devtools

Direzione di ricerca

Read the shared remediation contract in Azure/azure-rest-api-specs#48168 and the dependent Java review skill issue #51221 first; the skill path and maintainer names are still placeholders. Build .github/skills/<remediation-skill-name>/SKILL.md to consume the supplied review result and context, map every finding exactly once, and emit the versioned result without edits. Done means reviewed historical examples and CI evals cover supported planes, uncertain cases route to manual-investigation, and maintainers and CODEOWNERS are confirmed.

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

Descrizione

needs-triage

Parent: https://github.com/Azure/azure-rest-api-specs/issues/48167
Repository: Azure/azure-sdk-for-java
Depends on: #51221 (generated SDK review skill)

Language-team ownership

  • Language owner completing this issue:
  • Remediation skill maintainers:
  • CODEOWNERS paths or team: <paths/team>

Summary

Author and maintain a TypeSpec remediation skill that takes the findings from the Java review skill and maps each one to where the spec author (or SDK team) should fix it.

This skill consumes the review skill's output, so it depends on #51221. The initial phase is guidance only. The pipeline never edits the spec PR or the SDK repo.

Shared skill contract

The central invocation, input, output, and trusted-validation contracts are defined in Azure/azure-rest-api-specs#48168.

The language team owns the skill's internal design, rules, supporting tools, and methodology. Central integration requires only that the skill satisfies the shared remediation contract within the provided read-only execution environment.

Deliverable: TypeSpec remediation skill

Location: .github/skills/<remediation-skill-name>/SKILL.md

  • Accepts the immutable review result and typespec-review-context.json supplied by the central workflow.
  • Returns the versioned TypeSpec remediation result defined in Azure/azure-rest-api-specs#48168.
  • Maps every review finding exactly once without adding, removing, or rewriting findings.
  • Produces guidance only and does not edit or regenerate code.

Evidence and evals

  • A small set of historical findings with known accepted fixes (TypeSpec, client.tsp, SDK-repository customization, or manual).
  • Examples for every plane supported by the review skill, or a documented subset with gaps and follow-up ownership.
  • Evals confirm that each finding is routed to the expected target and that uncertain cases go to manual-investigation.
  • Evals run in CI in this repository.
  • Evidence links and expected outcomes are reviewed by the language-team maintainers.

Pilot packages

Uses the pilot packages selected in #51221.

Maintenance

  • Named maintainers for the remediation skill (added to CODEOWNERS for the skill folder).
  • Process for updating the skill as client.tsp decorators, emitter options, or SDK customization mechanisms change.

Completion criteria

  • The skill path is final and owned by the language team.
  • The skill satisfies the shared remediation contract in Azure/azure-rest-api-specs#48168.
  • Supported planes match the review skill or are a documented subset.
  • Historical examples and evals are reviewed and passing.
  • Maintainers and CODEOWNERS are confirmed.
  • The language team confirms the skill is ready for central remediation integration.

Out of scope

Generated SDK review (tracked in #51221), central workflow implementation, PR publication, blocking checks, applying fixes, and regeneration.

Lingua principale
Java
Stelle
2.6k
Fork
2.2k
Merge medio
1g 17h
PR unite (30g)
259

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

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 Azure/azure-sdk-for-java

Tutte le issue di Azure/azure-sdk-for-java

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.