aliasunder
UserAgent skills for AI coding agents — trip planner, Obsidian vault, and more
Categories
Indexed Skills (8)
obsidian-vault
Create, edit, and audit notes in an Obsidian vault. Handles frontmatter properties, wikilinks, embeds, callouts, tasks, block references, tags, and Mermaid diagrams. Plugin-aware: Dataview queries and inline fields, Tasks emoji syntax, Kanban boards, Meta Bind fields, Templater templates, Bases schemas, and Canvas JSON. ALWAYS-ON: if the working directory is inside an Obsidian vault (a .obsidian/ directory in any ancestor, or a CLAUDE.md identifying the project as vault-embedded), use this skill for ALL .md file operations — including CLAUDE.md, TASKS.md, and session logs — even when Obsidian isn't mentioned. Triggers: "create/edit a note", "update frontmatter", "add tags", "fix the links", "write a Dataview query", "fix this callout", "add a task", "edit my Kanban board", "make a template", or any note-editing task in a vault. NOT for: .md files outside a vault (code-repo READMEs, GitHub issues, static-site content), generic markdown linting, or Obsidian plugin development.
trip-planner
Plan a real trip. Use for: hotel/flight/train/restaurant research for specific destinations and dates, creating travel documents (daily cards, itineraries, packing lists, offline guides), managing booking changes or cancellations, and resuming a trip project with CLAUDE.md/TASKS.md/memory/ files. Handles the full lifecycle — transport, accommodation, activities, restaurants, budget tracking, and printable traveler materials. ALWAYS use this skill in a trip planning project — detected by a CLAUDE.md with traveler profiles, an itinerary phase marker, or a memory/ directory with trip planning files. Also trigger on "plan a trip", "start a session", "research hotels", "find restaurants", "build the itinerary", "make daily cards", "create packing list", or any travel planning task. NOT for: presentations, file conversions, sending emails, building apps, or hypothetical travel questions.
bug-check
Systematic bug hunt focused on patterns that survive code review and test audit — description-vs-implementation mismatches, SQL correctness, type coercion bugs, boundary/off-by-one errors, behavioral asymmetry, and input validation gaps. Derived from analysis of 40+ bugs found by Qodo and CodeRabbit that the ship-check pipeline (pr-review, code-quality, test-audit) missed. Use when asked to "bug check", "check for bugs", "deep correctness check", "look for subtle bugs", or as part of the ship-check pipeline. NOT for: code style (use code-quality), test design (use test-audit), security review (use security-review), or high-level correctness review (use pr-review).
code-quality
Readability and convention compliance pass on production code, grounded in the project's AGENTS.md and the user's vault memory preferences. Use when asked to "do a readability pass", "code quality pass", "make more readable", "review code quality", "clean up against conventions", "simplify with my preferences", or "review against AGENTS.md". Different from the built-in /simplify (which is generic) — this loads project-specific conventions and personal preferences. NOT for: test file audits (use test-audit), full PR review (use pr-review), or generic simplification without convention grounding (use /simplify).
pr-monitor
Monitor PR status — CI checks, review bot findings, unresolved conversations — and address + resolve bot comments. After pushing fixes, waits for and handles new bot review comments before declaring merge-ready. Use when asked to "check PR status", "monitor this PR", "check CI", "resolve PR comments", "address review comments", "mark conversations resolved", or when waiting on a PR to be merge-ready. NOT for: initial code review (use pr-review), post-merge testing (use verify), or reviewing the diff itself.
pr-review
Project-aware PR review grounded in AGENTS.md conventions and vault memory. Runs a multi-dimension review: correctness, convention compliance, test quality, security, performance, and conditional checks (TDQS scoring, feature surface docs). Use when asked to "review this PR", "review PR #X", "do a thorough review", "review against AGENTS.md", or "review with my preferences in mind". Complements the built-in /code-review (which is generic) by loading project-specific conventions and personal preferences. NOT for: quick CI failure diagnosis (use pr-monitor), post-merge testing (use verify), or code simplification without a PR context (use code-quality).
test-audit
Audit test files against the project's AGENTS.md test conventions, ensuring tests meet the bar for high-quality behavioral specs. Also checks whether production code changes have adequate test coverage (coverage gap analysis). Use when asked to "audit tests", "check test quality", "review tests against AGENTS.md", "do a test pass", "check test conventions", "ensure tests are high quality", or "are there missing tests". Focuses on test design, assertion quality, and coverage gaps — not code coverage metrics. NOT for: production code quality (use code-quality) or full PR review (use pr-review).
ship-check
Run the full post-implementation review pipeline: pr-review -> code-quality -> test-audit -> bug-check -> pr-monitor. Phases 1-4 run as dedicated agent types (ship-check plugin) with skills preloaded — genuine fresh eyes with no inherited context. Phase 5 (pr-monitor) runs inline for user interaction. Use when asked to "ship check", "review pipeline", "full review", "run all reviews", or after implementation is complete and ready for review. NOT for: single-dimension review (use the individual skill), quick CI check (use pr-monitor), or post-merge testing (use verify).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.