<!-- Thanks for contributing! A few quick checks make it more likely your PR ships fast. -->

## What this PR does

<!-- One or two sentences. What changed and why. -->

## Type of change

- [ ] 🐛 Bug fix (non-breaking change that fixes an issue)
- [ ] ✨ New feature (non-breaking change that adds functionality)
- [ ] 📜 New slash command
- [ ] 📚 Documentation update
- [ ] 🧹 Refactor / cleanup
- [ ] ⚠️ Breaking change (fix or feature that changes existing behavior)

## Related issues

<!-- "Closes #123" or "Related to #456". If none, write "n/a". -->

Closes #

## How I tested it

<!-- Be specific. "Ran /obsidian-save with a 200-line conversation, verified 5 notes were created in the right folders." -->

## AI-first rule compliance (required for any vault-writing command)

- [ ] My changes follow `references/ai-first-rules.md`
- [ ] If I added or changed a command that writes to the vault, the produced note has a `## For future Claude` preamble
- [ ] Frontmatter includes `ai-first: true`, `type:`, `date:`, `tags:`
- [ ] Wikilinks (`[[...]]`) used for every person, project, idea, decision referenced
- [ ] External claims have recency markers (`(as of YYYY-MM, source.com)`)
- [ ] Sources preserved verbatim (URLs inline, not paraphrased)

## Checklist

- [ ] I searched existing issues and PRs before opening this one
- [ ] My commit messages are descriptive (focus on WHY, not just WHAT)
- [ ] I updated the README or docs if user-facing behavior changed
- [ ] I updated `CHANGELOG.md` (under "Unreleased") if applicable
- [ ] If I added a new command, I added an entry in `SKILL.md` and the README's command table

## Screenshots / output (if visual or producing notes)

<!-- A screenshot of the new command running, or the vault note it produces, makes review 10× faster. -->

---

<!-- Maintainers: thanks for reviewing! -->
