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

Export as skill, and `prompuff export --format`

Abierto
  • ¿Algo no está bien?
#39 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
cli, csharp, markdown, yaml
Área
cli, developer-experience, documentation, full-stack, testing

Línea de trabajo

Read MarkdownTransferService.cs and IPromptTransferService for existing export behavior, then PromptTemplateService.ExtractVariables and CliApp.cs for variable handling and command registration. Check each target tool’s current format documentation before implementing the four exports. Done means each format works with no, one, and several variables, the listed tool checks pass, and the user guide and CLI help describe the feature.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Prompts are turning into skills. Codex deprecated custom prompts for skills, Claude Code merged commands into skills, and Cursor, VS Code and Devin each ship a way to move over (market research, 2026-10-10). Export as skill gives a prompt to those tools in the form they read now.

What to do

  • Export as skill for a prompt or a selection, with a choice of format:
    • an Agent Skills folder, <name>/SKILL.md, which Codex, Cursor and Copilot CLI read from ~/.agents/skills
    • a Claude Code skill
    • a Copilot .prompt.md
    • a Gemini CLI .toml command
  • {{variables}} become each tool's own arguments where it has them: $name in Claude Code, ${input:name} in Copilot and {{args}} in Gemini. Where a format has none, the skill gets a short list of its inputs.
  • prompuff export --format <format> <prompt>… does the same from the command line.
  • Check each format against its tool's current docs before building it, and link the docs in the pull request. These formats change quickly.
  • Remembered values stay out of exports.

Where to look

  • src/Prompuff.Infrastructure/ImportExport/MarkdownTransferService.cs and IPromptTransferService
  • src/Prompuff.Application/Services/PromptTemplateService.cs: ExtractVariables
  • src/Prompuff.Cli/CliApp.cs: adding a command (Usage, the command list, the switch, a handler)

Done when

  • A favorite exported each way runs in its tool: as a skill in Claude Code and Codex, a prompt file in Copilot and a command in Gemini CLI, each checked by hand once.
  • Tests cover each format with no variables, with one, and with several.
  • docs/user-guide.md and the CLI's help describe it.
Lenguaje dominante
C#
Estrellas
0
Forks
1
Merge medio
1 h 21 min
PR fusionados (30 d)
22

Preparar el entorno

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 hazeliscoding/prompuff

Todos los issues de hazeliscoding/prompuff

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.