add claude-obsidian

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,41 @@
+---
+name: Bug report
+about: Something is broken or behaves unexpectedly
+title: "[bug] "
+labels: bug
+assignees: ''
+---
+
+## What happened
+A clear description of the unexpected behavior.
+
+## Expected behavior
+What you expected to happen instead.
+
+## Reproduction steps
+1. ...
+2. ...
+3. ...
+
+## Environment
+- Plugin version: (e.g. v1.9.0)
+- Claude Code version: (run `claude --version`)
+- OS: (e.g. macOS 14.5, Pop!_OS 24.04, Windows 11)
+- Obsidian version: (if relevant)
+- Transport selected: (filesystem / obsidian-cli / mcp-obsidian — see `.vault-meta/transport.json`)
+
+## Skill / agent / script involved
+Which surface is affected? (e.g. `/wiki-ingest`, `scripts/wiki-mode.py`, `agents/verifier.md`)
+
+## Logs / output
+```
+Paste relevant terminal output or error messages here.
+```
+
+## What you tried
+- [ ] Ran `make test` — all 8 suites green? Yes / No
+- [ ] Checked CHANGELOG for known issues at your version
+- [ ] Searched existing issues for similar reports
+
+## Additional context
+Anything else that might help (screenshots, related issues, recent changes).

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,36 @@
+---
+name: Feature request
+about: Suggest an idea, new skill, or enhancement
+title: "[feature] "
+labels: enhancement
+assignees: ''
+---
+
+## Problem
+What user need or workflow gap motivates this request? Be specific about the situation where today's behavior falls short.
+
+## Proposed solution
+Describe what you'd like to see. New skill? New agent? Change to an existing one? Sketch the interface (slash command, trigger phrases, expected output).
+
+## Alternatives considered
+What other approaches did you think about, and why is this one preferred?
+
+## Scope
+Which existing surface(s) does this touch?
+- [ ] A new skill (`skills/<name>/`)
+- [ ] A new agent (`agents/<name>.md`)
+- [ ] A new script (`scripts/<name>`)
+- [ ] Change to existing skill: (which?)
+- [ ] Change to plugin manifest / hooks / setup scripts
+- [ ] Documentation only
+
+## Compatibility
+- Does this change behavior for existing v1.x vaults? Yes / No
+- Does it require a new opt-in (`bin/setup-*.sh`)? Yes / No
+- Does it introduce a new dependency? Yes / No
+
+## Testing
+How would this be tested hermetically? (No network, no external services.)
+
+## Additional context
+Links, examples, or references to similar features in other tools.