Defame1297
2c6ce438b6
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
2.2 KiB
git
Skills and agents for working with a local Git clone over the git wire protocol, and for authoring and running the pre-commit hooks that guard it.
Install
Claude Code:
claude plugin marketplace add <owner>/<repo>
claude plugin install git@<marketplace-name>
GitHub Copilot CLI:
copilot plugin marketplace add <owner>/<repo>
copilot plugin install git
Local (development):
# Claude Code
claude --plugin-dir ./plugins/git
# GitHub Copilot CLI
copilot plugin install ./plugins/git
Conventions
Every skill in this plugin runs local git commands through the org's rtk wrapper, never bare git — see git-commits/SKILL.md's Gotchas and git-workflow/references/hard-rules.md. Issue #113 made that rule precise for skill prose, where a git <subcommand> mention can be either an instruction to execute or just a reference to the concept:
- Executable, instructed commands — anything telling the agent to run a command right now (an imperative step, a dispatch-table "Run" cell, a fenced code-block procedure) — use
rtk git. Example:rtk git push -u origin <branch>. - Illustrative or referential mentions — naming a flag's behavior, quoting a doc's own heading, describing what a command does in the abstract, or warning against an anti-pattern — stay bare
git. Example: "git switchrefuses rather than clobbering conflicting local edits."
This applies within this plugin's own skill files (git-*, pc-*) — it does not generalize to other plugins. The gitea-* skills, for instance, talk to a remote Gitea server through the gitea MCP tools and contain no git/rtk mentions at all; the distinction has nothing to hold onto there.
Contents
| Component | Path | Description |
|---|---|---|
| Skills | .apm/skills/ → skills/ |
git-commits, git-branches, git-history, git-remotes, git-submodules, git-workflow, git-worktrees, pc-author, pc-run |
| Agents | .apm/agents/ → agents/ |
git-orchestrate |
.apm/ is the authoring source; skills//agents/ are the generated mirrors plugin hosts scan (ADR-0017) — edit only under .apm/.
Author
Defame1297