Write Taiga updates in Indonesian

This commit is contained in:
2026-08-29 20:14:23 +07:00
parent 0dbccee979
commit 6693213b02
3 changed files with 4 additions and 3 deletions

View File

@@ -1,6 +1,6 @@
{
"name": "taiga-auto-sync",
"version": "0.1.0+codex.20260829130430",
"version": "0.1.0+codex.20260829131410",
"description": "Automatically tracks material IT Infra & Ops work and guards Taiga writes.",
"author": { "name": "Senkensha" },
"hooks": "./hooks/claude-codex-hooks.json"

View File

@@ -1,6 +1,6 @@
{
"name": "taiga-auto-sync",
"version": "0.1.0+codex.20260829130430",
"version": "0.1.0+codex.20260829131410",
"description": "Automatically tracks material IT Infra & Ops work and guards Taiga writes.",
"author": {
"name": "Local developer"

View File

@@ -12,4 +12,5 @@ Use this workflow automatically when the prompt requests material IT Infra & Ops
3. Find an existing matching open item before creating a new one. Reuse its local state reference when available.
4. Classify a standalone daily operation as an Issue. Use one User Story only for one outcome with two or more related Tasks; create those Tasks beneath it.
5. Every active User Story, Task, and Issue needs an owner, current sprint, one area tag, one `source:<agent>` tag, and one `repo:<name>` or `system:<name>` tag.
6. Use the Wiki template for the selected item type. Record only material `start`, `progress`, `blocked`, and verified `done` events. Never put credentials or sensitive evidence in Taiga or local state.
6. Write all Taiga-facing natural-language text in Bahasa Indonesia: titles, descriptions, comments, summaries, verification, blockers, and handoffs. Preserve code, commands, branch/PR names, repository and service names, domains, tags, statuses, and established technical terms in English.
7. Use the Wiki template for the selected item type. Record only material `start`, `progress`, `blocked`, and verified `done` events. Never put credentials or sensitive evidence in Taiga or local state.