changes

.config/opencode/skills/doc-coverage/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: doc-coverage
-description: Documentation coverage checklist and update procedures — load when completing a feature or change set
+description: Documentation coverage checklist and update procedures — load when completing
+  a feature or change set
+permalink: opencode-config/skills/doc-coverage/skill
 ---
 
 ## When to Use
@@ -41,7 +43,7 @@ Check `AGENTS.md` and its symlinks:
 **Anti-patterns:**
 - Symlinks missing or pointing to wrong location
 - Instruction file is stale or empty
-- Instruction file duplicates `.memory/` tracking content (plans, research)
+- Instruction file duplicates basic-memory project note content (plans, research)
 
 ### 4. Inline documentation
 - [ ] Are complex functions/components documented with comments explaining **why**, not **what**?
@@ -67,4 +69,4 @@ Check `AGENTS.md` and its symlinks:
 
 - The **librarian** subagent is the specialist for documentation work.
 - Lead should delegate doc coverage review to librarian after coder completes implementation.
-- Librarian reads the changes, identifies doc gaps, and writes/updates documentation.
+- Librarian reads the changes, identifies doc gaps, and writes/updates documentation.

.config/opencode/skills/git-workflow/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: git-workflow
-description: Procedures for git commits, worktrees, branches, and GitHub PRs — load before any git operation
+description: Procedures for git commits, worktrees, branches, and GitHub PRs — load
+  before any git operation
+permalink: opencode-config/skills/git-workflow/skill
 ---
 
 ## Git Commit Procedure
@@ -13,7 +15,7 @@ description: Procedures for git commits, worktrees, branches, and GitHub PRs —
    - 1-2 sentences max.
    - Match the repository's existing style.
 5. Check for secrets: do NOT commit `.env`, credentials, or key files.
-6. The `.memory/` directory IS committed to git (it is meant for collaboration).
+6. Repo-local `.memory/` directories are legacy artifacts and should not be relied upon. Do not commit new `.memory/` content — use basic-memory notes (in the per-repo project or `main`) instead.
 7. Stage relevant files: `git add <files>` (not blindly `git add .`).
 8. Commit: `git commit -m "<message>"`.
 9. Run `git status` after commit to verify success.
@@ -99,4 +101,4 @@ gh issue comment <number> -b "<comment>"  # Add comment
 - **Never `git push --force` to `main`/`master`** unless the user explicitly confirms.
 - **Never skip hooks** (`--no-verify`) unless the user explicitly requests it.
 - **Never `git commit --amend`** unless: (1) explicitly requested OR pre-commit hook auto-modified files, (2) HEAD was created in this session, AND (3) commit has NOT been pushed to remote.
-- If commit fails due to pre-commit hook, fix the issue and create a NEW commit.
+- If commit fails due to pre-commit hook, fix the issue and create a NEW commit.

.config/opencode/skills/work-decomposition/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: work-decomposition
-description: Procedure for decomposing multi-feature requests into independent workstreams — load when user requests 3+ features or features span independent domains
+description: Procedure for decomposing multi-feature requests into independent workstreams
+  — load when user requests 3+ features or features span independent domains
+permalink: opencode-config/skills/work-decomposition/skill
 ---
 
 ## When to Load
@@ -106,7 +108,7 @@ When triggering a checkpoint, present:
 Do not interrupt the user for:
 - Implementation details (naming, file organization, code patterns)
 - Choices fully determined by existing codebase conventions
-- Decisions already covered by prior user answers or cached guidance in `.memory/decisions.md`
+- Decisions already covered by prior user answers or cached guidance in basic-memory project `decisions/` notes
 
 ## Coder Dispatch Rules
 
@@ -132,7 +134,7 @@ Each coder dispatch MUST include:
 2. **Specific file paths and edit points** from discovery (not vague references)
 3. **Discovered values verbatim**: i18n keys, API signatures, component names, existing patterns
 4. **Worktree path** for all file operations
-5. **Active plan file path** for the task (for example: `.memory/plans/<feature>.md`)
+5. **Active plan note** for the task (for example: a basic-memory project `plans/<feature>` note)
 6. **Quality tier** so coder understands the expected rigor
 
 ### Anti-patterns — Never Do These
@@ -196,4 +198,4 @@ Decomposition:
     - One worktree, one branch, one PR
     - Coder A: toggle + persistence together (they share state)
     - Or split if toggle is pure UI and persistence is API: two coder calls
-```
+```