Bilingual command descriptions (EN/RU)

.gitignore

@@ -13,3 +13,4 @@ coverage/
 __pycache__/
 opencode-plugin-template/
 opencode-docs-*/
+package-lock.json

src/command/sync-enable-secrets.md

@@ -1,7 +1,14 @@
 ---
-description: Enable secrets sync (private repo required)
+description: Enable secrets sync / Включить синхронизацию секретов (требуется приватный репозиторий)
 ---
 
-Use the opencode_sync tool with command "enable-secrets".
-If the user supplies extra secret paths, pass them via extraSecretPaths.
-If they want MCP secrets committed in a private repo, pass includeMcpSecrets: true.
+You MUST call the `opencode_sync` tool with `command="enable-secrets"`.
+Do not answer with plain text only.
+
+Argument handling:
+- If the user supplies extra secret paths, pass them via `extraSecretPaths`.
+- If they want MCP secrets committed in a private repo, pass `includeMcpSecrets: true`.
+
+Reminder:
+- Enabling secrets requires the sync repo to be private — the tool will enforce this.
+- Secrets are synced via a configured backend (e.g., 1Password), not stored in git directly.

src/command/sync-init.md

@@ -1,5 +1,5 @@
 ---
-description: Initialize opencode-synced configuration
+description: Initialize opencode-synced configuration / Инициализировать конфигурацию синхронизации
 ---
 
 You MUST call the `opencode_sync` tool with `command="init"`.

src/command/sync-link.md

@@ -1,5 +1,5 @@
 ---
-description: Link this computer to an existing sync repo
+description: Link to an existing sync repo / Привязать компьютер к существующему репозиторию синхронизации
 ---
 
 You MUST call the `opencode_sync` tool with `command="link"`.

src/command/sync-pull.md

@@ -1,6 +1,10 @@
 ---
-description: Pull and apply synced opencode config
+description: Pull and apply synced config / Загрузить и применить синхронизированную конфигурацию
 ---
 
-Use the opencode_sync tool with command "pull".
-If updates are applied, remind the user to restart opencode.
+You MUST call the `opencode_sync` tool with `command="pull"`.
+Do not answer with plain text only.
+
+Reminder:
+- Pull applies remote config to local — after a successful pull, tell the user to restart opencode.
+- If the local repo has uncommitted changes, pull will fail — suggest /sync-resolve first.

src/command/sync-push.md

@@ -1,5 +1,10 @@
+---
+description: Push local config / Отправить локальную конфигурацию
 ---
-description: Push local opencode config to the sync repo
----
 
-Use the opencode_sync tool with command "push".
+You MUST call the `opencode_sync` tool with `command="push"`.
+Do not answer with plain text only.
+
+Reminder:
+- The tool will auto-commit and push local changes to the sync repo.
+- If there are uncommitted changes in the local repo, the push may fail — suggest /sync-resolve.

src/command/sync-resolve.md

@@ -1,5 +1,11 @@
 ---
-description: Resolve uncommitted changes in sync repo
+description: Resolve uncommitted changes / Разрешить незакоммиченные изменения в репозитории
 ---
 
-Use the opencode_sync tool with command "resolve" to automatically resolve uncommitted changes in the local sync repository using AI.
+You MUST call the `opencode_sync` tool with `command="resolve"`.
+Do not answer with plain text only.
+
+Behavior:
+- The tool analyzes uncommitted changes using AI and decides whether to commit or discard them.
+- After resolution, the user can retry the failed command.
+- If AI analysis is not available, the tool falls back to manual resolution instructions.

src/command/sync-secrets-pull.md

@@ -1,5 +1,10 @@
 ---
-description: Pull secrets from the configured backend
+description: Pull secrets from backend / Загрузить секреты из настроенного бэкенда
 ---
 
-Use the opencode_sync tool with command "secrets-pull".
+You MUST call the `opencode_sync` tool with `command="secrets-pull"`.
+Do not answer with plain text only.
+
+Behavior:
+- Pulls secrets from the configured backend (e.g., 1Password) and applies them locally.
+- Requires a secrets backend to be configured.

src/command/sync-secrets-push.md

@@ -1,5 +1,10 @@
 ---
-description: Push secrets to the configured backend
+description: Push secrets to backend / Отправить секреты в настроенный бэкенд
 ---
 
-Use the opencode_sync tool with command "secrets-push".
+You MUST call the `opencode_sync` tool with `command="secrets-push"`.
+Do not answer with plain text only.
+
+Behavior:
+- Pushes secrets to the configured backend (e.g., 1Password).
+- Requires a secrets backend to be configured.

src/command/sync-secrets-status.md

@@ -1,5 +1,10 @@
 ---
-description: Show secrets backend status
+description: Show secrets backend status / Показать статус бэкенда секретов
 ---
 
-Use the opencode_sync tool with command "secrets-status".
+You MUST call the `opencode_sync` tool with `command="secrets-status"`.
+Do not answer with plain text only.
+
+Behavior:
+- Shows the current status of the secrets backend (e.g., last sync, backend type).
+- Requires a secrets backend to be configured.

src/command/sync-sessions-backend.md

@@ -1,8 +1,9 @@
 ---
-description: Switch session sync backend between git and turso
+description: Switch session sync backend (git/turso) / Переключить бэкенд синхронизации сессий
 ---
 
 You MUST call the `opencode_sync` tool with `command="sessions-backend"`.
+Do not answer with plain text only.
 
 Argument handling:
 - `$ARGUMENTS` must be either `git` or `turso`.

src/command/sync-sessions-cleanup-git.md

@@ -1,7 +1,10 @@
 ---
-description: Remove deprecated git session artifacts after Turso migration
+description: Remove deprecated git session artifacts / Удалить устаревшие git-артефакты сессий
 ---
 
 You MUST call the `opencode_sync` tool with `command="sessions-cleanup-git"`.
+Do not answer with plain text only.
 
-Use this only after sessions are running on Turso and the user confirms fallback artifacts are no longer needed.
+Reminder:
+- Use this only after sessions are running on Turso and the user confirms fallback artifacts are no longer needed.
+- This removes data/sessions/*.json and data/opencode.db from the sync repo.

src/command/sync-sessions-migrate-turso.md

@@ -1,8 +1,9 @@
 ---
-description: Migrate session sync from git artifacts to Turso backend
+description: Migrate session sync to Turso / Перенести синхронизацию сессий из git в Turso
 ---
 
 You MUST call the `opencode_sync` tool with `command="sessions-migrate-turso"`.
+Do not answer with plain text only.
 
 Behavior:
 - Ensure Turso setup is complete.

src/command/sync-sessions-setup-turso.md

@@ -1,8 +1,9 @@
 ---
-description: Install/auth/provision Turso for session sync on this machine
+description: Setup Turso for session sync / Настроить Turso для синхронизации сессий
 ---
 
 You MUST call the `opencode_sync` tool with `command="sessions-setup-turso"`.
+Do not answer with plain text only.
 
 Behavior:
 - Run Turso CLI install if missing.

src/command/sync-status.md

@@ -1,5 +1,10 @@
 ---
-description: Show opencode-synced status
+description: Show sync status / Показать статус синхронизации
 ---
 
-Use the opencode_sync tool with command "status" and report the results.
+You MUST call the `opencode_sync` tool with `command="status"`.
+Do not answer with plain text only.
+
+Reminder:
+- Report the results to the user in a readable format (repo, branch, last push/pull, working tree state).
+- If sessions sync is enabled, mention the session backend (git or turso) and last sync times.