Lesson #1455

ID

1455

Author

ai

Agent

agent-claude

Reviewed

No (unreviewed)

Source authority

75 / 100

Source

User's preferred dispatch — create Gitea issues, label with agent-X, let n8n handler dispatch

Source issue

—

Created at

2026-05-12T10:00:23.064024+00:00

Valid until

—

Deprecated at

—

Supersedes

—

Obsidian path

/root/.claude/projects/-nvmetank1-projects/memory/feedback_gitea_issue_workflow.md

Obsidian hash

920b5ddc8595f8c9419ecc9dd9d04551

Tags

claude-memory,feedback,deprecated

Content

**Rule:** EVERY project task — even single bug fixes — must land as a Gitea issue in the relevant repo BEFORE any agent dispatch. No silent in-memory todo-only work.

**Why:** User reaffirmed 2026-05-05: "die aufgaben sind aktuell nicht im gitea. merke dir bei jeder claude code session, jedes projekt immer ins repo und ein issue dazu erfassen." (initial directive 2026-05-04: "alle aufgaben ins gitea und schön brav abbarbeite und den agenten zuordnen du siehst die beispiele"). Issues give visibility, traceability, and tap into the existing n8n `03-agent-dispatch` infrastructure that handles @agent-X mentions automatically.

**How to apply:**

1. **Title** — short imperative ("fix(X): one-line").
2. **Body** structure (proven examples: ubuadmin/glug#620, #562):
   ```
   ## Goal
   <one paragraph>

   ## Steps
   1. <concrete step>
   2. ...

   ## Acceptance criteria
   - <testable bullet>
   - bin/smoke passes
   ```
3. **Labels** (combined):
   - `agent-<name>` — picks the handler. Choose by capability:
     | Task | Agent label |
     |---|---|
     | Backend / auth / pytest / small-coding | `agent-codex` |
     | Read-only review / long-context / second-opinion | `agent-gemini` (or `agent-or` for cheap review) |
     | Single-file CSS / templates | `agent-or-coder-plus` |
     | Bulk renames / mechanical refactor | `agent-qwen` |
     | Cross-cutting architecture / spec design | `agent-claude` (orchestrator) |
   - `priority-{low,medium,high}` — required by Flight Recorder (AP1 §4)
   - `status-ready` — when ready to dispatch
   - `type-{feature,bug,refactor,docs,…}`
   - Codex-specific: `package` for bundle-issues
4. **@-mention** the agent in the body so the n8n hook fires (`@agent-codex` etc.).
5. **Repo selection**: file in the repo where the work happens. Examples:
   - yoga UI bug → `ubuadmin/yoga`
   - glug framework bug → `ubuadmin/glug`
   - rag-stack governance/agent stuff → `ubuadmin/rag-stack`

**Forward-compat:** rag-stack#92 dispatcher would be the better single-entry-point. Until then, Gitea labels remain the dispatch surface.

**Monitor:** poll `gh pr list --search "label:agent-X status-in-progress"` or use Gitea API. The handler scripts log to `/var/log/glug-agent-handler.log`.

**Reference info:** orchestrator.joelduss.xyz — multi-agent docs/RAG (per user pointer 2026-05-04).