changes

.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.