القائمة
Inspect queue health, diagnostics, dashboards, run traces, and recent failures. Use when working in Claude Code and the user needs tx commands from this area.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Turn 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.
| name | tx-observability-traces |
| description | Inspect queue health, diagnostics, dashboards, run traces, and recent failures. Use when working in Claude Code and the user needs tx commands from this area. |
| metadata | {"short-description":"Inspect queue health, diagnostics, dashboards, run traces, and recent failures."} |
Use when the user is debugging tx behavior, stalled runs, or dashboard/API status.
tx diag doctortx trace listtx trace errorstx dashboard: Start API server + dashboard and open in browsertx diag: Diagnosticstx diag dashboard: Start API server + dashboard UItx diag doctor: Run system health checkstx diag stats: Show queue metrics and health overviewtx doctor: System health checkstx stats: Show queue metrics and health overviewtx trace: Execution tracing for debugging run failurestx trace errors: Show recent errors across all runstx trace heartbeat: Update run heartbeat statetx trace list: Show recent runs with event countstx trace show: Show metrics events for a runtx trace stalled: List or reap stalled running runstx validate is a deprecated alias for 'tx doctor'.Read references/commands.md for the full generated CLI help text for this skill's commands.
When working in Claude Code, 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 files