Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#1,404 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@AbirAbbas ya está trabajando en esto.

Desde el 23/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.
Lenguaje dominante
Go
Estrellas
115
Forks
14
Merge medio
9 h 35 min
PR fusionados (30 d)
752

Preparar el entorno

Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Agent-Field/CodeAF

Todos los issues de Agent-Field/CodeAF

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.