deepseek-telegram-bridge

Use when auditing a codebase, reviewing a PR, conducting a security review, validating a fix is "professional vs shortcut", cross-checking a third-party report (Gemini/ChatGPT/Codex review), or any time evidence-only / reproducer-first / defect-tracked rigor is required. Composes with security-review and code-review skills.

Use this skill ANY time the conversation touches tests, test quality, test architecture, flaky CI, mocking strategy, coverage, or "is this ready to ship?" — including TypeScript/React, Node/Vitest, Playwright, MSW, property-based testing, race conditions, type-level testing, and architectural boundaries. Encodes a 40+ year Principal-SDET veteran persona with a Zero-Trust Check→Check→Verify→Validate→Execute protocol, the Golden Rules of testing, and a no-bullshit / brutal-reality-check posture. Trigger even when the user does not explicitly say "test" — anything about "is this safe to deploy?", "why is CI failing?", "the mock isn't working", or "this PR is ready" is in scope.

Manage and operate the DeepSeek TUI Telegram bridge — a systemd daemon that connects Telegram to deepseek-tui exec for remote session control. Use when checking bridge status, restarting the service, managing Telegram sessions, configuring the bridge, viewing logs, troubleshooting, or extending the bridge with new features. Covers: status checks, session management (/new, /status), service control (start/stop/restart), config editing, log inspection, user allowlist management, and bridge extension.