Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Turn pack proposals into generation pull requests, triggered by a maintainer label

Open
  • Is something wrong?
#50 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, typescript
Domain
ci-cd, devtools

Research direction

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.

Written by the indexing model from the issue text.

Description

area: infra area: pipeline priority: high type: feature

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 generate needs: 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.yml on issues: 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_KEY from 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 the lexvm check summary, token totals, the provenance and a link to the proposal; labels content-pack and area: 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)
Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
28m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nullthrone/lexvm

All issues in nullthrone/lexvm

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.