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
13 lines
524 B
Markdown
13 lines
524 B
Markdown
---
|
|
name: next-issue
|
|
description: Wählt das nächste zu bearbeitende Gitea-Issue und gibt nur die Kerndaten zurück.
|
|
tools: mcp__gitea__list_issues, mcp__gitea__issue_read
|
|
model: haiku
|
|
---
|
|
Finde das nächste offene Issue im Repo pitfriedrich/chart-app mit Label `ai-ready`
|
|
und NICHT mit Label `ai-wip` oder `ai-blocked`.
|
|
Priorisiere nach `prio/high` > `prio/medium` > `prio/low`, dann nach ältestem.
|
|
|
|
Gib AUSSCHLIESSLICH eine Zeile aus, sonst nichts:
|
|
- Wenn eins gefunden: `ISSUE=<nummer>`
|
|
- Wenn keins offen: `ISSUE=NONE` |