AgriciDaniel/claude-obsidian / skills/wiki
wiki
VerifiedInitialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt this vault, Obsidian vault, second brain setup, persistent wiki.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.1 KB |
| references/coordination.md | markdown | 1.9 KB |
| references/css-snippets.md | markdown | 4.3 KB |
| references/dataview.md | markdown | 1.6 KB |
| references/frontmatter.md | markdown | 2.7 KB |
| references/git-setup.md | markdown | 2.5 KB |
| references/install-modes.md | markdown | 1.9 KB |
| references/knowledge-recipes.md | markdown | 3.3 KB |
| references/mcp-setup.md | markdown | 1.9 KB |
| references/model-guidance.md | markdown | 1.6 KB |
| references/modes.md | markdown | 3.1 KB |
| references/operation-transactions.md | markdown | 6.0 KB |
| references/plugins.md | markdown | 2.7 KB |
| references/provenance.md | markdown | 3.2 KB |
| references/rest-api.md | markdown | 1.4 KB |
references/git-setup.md
View on GitHub# Optional Git history
Git is optional. Vault correctness comes from operation transactions, expected
hashes, recovery journals, and deterministic validation, not from background
commits.
## Initialize only with approval
Do not initialize a repository, add a remote, stage files, commit, or push merely
because a vault was scaffolded. If the user requests local history, first show
the selected vault and planned action, then initialize Git in that vault. Keep
workspace state, caches, secrets, and trash excluded.
A typical user-vault ignore policy includes:
```gitignore
.obsidian/workspace.json
.obsidian/workspace-mobile.json
.trash/
.DS_Store
.vault-meta/
```
Transaction bundles, recovery journals, queues, and derived chunks may contain
note text, local paths, or source URLs, so keep all `.vault-meta/` ignored by
default. If the user deliberately wants to version a stable configuration file
from that directory, add the narrowest reviewed exception while leaving runtime
subtrees ignored. Adjust the remaining entries to actual plugins and privacy
needs. Do not copy the product repository's ignore file blindly.
`checkpoint` commits exactly one completed operation and therefore requires an
existing parent commit. After `git init`, create a separate reviewed baseline
before running any operation you intend to checkpoint:
```bash
git status --short
git add -- <reviewed-baseline-paths>
git diff --cached --stat
git diff --cached
git commit -m "vault: reviewed baseline"
```
Select baseline paths deliberately; do not stage ignored runtime state, secrets,
or raw payloads merely to make the repository non-empty. The checkpoint command
never creates this baseline or silently folds pre-existing files into an
operation commit.
## Exact-operation checkpoints
After a successful claude-obsidian transaction, an explicitly requested
checkpoint is:
```bash
python3 "$CORE" checkpoint OPERATION_ID --vault "$VAULT"
```
The command verifies recorded hashes, refuses any pre-existing staged state,
runs deterministic lint by default, and excludes raw source payloads unless the
user opts in. It builds and verifies the commit through a temporary index, then
advances the ref by compare-and-swap. A durable pending record makes an
interrupted finalization retry-safe. Review the returned commit with `git show`.
Pushing or adding a remote is a separate external action that requires explicit
user authorization.
Avoid automatic-commit plugins during agent operations because they can capture
partial or unrelated state and invalidate exact-operation history.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |