apps/cli/src/templates/shared-skills/skills-sync/SKILL.md
Refresh bundled tx Claude Code and Codex skills in a project from the canonical tx source without manual copy and paste.
npx skillsauth add jamesaphoenix/tx skills-syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when the user wants to install or refresh the tx-managed skills for Claude Code, Codex, or both in a target project.
tx skills sync
tx skills sync --target claude
tx skills sync --target codex
tx skills sync --project-dir /absolute/path/to/project
tx skills sync --project-dir /absolute/path/to/project --json
tx skills sync from the canonical tx checkout or any environment where
the desired tx version is installed.added, updated, and unchanged files.tx skills sync updates the tx-managed bundle and preserves unrelated skill
directories.--project-dir when you want to sync another repo without changing the
current working directory.--target codex or --target claude when only one host needs an update.development
Implement and verify design doc invariants by annotating tests and source code with [INV-*] / @spec tags, then driving tx spec coverage from BUILD toward HARDEN (100% FCI). Works with any design doc that has an invariants block.
data-ai
Link tasks to paired PRD/design specs, export all open work to markdown, and keep Ralph-style loops moving by creating tasks, subtasks, and dependency updates through tx primitives.
development
Run Ralph against either the full repo queue or tasks linked to one design doc, with injected task/spec/queue context for Codex or Claude runtimes.
documentation
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.