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

Writing pipeline: editor should start from a topic, not a single note

Abierto
  • ¿Algo no está bien?
#20 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
43/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
developer-experience

Línea de trabajo

The parked feat/writing-pipeline branch contains the harvest and editor skills, their README, and go-help entries. Start by reading those files and trying the workflow on a real piece, as the issue requests. Update the editor, note format, harvest ending, README, and /editor help row to match the six changes; completion means the workflow starts from a topic or draft and all six changes are reflected.

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

Descripción

enhancement

Parked work on branch feat/writing-pipeline: the harvest and editor skills, plus their README and go-help entries. Nothing is merged.

Problem

Harvest works: it saves one dated note per moment to the writing inbox. The editor is the weak part. Give it one note and its "find the point" step just restates the note's claim. Most notes are fragments, and a real post draws on several of them.

Pick this up when

You are writing a real piece and want to pull inbox notes into it. Try the changes below on that piece. Don't build them before then.

Changes

  1. Editor starts from a topic or a draft, not from a note. Input is a topic ("running agents unattended"), a draft you've started, or a brain dump. The editor searches the inbox, lists the notes that fit, and you pick the ones to use. Then it finds the point across them and builds the draft from your quotes. The interview and editing passes stay.
  2. Drop Fits from the note format. It guesses the final form before anyone knows what the piece is.
  3. Add free-form Tags to notes (e.g. autonomy, testing, skill-design). Harvest reuses tags already in the inbox before it makes new ones. Don't fix a tag list up front.
  4. Add a Used in: <draft slug> line when a note goes into a draft, so later searches can rank unused notes first.
  5. Change harvest's last step: stop offering /editor on the strongest note. Report which tags gained notes.
  6. Update the README and the go-help row for /editor to say it starts from a topic or draft.

Later, maybe

  • Suggest pieces from tag clusters: e.g. when three or more unused notes share a tag. Only worth building once the inbox is large enough that you lose track of it.

Considered and dropped

  • A separate /pitch skill between harvest and editor that groups notes into piece ideas. Starting from a topic covers the main case with one skill fewer. Cluster suggestions (above) cover the rest if it ever matters.
Lenguaje dominante
TypeScript
Estrellas
0
Forks
0
Merge medio
3 h 33 min
PR fusionados (30 d)
13

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: 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 gregogun/gstack

Todos los issues de gregogun/gstack

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.