tsforge

How to write and maintain tsforge agent skills — when to use a skill vs a rule vs a recipe vs docs, description routing, progressive disclosure, and the ship checklist. Use when creating, editing, or reviewing SKILL.md files under .claude/skills/, or when asked "should this be a skill?".

Adversarially review one tsforge harness subsystem (or all) against its invariants. Use when asked to "review the harness", "audit a subsystem", "check the gate/tools/loop/process layer", or before a release. Reads source + tests, checks each invariant, repros suspected breaks, and returns a structured findings list.

End-to-end tsforge release — validate, commit pending work, bump version, signed tag, push, watch npm publish. Use when the user asks to release, publish, ship, tag, or cut a version. Does not require a clean git tree. Manual-only; do not auto-run during unrelated tasks.