[Sync] Lua Hyprland chain, licence cleanup

common/.config/claude/skills/commit-msg/SKILL.md

@@ -1,8 +1,8 @@
 ---
-description: Draft a commit message for the staged changes, matching this repo's commit style, then print it in the reply, save it to the repo's CLAUDE_COMMIT_MSG file, and copy it to the clipboard. Never stages or commits. Use once you've staged what you want to commit.
+description: Draft a commit message for the staged changes, matching this repo's commit style, then print it in the reply and save it to the repo's CLAUDE_COMMIT_MSG file. Never stages or commits. Use once you've staged what you want to commit.
 argument-hint: [optional focus/scope hint]
 disable-model-invocation: true
-allowed-tools: Bash(git diff:*), Bash(git log:*), Bash(git status:*), Bash(git rev-parse:*), Bash(wl-copy:*), Bash(~/.config/git/claude-commit-msg:*), Read, Glob
+allowed-tools: Bash(git diff:*), Bash(git log:*), Bash(git status:*), Bash(git rev-parse:*), Bash(~/.config/git/claude-commit-msg:*), Read, Glob
 ---
 
 # Draft a commit message for the staged changes
@@ -26,9 +26,8 @@ Context for the current commit — what's staged, plus this repo's recent style:
    - Add a short body (wrapped ~72 cols) only when the change needs the *why*; otherwise
      subject-only. Don't invent motivation that isn't evident from the diff.
 4. **Print the message in your reply first** — as a single fenced ` ```text ` block, copy-paste
-   ready. This in-reply copy is the durable one: it lives in the transcript, so it survives even if
-   the clipboard gets overwritten later (by me copying something else, or another Claude session
-   running `wl-copy`). Always print it; don't rely on the clipboard alone.
+   ready. This in-reply copy is the durable one: it lives in the transcript, so it survives even
+   after the hook has consumed the handoff. Always print it.
 5. **Hand it off** so I can recover it any time — feed the raw message to the CLI as a quoted
    heredoc (so quotes, backticks and `$` in the body survive untouched):
    ```sh
@@ -41,8 +40,6 @@ Context for the current commit — what's staged, plus this repo's recent style:
    `prepare-commit-msg` hook prefills the next `git commit` / lazygit `C` with the message(s) whose
    paths are part of that commit, then consumes them. Never write `CLAUDE_COMMIT_MSG` or
    `COMMIT_EDITMSG` directly. The `save` output names the saved id and file path.
-6. **Also copy it to the clipboard** as a convenience: `wl-copy < <file path printed by save>`.
-   Then tell me all three places it is: **printed above**, **saved for the hook** (with its id),
-   and **on the clipboard** — so I never lose it to a stray copy.
-7. **Never** run `git add`, `git commit`, or `git push`, and never offer to — I stage and commit
+   Then tell me both places it is: **printed above** and **saved for the hook** (with its id).
+6. **Never** run `git add`, `git commit`, or `git push`, and never offer to — I stage and commit
    manually. Draft only.