菜单
Create and edit Obsidian Bases (.base files) — database-like views of notes with filters, formulas, and summaries. Use when working with .base files, creating table/card/list/map views of vault notes, or when the user mentions Bases, database views, filters, or formulas in Obsidian.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Mine architecture decision records (ADRs), gotcha files, runbooks, and docs/archive for cross-project lessons that warrant ai-playbook canonical specs. Use when a project lacks a populated retros/ directory but has equivalent material in other forms.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Orchestrate the canonical task↔PR↔release flow end-to-end. Two modes — `/dev-flow start <description>` scaffolds an OpenSpec change + branch + (optional) worktree + git hook ready for commits; `/dev-flow ship` validates the current branch + pushes + opens PR + monitors CI. Use whenever you start any non-trivial change in a playbook-consuming project. LLM-agnostic — works for Claude Code, Cursor, Antigravity, Gemini CLI, OpenCode, and humans.
Implement an OpenSpec change in parallel using multiple subagents (one per disjoint task group inside the same slice). Use when the slice's tasks.md has ≥2 task groups with disjoint write-paths AND >30 min of parallelisable work. For sequential implementation use openspec-apply-change instead.
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
| name | obsidian-bases |
| description | Create and edit Obsidian Bases (.base files) — database-like views of notes with filters, formulas, and summaries. Use when working with .base files, creating table/card/list/map views of vault notes, or when the user mentions Bases, database views, filters, or formulas in Obsidian. |
| model | haiku |
| allowed-tools | Read, Edit, Write |
Extension: .base — YAML content defining views, filters, and formulas.
filters:
and:
- property: status
operator: equals
value: active
- property: tags
operator: contains
value: project
views:
- type: table
name: Active Projects
columns:
- property: title
- property: status
- property: due_date
- type: cards
name: Card View
cover: banner
- type: list
name: Simple List
equals, not-equalscontains, not-containsgreater-than, less-than, greater-than-or-equal, less-than-or-equalis-empty, is-not-emptystarts-with, ends-withand / orformulas:
days_until_due:
expression: "dateDiff(today(), prop('due_date'), 'days')"
is_overdue:
expression: "prop('due_date') < today()"
table — spreadsheet-like with configurable columnscards — visual card layout with optional cover imagelist — simple list viewmap — geographic map (requires location property)summaries:
- property: effort
function: sum
- property: status
function: count-by-value
Use prop('property_name') in formulas to reference note properties.
Property names are case-sensitive and must match frontmatter keys exactly.