Pit Friedrich
ed399cec6c
fix-issue/next-issue had unresolved placeholders (<dein Testkommando>, <owner>/<repo>) and no explicit branch-creation step, so a run that skipped the CLAUDE.md convention could commit straight to main. Adds a CI-gate before setting ai-review (actions_run_read against the existing .gitea/workflows/ci.yml) instead of trusting self-reported test results, plus a /work-queue command to chain next-issue -> fix-issue. dev.bundle is Vaadin-regenerated and was tracked+dirty, so every autofix commit would have swept in unrelated binary diffs. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0114SVTvBYjLBt3TTxhzJttd
24 lines
1.0 KiB
Markdown
24 lines
1.0 KiB
Markdown
---
|
||
description: Wählt das nächste ai-ready Issue und arbeitet es via /fix-issue ab.
|
||
allowed-tools: >
|
||
Bash, Edit, Read, Write, Grep, Glob,
|
||
mcp__gitea__list_issues, mcp__gitea__issue_read, mcp__gitea__issue_write,
|
||
mcp__gitea__label_read,
|
||
mcp__gitea__pull_request_write, mcp__gitea__pull_request_read,
|
||
mcp__gitea__actions_run_read
|
||
model: opus
|
||
---
|
||
Arbeitet genau EIN Issue aus der Autofix-Warteschlange ab. Kein Loop
|
||
innerhalb dieses Commands — für wiederholte Läufe die `/loop`-Skill nutzen
|
||
(z.B. `/loop 30m /work-queue`).
|
||
|
||
1. Rufe den Agenten `next-issue` auf. Er liefert entweder `ISSUE=<nr>`
|
||
oder `ISSUE=NONE`.
|
||
2. `ISSUE=NONE` → melde „Queue leer, kein `ai-ready`-Issue offen" und
|
||
beende ohne weitere Aktion.
|
||
3. `ISSUE=<nr>` → führe exakt den Ablauf aus `.claude/commands/fix-issue.md`
|
||
für Issue `<nr>` aus (Schritte 0–10 dort, unverändert, inklusive
|
||
Label-Regeln, Branch-Schema, Testkommando und CI-Gate). Diese Datei
|
||
beschreibt den Ablauf nicht erneut — Quelle der Wahrheit ist
|
||
`fix-issue.md`.
|