.config/opencode/skills/obsidian-vault/SKILL.md
Manage and navigate Obsidian vault with consistent structure, naming conventions, and linking patterns
npx skillsauth add alexismanuel/dotfiles obsidian-vaultInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when working with Obsidian notes in /Users/alexismanuel/workspace/obsidian_notes/notes.
| Note Type | Location | Naming |
|-----------|----------|--------|
| Daily notes | daily/ | YYYY-MM-DD.md |
| Tickets | work/tickets/ | RD-XXXX [Title]/ (folder containing Ticket.md, PRD.md, Plan.md) |
| Concepts | work/concepts/ | Descriptive title.md |
| Topics | topics/ | Descriptive title.md |
| Objectives | work/ | Y[X]S[X] Objectives.md |
Tickets in work/tickets/ use a folder-based structure called "Feature Folder":
work/tickets/RD-XXXX [Title]/
├── Ticket.md # Progress dashboard with links to [[PRD]] and [[Plan]]
├── PRD.md # Product Requirements Document (Goal, Requirements, Non-Goals)
└── Plan.md # Implementation plan (Technical Strategy, Tasks, Testing)
Each ticket is a folder, not a single file. Use the templates in templates/ to create each component.
topics/Index.md for vault overviewdevelopment
Generate GitLab merge request descriptions from git commits with automatic categorization and Jira integration.
development
This skill should be used when validating that an implementation plan was correctly executed. It verifies success criteria, runs tests, identifies deviations, and presents structured completion options including MR creation or discard.
development
This skill should be used when reviewing code changes in a branch against main/master/develop. It analyzes commits, integrates JIRA ticket and MR context when available, and produces a structured code review using Conventional Comments format.
development
This skill should be used when conducting comprehensive codebase research to answer questions, understand architecture, or prepare context for implementation planning. It spawns parallel sub-agents and synthesizes findings into a structured research document.