backlog-write
/backlog-write
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".
- Author
- mickey-ichi ↗
- Repository
- backlog-bridge ↗
- Licence
- MIT
- Last repository change
- 07.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Original author 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".
How it works
- Flow
- Writing to a customer — review mode
- Commands
- Don't
SKILL.md preview
--- 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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · mickey-ichi/backlog-bridge | 100 | MIT |
| mickey-ichi/backlog-bridge | 100 | MIT |
Database snapshot: 13.11.2026 · package version 81083a9ec366 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100backlog-query
Read issues, comments, search results and activity across MANY Backlog spaces via the backlog-bridge CLI. Use when the user pastes a Backlog link or issue key (e.g. https://acme.backlog.jp/view/ACME-123, DEV-42), asks "what's the status of this task", "find tasks assigned to X",… - 100backlog-query
Read issues, comments, search results and activity across MANY Backlog spaces via the backlog-bridge CLI. Use when the user pastes a Backlog link or issue key (e.g. https://acme.backlog.jp/view/ACME-123, DEV-42), asks "what's the status of this task", "find tasks assigned to X",… - 90Backlog Management
This skill should be used when the user asks to 'add to backlog', 'update backlog', 'check backlog', 'list backlog items', 'prioritize backlog'. Provides conventions for managing the project backlog in .s2s/BACKLOG.md. - 100comment-jira-issue
Use this skill only when the user explicitly invokes /comment-jira-issue to add, list, edit, or delete comments on a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Subcommands: add (post a new… - 84backlog
Manage the structured product backlog — pick what to work on next, add/find/list/update items, and migrate legacy items. Use when the user wants to triage, file, or choose backlog work, or says /prawduct:backlog. - 95backlog
Read, work, and maintain a repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task…