backlog-write
/backlog-write
Dodaje komentarze i zmienia status, osobę lub termin zgłoszenia w połączonych przestrzeniach Backlog, zawsze z podglądem przed zapisem.
- Autor
- mickey-ichi ↗
- Repozytorium
- backlog-bridge ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 07.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Dodaje komentarze i zmienia status, osobę lub termin zgłoszenia w połączonych przestrzeniach Backlog, zawsze z podglądem przed zapisem.
Wyzwalacze z opisu
Oryginalny opis (EN)
Comment on, change status/assignee/due date of, or edit the summary of an issue on any connected Backlog space (internal or customer) via backlog-bridge, always previewing before writing. Use when the user says "comment on the customer ticket", "move this task to Resolved", "assign it to X", "change the due date", "post the translation to Backlog".
Jak działa
- Flow
- Writing to a customer — review mode
- Commands
- Don't
Podgląd SKILL.md
--- name: backlog-write description: Comment on, change status/assignee/due date of, or edit the summary of an issue on any connected Backlog space (internal or customer) via backlog-bridge, always previewing before writing. Use when the user says "comment on the customer ticket", "move this task to Resolved", "assign it to X", "change the due date", "post the translation to Backlog". --- # Write to Backlog across spaces Every write command of `backlog-bridge` is **DRY by default**: it prints the request and stops. Add `--yes` only after showing the preview to the user and getting a clear yes. ## Flow 1. Read the current state: `backlog-bridge issue <ref>` (see skill `backlog-query` for `<ref>`). 2. Run the write **without** `--yes` → show the user the space, issue key and the exact content. 3. If the space is a **customer's** (not the user's own internal space) → follow **Writing to a customer** below. Ask again before every send, even if the user approved a similar write earlier. 4. Run the same command again with `--yes`. ## Writing to a customer — review mode How the user reviews depends on whether they read the customer's language. Check it first: ```bash backlog-bridge home # line "review : …" ``` `BACKLOG_BRIDGE_REVIEW` in the user's own `.env` (with `BACKLOG_BRIDGE_LANG`, default `vi`, and `BACKLOG_BRIDGE_CUSTOMER_LANG`, default `ja`): **`bilingual` — the user reads the customer's language** 1. Draft the reply in the customer's language, polite business tone. 2. Show it for review **bilingually**: the customer-language text, followed by a faithful translation into the user's language under a `【VN】` (or matching) heading — so they can check meaning and wording side by side. 3. Revise until the user approves. 4. Send **only the customer-language text** (never the translation): write it to a file, `backlog-bridge comment <ref> --file=…`, check the dry run, then `--yes`. **`translate` — the user does not read the customer's language** 1. Draft the reply **in the user's language only** and have them review and approve that version. Do not ask them to review text they can't read. 2. Translate the approved text into the customer's language faithfully — no added promises, dates or details. 3. Send it right away: dry run, then `--yes` without asking again (the approval of step 1 covers this send). Then tell the user what was sent, with the translation of the final text back into their language. **Not set** (`review : (not set …)`) → ask the user once which case applies, use it for this write, and tell them the line to add to their `.env` (`BACKLOG_BRIDGE_REVIEW=bilingual` or `=translate`). Never edit `.env` yourself. The same applies to other customer-facing text: issue summaries/descriptions written with `backlog-bridge update` or `backlog-bridge api`. ## Commands ```bash # comment — put long / multi-line text in a file first backlog-bridge comment <ref> --file=reply.txt backlog-bridge comment internal DEV-42 --text="Fixed, please re-test" # update — status/assignee by NAME (resolved to ids in the project); other fields go straight to API v2 backlog-bridge update <ref> status=Resolved backlog-bridge update <ref> assignee=An dueDate=2026-10-30 backlog-bridge update <ref> summary="ACME-123 [impl] ..." # any other endpoint (wiki, links, …) backlog-bridge api <space> POST /wikis projectId=12345 name="Release note" content="..." ``` Append `--yes` to actually send. `--file` refuses `.env*` files, `state/` directories and the config file (also through symlinks) — secrets are never posted. ## Don't - Don't create or delete issues in bulk by hand — mirroring is `backlog-bridge sync` (skill `backlog-sync`). - Don't close (`Closed`) a customer's issue — the customer closes it; go up to `Resolved` at most. - Don't delete issues or comments (API `DELETE`) unless the user names that exact item.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · mickey-ichi/backlog-bridge | 100 | MIT |
| mickey-ichi/backlog-bridge | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 81083a9ec366 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100backlog-query
Odczytuje zgłoszenia, komentarze i aktywność z wielu przestrzeni Backlog przez CLI backlog-bridge, np. po wklejonym linku. - 100backlog-query
Odczytuje zgłoszenia, komentarze i aktywność z wielu przestrzeni Backlog przez CLI backlog-bridge, np. po wklejonym linku. - 90Backlog Management
Prowadzi backlog projektu w pliku BACKLOG.md: dodaje pozycje, aktualizuje je, sprawdza i ustala priorytety. - 100comment-jira-issue
Dodaje, wyświetla, edytuje i usuwa komentarze do zgłoszeń Jira, wyłącznie na wyraźne wywołanie /comment-jira-issue, z podglądem przed zapisem. - 84backlog
Prowadzi ustrukturyzowany backlog produktu: wybiera zadania, dodaje, szuka, aktualizuje i migruje pozycje. - 95backlog
Prowadzi listę odłożonych zadań w katalogu docs/backlog, po jednym pliku na pozycję: czyta, dopisuje i porządkuje.