grant/standards
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Thread inbox-check line and canonical .gitignore into the retrofit flow; scope relative-symlink rule to in-repo links

Browse Source 
Retrofit playbook Step 0/Step 1 and the /retrofit guide now seed every new repo
with the canonical .gitignore block and the inbox-check line, and Part 5 documents
/capture, /triage, /roundup. portability.md and the portability-checker guide now
scope the relative-symlink mandate to in-repo (committed) symlinks, so global
~/.claude/* links are no longer flagged. ROADMAP adds a high-priority cross-repo
git-hygiene audit.
This commit is contained in:
Keysat
2026-06-14 11:15:16 -05:00
parent 72bebdd3e8
commit 04651503d2
5 changed files with 42 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
portability.md
+5 -1
View File
@@ -57,7 +57,11 @@ secrets** — but it lands in three places.
Because every vendor path in this standard is a *relative* symlink (`CLAUDE.md → AGENTS.md`,
`.claude/rules/x.md → ../../docs/guides/x.md`), it commits and clones correctly on any
machine. This is the concrete payoff of the relative-symlink mandate: an absolute symlink
would commit too, but break on every other clone. Never commit an absolute symlink.
would commit too, but break on every other clone. Never commit an absolute symlink. This
mandate binds **in-repo** symlinks specifically — the ones git commits and clones. The
global `~/.claude/*` symlinks (point 3) are never committed, so the rule doesn't reach them:
they're per-machine glue, recreated on each machine by the adoption step, and may be absolute
without harm. A repo audit checks only the symlinks inside the repo.
**2. Inside a project repo — commit shared, ignore local.**