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

Offen
#1,164 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Refactoring
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
481
Forks
45
Ø Merge
1 T. 13 Std.
Gemergte PRs (30 T.)
91

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ai-driven-dev/framework

Alle Issues in ai-driven-dev/framework

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.