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

Skills 2/6: /<skill-name> invokes a skill by its own name

Aperta
  • Qualcosa non va?
#1,404 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@AbirAbbas ci sta già lavorando.

Dal 23/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

area:chat feature

Step 2 of #1277. It lands in the single pull request for #1277 (branch feat/1277-skills).

What

  • Every discovered skill is a slash command by its own name. Skills become a second, dynamic source of commands beside the fixed table in internal/tui3/commands.go. The picker under the draft ranks them among codeaf's own commands, and the dispatcher consults them after the fixed table.
  • /<skill-name> [words] sends the skill's body plus your words as the turn. The transcript shows the line you typed, not the body. If the skill is already in this conversation's context, only your words are sent, and the skill is named as already loaded.
  • codeaf's own commands always win a name. A skill named like one of them is reached with /skill use <name> [words], which does exactly what its own slash would have done.
  • A shadowed or skipped skill is not a command.

Acceptance, end to end

Real binary in tmux, with a fixture skill pdf-processing in ~/.agents/skills and a stub model that records its requests:

  • Typing /pdf shows pdf-processing in the picker, with its description.
  • /pdf-processing extract the tables draws that exact line in the transcript. The model's request carries the SKILL.md body and extract the tables.
  • Sending /pdf-processing again in the same conversation sends only again.
  • A fixture skill named help is not reachable as /help (codeaf's help opens). /skill use help hi sends that skill's body.
  • The manual answers "how do I use a skill?" and names /skill. The command-table gate passes.
Lingua principale
Go
Stelle
115
Fork
14
Merge medio
9h 35m
PR unite (30g)
752

Preparare l'ambiente

Non abbiamo ancora controllato i file di configurazione di questo progetto. Parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 Agent-Field/CodeAF

Tutte le issue di Agent-Field/CodeAF

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.