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

Aberta
#1,164 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Refatoração
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
481
Forks
45
Merge médio
1d 13h
PRs com merge (30d)
91

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de ai-driven-dev/framework

Todas as issues de ai-driven-dev/framework

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.