メニュー
Reusable guidance for working with the tk ticket CLI in local-first repositories. Load when the project has a ./.tickets directory or TICKETS_DIR env defined.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Select Rails and Hotwire patterns derived from 37signals applications, with the incompatible parts removed. Use only as a supplementary reference alongside the `rails` skill.
Use when committing code changes — guides commit message structure, type selection, and body content following Conventional Commits format
Authoritative Rails patterns for modern object-oriented Rails applications. Use when writing Rails code that follows transaction-oriented architecture, explicit dependency injection, Phlex views, and RSpec testing.
| name | tickets |
| description | Reusable guidance for working with the tk ticket CLI in local-first repositories. Load when the project has a ./.tickets directory or TICKETS_DIR env defined. |
Use this skill when tk is available for the current project, as indicated by either ./.tickets/ in the repo or a TICKETS_DIR environment variable.
references/workflow.md - Session lifecycle, approval gates, and ticket hygiene.references/commands.md - Small, high-value tk command reference for common work.This skill covers reusable tk workflow and command usage.
If neither ./.tickets/ nor TICKETS_DIR exists, do not load this skill and do not mention tickets or tk.
After loading the skill, choose one of these modes:
private if the ticket directory is gitignored.private if the repo instructions or docs tell contributors to use another issue tracker for team workflow, such as Linear or Jira.shared.shared: tickets are part of the repo workflow. Ticket IDs may appear in branches, commits, and PRs. Ticket files may be staged and committed when the project tracks them.private: tickets are for personal tracking only. Do not mention ticket IDs in branches, commits, PRs, or other team trackers. Do not stage or commit ticket files.