alex/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: align opencode memory docs with .memory project

Browse Source
This commit is contained in:
alex
2026-03-11 11:08:39 +00:00
parent ffd0d31fa5
commit f7a1aac68b
12 changed files with 40 additions and 142 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
.config/opencode/skills/doc-coverage/SKILL.md
View File

@@ -25,13 +25,10 @@ For every completed change set, verify documentation coverage:
### 3. Instruction File
Check `AGENTS.md` and its symlinks:
Check `AGENTS.md` as the single instruction source:
- Does `AGENTS.md` exist and contain current project info?
- Do symlinks exist and point correctly?
- `CLAUDE.md -> AGENTS.md`
- `.cursorrules -> AGENTS.md`
- `.github/copilot-instructions.md -> ../AGENTS.md`
- If legacy tool-specific instruction files exist, has their durable repo guidance been consolidated into `AGENTS.md`?
- Does the instruction file contain:
- Project purpose and overview
- Tech stack and architecture
@@ -41,7 +38,7 @@ Check `AGENTS.md` and its symlinks:
- Is the instruction file in sync with current project state?
**Anti-patterns:**
- Symlinks missing or pointing to wrong location
- Mirrored instruction files requiring parallel maintenance
- Instruction file is stale or empty
- Instruction file duplicates basic-memory project note content (plans, research)
@@ -69,4 +66,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.

4
.config/opencode/skills/git-workflow/SKILL.md
View File

@@ -15,7 +15,7 @@ permalink: opencode-config/skills/git-workflow/skill
- 1-2 sentences max.
- Match the repository's existing style.
5. Check for secrets: do NOT commit `.env`, credentials, or key files.
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.
6. The managed per-repo basic-memory project directory is `<repo>/.memory/`; do not edit managed `.memory/*` files directly. Older repo-local memory workflow artifacts (including `.memory.legacy/` and legacy contents from prior workflows) are non-authoritative and should not be edited unless explicitly migrating historical content into basic-memory.
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.
@@ -101,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.