refactor(git): normalize rtk-prefix usage, add metadata.version

Two bundled fixes across the same nine skills, since both touch the
same files.

Issue #113: skill prose used rtk git and bare git inconsistently for
the same operations, with no stated rule for which applied where.
Executable instructed commands (a dispatch-table "Run" cell, a fenced
code-block procedure, an imperative step) now consistently use rtk
git; illustrative or referential mentions -- naming a flag's behavior,
quoting a doc heading, warning against an anti-pattern -- stay bare
git. Documented in the new plugins/git/README.md, scoped to this
plugin only: gitea-* skills talk to the server over MCP tools and
carry no git/rtk mentions at all.

Also the git-plugin slice of #127: metadata.version added to the
eight skills that lacked it. git-commits already had one and is
untouched.

Fixes: #113
Fixes: #127
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EeH8SCbcrCAQrtymkNuhKP

plugins/git/.apm/skills/git-history/SKILL.md

@@ -8,6 +8,7 @@ description: >
   `git-commits`. Not a Gitea server's history -> `gitea-branches`.
 
 metadata:
+  version: "1.0.0"
   category: git
   source_keys:
     - git-scm-bisect-docs
@@ -34,13 +35,13 @@ allowed-tools: Bash
 
 ## Step 2 — Query the log
 
-Default to `git log --oneline`, then narrow by whatever is known:
+Default to `rtk git log --oneline`, then narrow by whatever is known:
 
-- **Content**: `git log -S"string"`, or `-G"regex"` to match any diff line. `--pickaxe-regex` makes the `-S` argument a POSIX ERE; `--pickaxe-all` shows every file in a matching changeset.
-- **A line or function**: `git log -L <start>,<end>:<file>` or `git log -L :<function>:<file>`. Confirm the range resolves before reporting on it — an off-by-one silently omits the target.
-- **A file across renames**: `git log --follow -- <file>`. Without `--follow` the history stops at the rename boundary.
+- **Content**: `rtk git log -S"string"`, or `-G"regex"` to match any diff line. `--pickaxe-regex` makes the `-S` argument a POSIX ERE; `--pickaxe-all` shows every file in a matching changeset.
+- **A line or function**: `rtk git log -L <start>,<end>:<file>` or `rtk git log -L :<function>:<file>`. Confirm the range resolves before reporting on it — an off-by-one silently omits the target.
+- **A file across renames**: `rtk git log --follow -- <file>`. Without `--follow` the history stops at the rename boundary.
 - **Mainline only**: `--first-parent` follows the integration branch and skips commits merged in from side branches.
-- **Structured output**: `git log --format="%h | %s | %an (%ar)"`.
+- **Structured output**: `rtk git log --format="%h | %s | %an (%ar)"`.
 
 If you need the placeholder catalogue, format presets, `--diff-filter` letters, full `-L` syntax, ancestry filters, pickaxe binary-file behaviour, or `git diff` output-control flags such as `--stat`, `--word-diff` and the whitespace options, read `references/git-log-format.md`.
 
@@ -49,8 +50,8 @@ If you need the placeholder catalogue, format presets, `--diff-filter` letters,
 Offer the operation and its consequence; run it only once the user has chosen.
 
 - Backporting the commit to another branch is a cherry-pick, and cherry-pick is `git-commits`' — it owns the destination-branch check, the `rtk git` wrapper and the `--abort` path. Hand it the SHA; do not run `git cherry-pick` from here.
-- `git revert <commit>` adds a new commit undoing it — for un-applying merged work without rewriting history.
-- `git blame <file>` attributes each line to the commit that last touched it, when the question is which commit introduced one specific line.
+- `rtk git revert <commit>` adds a new commit undoing it — for un-applying merged work without rewriting history.
+- `rtk git blame <file>` attributes each line to the commit that last touched it, when the question is which commit introduced one specific line.
 
 For diff output control on the located commit, read `references/git-log-format.md`.