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
1.0 KiB
1.0 KiB
description, allowed-tools, model
| description | allowed-tools | model |
|---|---|---|
| Wählt das nächste ai-ready Issue und arbeitet es via /fix-issue ab. | 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 | 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).
- Rufe den Agenten
next-issueauf. Er liefert entwederISSUE=<nr>oderISSUE=NONE. ISSUE=NONE→ melde „Queue leer, keinai-ready-Issue offen" und beende ohne weitere Aktion.ISSUE=<nr>→ führe exakt den Ablauf aus.claude/commands/fix-issue.mdfü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 istfix-issue.md.