WapplerSystems/t3bootstrap-upgrade-skills
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

redmine skill 1.1: keine Icons, noch kuerzere Notizen

Browse Source 
Zwei Ergaenzungen zu den Posting-Regeln: keine Icons, Emoji oder
dekorativen Symbole im Ticket-Text, und als Norm zwei bis drei Saetze
ohne Commit-Hashes, Dateinamen oder Messwerte. Der Kunde hat nicht
gefragt, wie etwas geloest wurde, sondern ob.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
melnicenko
2026-08-06 13:48:45 +02:00
co-authored by Claude Opus 5
parent 52df6752d9
commit 3a20af6208
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
redmine-issue-workflow/SKILL.md
+5 -1
View File
@@ -3,7 +3,7 @@ name: redmine-issue-workflow
description: "Read and update issues on a self-hosted Redmine via its REST API from the CLI — list/read tickets, add notes, change status, edit an existing journal note in place, and download attachments. Use when a project tracks its work/bugs in Redmine and you need to look up 'the next fixes', check a ticket's details, mark work done, or maintain a collection ('Sammelticket') ticket. Covers: API-key auth via header (never inline the secret), the issues/journals/attachments endpoints, Textile (NOT Markdown) formatting, localized statuses, and the posting-style rules (keep customer-visible notes minimal — strike through or 'erledigt', don't write the bug's cause; don't post unless asked)." description: "Read and update issues on a self-hosted Redmine via its REST API from the CLI — list/read tickets, add notes, change status, edit an existing journal note in place, and download attachments. Use when a project tracks its work/bugs in Redmine and you need to look up 'the next fixes', check a ticket's details, mark work done, or maintain a collection ('Sammelticket') ticket. Covers: API-key auth via header (never inline the secret), the issues/journals/attachments endpoints, Textile (NOT Markdown) formatting, localized statuses, and the posting-style rules (keep customer-visible notes minimal — strike through or 'erledigt', don't write the bug's cause; don't post unless asked)."
metadata: metadata:
author: Wappler author: Wappler
version: "1.0" version: "1.1"
--- ---
# Redmine issue workflow (REST API, CLI) # Redmine issue workflow (REST API, CLI)
@@ -58,6 +58,10 @@ Redmine renders **Textile** by default. Consequences:
- **Keep customer-visible notes minimal. Do NOT write out the bug's cause / technical explanation** in the - **Keep customer-visible notes minimal. Do NOT write out the bug's cause / technical explanation** in the
ticket. To mark something done, **strike the item through** (`-…-`) or just write **"erledigt"** beside ticket. To mark something done, **strike the item through** (`-…-`) or just write **"erledigt"** beside
it, where appropriate. The detailed root-cause/fix belongs in your own notes/memory, not the ticket. it, where appropriate. The detailed root-cause/fix belongs in your own notes/memory, not the ticket.
Two or three sentences is the norm: what is done, where to check it. No commit hashes, no file names,
no before/after measurements — the customer did not ask how, only whether.
- **No icons, emoji or decorative symbols in ticket text** (no ✅/✔/→/⚠, no bullets made of glyphs).
Plain sentences, plus Textile markup where it carries meaning (strike-through, bold). Team rule.
- Before posting a status change, prefer to draft the (short, German if the project is German) note and - Before posting a status change, prefer to draft the (short, German if the project is German) note and
confirm the target status with the user. confirm the target status with the user.