Commit Graph

7 Commits

Author SHA1 Message Date
Henner M. Kruse 9f39a898c4 Fix setup.md: version-discovery fragility and unused argument-hint
Observed live: a stale plugin-cache version dir (1.0.0) coexisted with
the active one (1.1.0). setup.md's 'try the hardcoded version path
first' advice picked the stale one, its --install-raw-git-hook flag
failed silently, and Claude went on an unscripted forensic dig (chained
test&&echo, --help probing, grep/cat across both version dirs, cat'ing
plugin.json, stat'ing .in_use mtimes) to figure out which version was
actually active.

Fix, in both plugins' commands/setup.md:
- Never hardcode a version number. Always do one bounded
  find -maxdepth 1 -type d first; disambiguate multiple hits via the
  .in_use marker Claude Code itself writes, falling back to highest
  plugin.json version. Explicitly rule out the exploration that
  happened here (stat/mtime, --help, reading source, diffing versions)
  since setup.sh has no --help and unrecognized flags just error.
- Wire up the declared but previously-unused argument-hint
  ([repo-name] [repo-path] / [vault-path] [mode]): if the user already
  supplied it on the command line, skip asking the question that would
  just re-collect the same info.
2026-08-05 18:17:09 +00:00
Henner M. Kruse d481d4f2a4 Bump git-manager plugin to 1.1.0
Backward-compatible feature addition (raw-git nudge hook, tag subcommand,
repo-ambiguity guidance in SKILL.md). Bumping per ARCHITECTURE.md's
documented convention, and because the plugin cache path is version-keyed
(~/.claude/plugins/cache/skill-repo/git-manager/<version>/), so a bump is
also what makes /plugin marketplace update reliably pick up the change.
2026-08-04 14:05:28 +00:00
Henner M. Kruse 1d0b66df2e Add opt-in raw-git nudge hook, independent of anti-chaining hook
Forces a normal confirmation prompt (never a silent block, never a silent
allow) when Bash runs raw git instead of git_cmd.sh, worded more
insistently when the subcommand is one the wrapper already supports.
Raw git stays a valid fallback for unsupported subcommands and
unregistered repos - a hard deny would remove that fallback entirely.

Also documents in SKILL.md that repo ambiguity (which registered repo is
meant, or none at all) must be resolved by asking the user rather than
guessing - a hook only sees the literal command string, not the
conversation, so that judgment can't live in the hook itself.
2026-08-04 13:58:30 +00:00
Henner M. Kruse 47595ff160 Allow tag in git-manager's subcommand allowlist
Tagging a commit doesn't rewrite or discard history/working-tree state,
unlike stash/merge/rebase/reset which stay excluded as a deliberate
guardrail.
2026-08-04 13:35:11 +00:00
Henner M. Kruse 6c6fc35a1f Fixed setups 2026-08-04 14:28:10 +02:00
Henner M. Kruse e485d33f00 Added git-manager, updated READMEs 2026-08-04 10:45:25 +02:00
Henner M. Kruse c774df7ad7 Initial commit 2026-08-04 00:18:16 +02:00