菜单
Export, import, migrate, hydrate, and compact task state and sync artifacts. Use when working in Codex and the user needs tx commands from this area.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | tx-sync-data |
| description | Export, import, migrate, hydrate, and compact task state and sync artifacts. Use when working in Codex and the user needs tx commands from this area. |
| metadata | {"short-description":"Export, import, migrate, hydrate, and compact task state and sync artifacts."} |
Use when data needs to move between SQLite, JSONL, Codex, Claude, or migration layers.
tx sync exporttx sync statustx sync compacttx compact: Compact completed tasks and export learningstx history: View compaction historytx migrate: Manage database schema migrationstx migrate status: Show migration statustx sync: Sync, data management, and migrationstx sync auto: Manage automatic synctx sync claude: Write tasks to Claude Code team directorytx sync codex: Write tasks to Codex (coming soon)tx sync compact: Compact completed tasks and export learningstx sync export: Export stream eventstx sync history: View compaction historytx sync hydrate: Full rebuild from stream event logstx sync import: Import from stream eventstx sync migrate: Show database migration statustx sync status: Show sync statustx sync stream: Show stream identity and sequence stateRead references/commands.md for the full generated CLI help text for this skill's commands.
When working in Codex, prefer rg -n <pattern> <path> and rg --files <path> over broad grep -r or fragile find pipelines.
If a shell/search command fails because of malformed flags, truncated paths, or broken quotes:
rg command with an explicit directorynode_modul or unterminated quotesgrep -r with rg -n unless rg is unavailablefind probes with rg --files when you are really locating source filesTurn a design spec into an explicit tx task graph with `tx decompose`, then refine the graph using normal tx task and dependency primitives.
Generate a detailed design document via `tx doc add design`. Covers architecture, interfaces, data model, invariants, failure modes, verification, and testing strategy. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Reads companion PRD automatically to map EARS requirements to invariants. Output lands in specs/design/<name>.md.
Generate a system overview spec via `tx doc add overview`. Produces an architectural overview covering problem, scope, components, data flows, and non-goals. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Output lands in specs/<name>.md with tx-managed frontmatter.
Generate a detailed Product Requirements Document via `tx doc add prd`. Uses EARS requirement syntax with traceable IDs, acceptance criteria, and non-functional requirements. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Designed to be created alongside a companion `/design-doc`. Output lands in specs/prd/<name>.md.
Internal closed-loop skill: drive CLI/API/MCP to 100% shape parity (same service methods) AND behaviour parity (same response shapes). Uses ESLint rules tx/require-surface-parity + tx/interface-parity. NOT shipped to tx users.
Generate a system-level design document via `tx doc add design`. Covers cross-cutting architecture, service boundaries, data flows, scalability, and deployment topology. References plan via file path instead of embedding. Plan lives in ~/.claude/plans/<name>.md. Use for system-wide or multi-domain designs rather than feature-scoped subsystem docs.