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
ROADMAP.md
+21
View File
@@ -118,3 +118,24 @@ the CLAUDE.md symlink, ROADMAP.md, the canonical `.gitignore`, and the inbox-che
**Open questions:** Gitea repo creation — API token vs. manual UI step; how much scaffolding
is generic vs. stack-specific (does it call a `/harden` step from item 1 to install the
stack's linter+hook?); whether the workshop output also seeds the first `## Current state`.
## 6. Cross-repo git-hygiene audit + remediation — HIGH PRIORITY
**Why:** a shallow scan of `~/Projects` (2026-06-14) shows the `.claude`/git setup is *not*
consistent across repos. Git repos with the full AGENTS.md + `.claude` + `.gitignore` setup:
`CRM`, `premier-gunner`, `recap-relay`, `recap`, `spark-control`, `standards`, `Workout-log`.
Outliers: `ten31-transcripts` has a `CLAUDE.md` but **no `.claude/` dir** (possible real file
instead of an AGENTS.md symlink — the stale-retrofit failure); `start-os` has neither (likely
an external/upstream repo). Plus many non-git folders (unprotected work). We don't yet know,
per repo, what inside `.claude/` is committed vs gitignored, or whether in-repo symlinks are
relative.
**Do:** fan out one read-only `portability-checker` (or `Explore`) per git repo under
`~/Projects`, each reporting: is `CLAUDE.md` a relative symlink to `AGENTS.md` or a real
file; what's in `.claude/` and which of it is tracked vs gitignored (esp. `settings.local.json`
committed by mistake, or shared `settings.json`/rules symlinks missing); whether `.gitignore`
carries the canonical block; any absolute in-repo symlinks. Synthesize one compliance matrix +
a prioritized remediation list, then a follow-up pass fixes each repo (its own commit).
**Open questions:** treat non-git folders (flag for retrofit) vs. external upstreams
(`start-os`?) differently; report-only first vs. auto-fix.