refactor(framework): apply the new skill template to every skill

Aperta
#1,164 0 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
45/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript

Direzione di ricerca

Read the new skill template and generator validation from the work described in #1092, then compare skills under plugins/ with the already updated plan, implement, assert, review and brainstorm skills. Rework remaining skills plugin by plugin while preserving their behavior and action contracts. Done means every skill follows the template or explains why it does not, passes generator validation, and passes its own ## Test.

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

Descrizione

Problem

The skill generator is being reworked in #1092: a lean flow with action paths, no repeated routing, and an end-to-end trial after validation. Only some skills follow that shape today. The lean pass already ran on plan, implement, assert, review and brainstorm, and is open for project memory (#1141). The other skills keep the old shape, so a model reads a different structure from one skill to the next.

Scope

  • Apply the new skill template to every skill that does not follow it yet, plugin by plugin.
  • Leave 10-learn and the generate skills to #1186 and #1178: they ship first, the rest follows.
  • Keep each skill's behavior and its action contracts unchanged.
  • Run the validation the generator provides on each reworked skill.

Acceptance criteria

  • Every skill under plugins/ follows the new template, or states why it does not.
  • Each reworked skill passes the generator's validation.
  • Behavior is unchanged: each skill's own ## Test still passes.

Depends on

#1179, #1178 and #1186 done.

Lingua principale
TypeScript
Stelle
481
Fork
45
Merge medio
1g 13h
PR unite (30g)
91

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 ai-driven-dev/framework

Tutte le issue di ai-driven-dev/framework

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.