[Sync] Lua Hyprland chain, licence cleanup

common/.config/claude/skills/pr-loop/SKILL.md

@@ -2,7 +2,7 @@
 description: Babysit the current branch's PR — address review comments that don't need my input, re-check every ~10 min, and stop when there are no open comments left or the automated reviewers (Codex, Claude) hit their limit. Prep-only — stages fixes and drafts the commit message; never commits, pushes, or merges.
 argument-hint: [pr number or url — optional; defaults to the current branch's PR]
 disable-model-invocation: true
-allowed-tools: Bash(gh:*), Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git rev-parse:*), Bash(git fetch:*), Bash(git add:*), Bash(wl-copy:*), Bash(~/.config/git/claude-commit-msg:*), Read, Edit, Write, Grep, Glob, ScheduleWakeup
+allowed-tools: Bash(gh:*), Bash(git status:*), Bash(git diff:*), Bash(git log:*), Bash(git rev-parse:*), Bash(git fetch:*), Bash(git add:*), Bash(~/.config/git/claude-commit-msg:*), Read, Edit, Write, Grep, Glob, ScheduleWakeup
 ---
 
 # Watch this PR and resolve review comments (prep-only)
@@ -238,8 +238,7 @@ Current state (auth + the current branch's PR):
      quoted heredoc, so quotes and backticks survive) — it is stored with the paths you staged this cycle, so the `prepare-commit-msg` hook prefills it only
      for the commit that contains them (other sessions' handoffs are not overwritten). Never write
      `CLAUDE_COMMIT_MSG` / `COMMIT_EDITMSG` directly.
-   - **(c) Copy it:** `wl-copy < <file path printed by save>`.
-   - Tell me all three locations. **Never** run `git commit`.
+   - Tell me both locations. **Never** run `git commit`.
    (Skip this step when nothing new was staged this cycle.)
 
 10. **Ping + schedule.** Give me a tight summary — deltas only, don't restate unchanged threads:
@@ -271,9 +270,10 @@ Current state (auth + the current branch's PR):
 
 - **Never** `git commit`, `git push`, `gh pr merge`, `gh pr create`, `gh pr close`, or `gh pr edit`
   — I do all of those. You stage, react, resolve, and draft; nothing more. The only comment you may
-  post is a needs-input decision question. This is enforced, not just asked: `settings.json` denies
-  those commands and the `git-guard.py` PreToolUse hook blocks any spelling of them, so a slip is
-  refused with a reason rather than executed.
+  post is a needs-input decision question. Commit, push, merge and close are enforced, not just
+  asked: `settings.json` denies them and the `git-guard.py` PreToolUse hook blocks any spelling of
+  them. `gh pr create` / `edit` are allowed globally (create asks first), so for this loop the rule
+  above is the only thing holding them back.
 - Act only on the target PR. Don't touch unrelated files or other PRs.
 - **Keep context lean:** no raw JSON dumps in replies, no re-listing threads that haven't changed,
   idle cycles ≤2 lines. Every line you emit is re-read (uncached) on every later cycle.