Turn pack proposals into generation pull requests, triggered by a maintainer label
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 38/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, typescript
Línea de trabajo
Read .github/ISSUE_TEMPLATE/content_pack_proposal.yml, .github/labels.json, and packages/cli/src/generate/, then review the referenced pipeline documentation and ADR. Map the issue form fields to the generator inputs and inspect how GitHub Actions handles issue events, permissions, and secrets. Done when the acceptance criteria pass, including injection safety, permission checks, successful and failed run behavior, and updated documentation.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Context
The content pack proposal form exists, and lexvm generate can produce a verified pack. Connecting them lets the community propose adventures that the project generates and reviews in the open. Every run costs API usage, so only a maintainer may start one. Needs a measured real run of lexvm generate (#40), the licensing decision (ADR 0010) and the provenance policy first.
Scope
- Extend .github/ISSUE_TEMPLATE/content_pack_proposal.yml with the inputs
lexvm generateneeds: idea, language, target minutes, pack id (kebab-case), license (SPDX) and author credit. - A new trigger label (for example
generate: approved) in .github/labels.json. - Workflow
generate-pack.ymlonissues: labeled: runs only when that label is added by a user with write or maintain permission (checked through the API, not only by label presence). - Input handling: parse the form fields with a script; issue text is passed through files or environment variables and never interpolated into shell commands; validate the pack id pattern, language and a minutes range.
- Generation:
ANTHROPIC_API_KEYfrom a protected environment, model from a repository variable; cost caps through--max-repairs,--max-tokens, a job timeout and a concurrency group of one; the trigger label is removed after the run. - Result: a branch
pack/<id>and a pull request with the pack, design/ and design/run.json; the PR body has thelexvm checksummary, token totals, the provenance and a link to the proposal; labelscontent-packandarea: content. - A comment on the proposal with the outcome. On failure: the diagnostics summary and the artifacts, and no pull request.
- Least-privilege permissions per job.
Acceptance criteria
- Adding the label as a user without write permission does nothing (tested).
- A proposal with shell metacharacters and
${{ }}in its text cannot inject commands (tested). - A successful run opens a pull request that passes CI.
- A failed run comments the diagnostics and opens no pull request.
- The token usage of each run is reported in the pull request.
- docs/authoring/pipeline.md and CONTRIBUTING.md describe the process.
References
- .github/ISSUE_TEMPLATE/content_pack_proposal.yml
- .github/labels.json
- packages/cli/src/generate/
- docs/authoring/pipeline.md
- docs/adr/0007-llm-pipeline-byo-prompt-kit-and-api-generator.md
- SECURITY.md (Scope)
- Lenguaje dominante
- TypeScript
- Estrellas
- 0
- Forks
- 0
- Merge medio
- 28 min
- PR fusionados (30 d)
- 2
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nullthrone/lexvm
-
area: web good first issue priority: low type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
nullthrone/lexvm#49 ·
-
area: infra good first issue priority: low type: chore
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
nullthrone/lexvm#41 ·
-
area: engine good first issue priority: low type: feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
nullthrone/lexvm#27 ·
-
area: web priority: low type: research
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
nullthrone/lexvm#63 ·
-
area: infra area: web priority: medium type: chore
Dificultad 5/5 Más de una semana Aptitud para principiantes 38/100
nullthrone/lexvm#62 ·
Todos los issues de nullthrone/lexvm
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
awesome-dsh-plugin/awesome-dsh-plugin#9184 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
farion1231/cc-switch#8829 ·
Los mantenedores suelen responder en 1 día
-
[core-client] Remove unused hand-maintained transport helpers after the definition-table cutoverAbiertodoc-audit enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100