Skip to content

feat: seed-issues.sh example + GitHub-Issues-as-tickets - #3

Merged
robercano merged 1 commit into
mainfrom
feat/seed-issues-example
Jun 11, 2026
Merged

feat: seed-issues.sh example + GitHub-Issues-as-tickets#3
robercano merged 1 commit into
mainfrom
feat/seed-issues-example

Conversation

@robercano

Copy link
Copy Markdown
Owner

What

Adds an optional, generic backlog seeder and documents GitHub Issues as a first-class ticket source.

USAGE.md mentions driving the orchestrator one task at a time, but the template ships nothing to create that backlog. When adapting it to a real project, a small idempotent seeder proved very useful — generalized here.

.claude/scripts/seed-issues.sh

  • Derives module:<name> labels automatically from the modules in .claude/gates.json (so labels match the worker boundaries), plus type:feature / type:infra.
  • Idempotent: reuses existing labels, and skips any issue whose exact title already exists (safe to re-run as the backlog grows).
  • Ships a clearly-marked placeholder TICKETS section the user replaces with their real backlog (one mkissue per ticket, each scoped to one module).
  • Prereqs guarded (gh auth, node); bash -n clean.

docs/USAGE.md

  • New short "Tickets: GitHub Issues (optional)" section: how to seed, and the one-issue-at-a-time drive prompt.

Two non-overlapping files; no change to agents/workflow.

🤖 Generated with Claude Code

Ship an optional, idempotent backlog seeder: derives module:<name> labels
from gates.json modules (+ type:feature/type:infra) and bulk-creates
issues, skipping titles that already exist. The TICKETS section is a
placeholder for the user's backlog. Document GitHub Issues as a
first-class ticket source in USAGE.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@robercano
robercano merged commit e883cd0 into main Jun 11, 2026
@robercano
robercano deleted the feat/seed-issues-example branch June 11, 2026 10:52
robercano added a commit that referenced this pull request Jul 10, 2026
…ns survive (v4)

Casualty #3 of the systemd minimal-PATH finding (#107): with the RC server
launched via absolute path (v2), the server itself ran, but the SESSION
processes it forks inherit the tmux server's env — systemd's minimal PATH —
and died at spawn ('Session failed: Process exited with error', capacity
0/8, observed live). Wrap the pane command in bash -c with an explicit
PATH (claude's bin dir + system dirs, no $PATH expansion pitfalls) so the
server and every child it forks can resolve node/claude. New __CLAUDE_DIR__
placeholder substituted by arm-loop.sh. Markers v3->v4.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant