Add a repo CLAUDE.md forbidding worktree development of the plugin #15
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This repository has no project
CLAUDE.md. Developing the plugin from agit worktree is silently ineffective, so the constraint is now recorded in
a repo-local
CLAUDE.md.Cause (verified):
install.sh:19resolvesREPO_DIRto the absolute pathof the clone it runs from, and the symlink loop writes absolute targets
(
install.sh:44). The live~/.claude/skills/*,agents/*, andworkflows/*.jssymlinks all point into the primary clone~/dev/skills.Claude Code loads user-level skills/agents/workflows through those symlinks
regardless of cwd, so a session always executes the primary clone's
definitions — edits made in a worktree of this repo are not what the live
session runs. Re-running
install.shfrom a worktree skips existingsymlinks (
install.sh:37) and only links new skills, producing asplit-brain across two checkouts.
Secondary (verified): a worktree session re-keys the cwd-derived project
slug (
postmortem/scripts/postmortem.py:304,cwd.replace("/", "-")), sothe auto-memory and session transcript land under a different namespace
than the primary clone.
Scope: the constraint is specific to editing the plugin itself. Consumer
projects are unaffected.
Acceptance:
CLAUDE.mdexists at the repo root and states the no-worktree rulewith its rationale.