From 899e3ed99246d9cc2e6088a540ef4480d87d6e82 Mon Sep 17 00:00:00 2001
From: goodboy <goodboy_foss@protonmail.com>
Date: Thu, 26 Mar 2026 19:28:43 -0400
Subject: [PATCH] Symlink `commit-msg` SKILL.md to global skill

Replace the repo-local 84-line `SKILL.md` with a
symlink to `~/.claude/skills/commit-msg/SKILL.md`
so the skill definition is maintained in one place
across all repos.

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code
---
 .claude/skills/commit-msg/SKILL.md | 85 +-----------------------------
 1 file changed, 1 insertion(+), 84 deletions(-)
 mode change 100644 => 120000 .claude/skills/commit-msg/SKILL.md

diff --git a/.claude/skills/commit-msg/SKILL.md b/.claude/skills/commit-msg/SKILL.md
deleted file mode 100644
index adf5cdef..00000000
--- a/.claude/skills/commit-msg/SKILL.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-name: commit-msg
-description: >
-  Generate piker-style git commit messages from
-  staged changes or prompt input, following the
-  style guide learned from 500 repo commits.
-argument-hint: "[optional-scope-or-description]"
-disable-model-invocation: true
-allowed-tools: Bash(git *), Read, Grep, Glob, Write
----
-
-## Current staged changes
-!`git diff --staged --stat`
-
-## Recent commit style reference
-!`git log --oneline -10`
-
-# Piker Git Commit Message Generator
-
-Generate a commit message from the staged diff above
-following the piker project's conventions (learned from
-analyzing 500 repo commits).
-
-If `$ARGUMENTS` is provided, use it as scope or
-description context for the commit message.
-
-For the full style guide with verb frequencies,
-section markers, abbreviations, piker-specific terms,
-and examples, see
-[style-guide-reference.md](./style-guide-reference.md).
-
-## Quick Reference
-
-- **Subject**: ~50 chars, present tense verb, use
-  backticks for code refs
-- **Body**: only for complex/multi-file changes,
-  67 char line max
-- **Section markers**: Also, / Deats, / Other,
-- **Bullets**: use `-` style
-- **Tone**: technical but casual (piker style)
-
-## Claude-code Footer
-
-When the written **patch** was assisted by
-claude-code, include:
-
-```
-(this patch was generated in some part by [`claude-code`][claude-code-gh])
-[claude-code-gh]: https://github.com/anthropics/claude-code
-```
-
-When only the **commit msg** was written by
-claude-code (human wrote the patch), use:
-```
-(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
-[claude-code-gh]: https://github.com/anthropics/claude-code
-```
-
-## Output Instructions
-
-When generating a commit message:
-
-1. Analyze the staged diff (injected above via
-   dynamic context) to understand all changes.
-2. If `$ARGUMENTS` provides a scope (e.g.,
-   `.ib.feed`) or description, incorporate it into
-   the subject line.
-3. Write the subject line following verb + backtick
-   conventions from the
-   [style guide](./style-guide-reference.md).
-4. Add body only for multi-file or complex changes.
-5. Write the message to TWO files:
-   - `.claude/skills/commit-msg/msgs/<timestamp>_<hash>_commit_msg.md`
-     * with `<timestamp>` from `date -u +%Y%m%dT%H%M%SZ`
-       or similar filesystem-safe format.
-     * and `<hash>` from `git log -1 --format=%h`
-       first 7 chars.
-   - `.claude/git_commit_msg_LATEST.md` (overwrite)
-
----
-
-**Analysis date:** 2026-01-27
-**Commits analyzed:** 500 from piker repository
-**Maintained by:** Tyler Goodlet
diff --git a/.claude/skills/commit-msg/SKILL.md b/.claude/skills/commit-msg/SKILL.md
new file mode 120000
index 00000000..3af0fccb
--- /dev/null
+++ b/.claude/skills/commit-msg/SKILL.md
@@ -0,0 +1 @@
+/home/goodboy/.claude/skills/commit-msg/SKILL.md
\ No newline at end of file