Loading...
Loading...
Found 5 Skills
Cursor Cloud Agent 環境で Git hook 連鎖（特に commit-msg と Co-authored-by 付与・除去）を設計・実装・検証するときに参照する。Cursor 管理 hook の実行順、`commit-msg.cursor.co-author-strip` の命名規則、install スクリプト、lefthook 多層防御、テスト手順を定義する。
Lefthook (高速並列 Git hooks マネージャー) リファレンス。 lefthook.yml 設定、pre-commit / pre-push / commit-msg 等のフック、 parallel / piped 実行、glob / run / tags フィルタ、 CI スキップ、staged_files、Husky からの移行。
Two-way traceability between commits and tickets. (A) When committing any change, make sure the commit message carries the ticket / work-item number — derive it from the user's words, the branch name, or the current task, ask if unknown (a commit-msg hook is bundled but install it only on explicit request). (B) When the user asks WHY code is the way it is — "why was this changed", "who decided this", "is this hardcode intentional", "ทำไมถึงแก้อันนี้", "มีเหตุผลป่าว" — trace the line through git blame/log to the commit, extract the ticket number from the message, fetch the ticket from the tracker (Azure DevOps, GitHub Issues, JIRA), INCLUDING downloading and reading attached images (requirements often live only in an annotated screenshot), and answer with commit + ticket evidence. Trigger on any commit request in a ticketed repo, on "install commit hook", and on any why-is-this-code-like-this / change-archaeology question — even when the user doesn't mention tickets.
Set up and maintain hk git hook manager in any repository. Use when adding pre-commit hooks, configuring linters, setting up code quality automation, working with hk.pkl, or maintaining existing hook configurations. Triggers on tasks involving hk, git hooks, pre-commit checks, commit-msg validation, or linting pipelines.
git の commit-msg hook から呼ぶ、コミットメッセージの書式の検査器。規約の正本は philtzjp/.github の conventions.yml。hook が「書式の検査器がありません」と止めたとき、検査の結果に納得できないとき、hook を設定するときに使う。書式そのものの書き方は github スキルに従う。