Summarize the current diff per file as markdown: a `## <filepath>` heading per changed file followed by a prose summary of its changes. Triggers: /changes, "summarize the diff", "what changed per file", "per-file summary of changes", "суммаризируй дифф", "что изменилось по файлам". Skip for reviewing quality or bugs (use /code-review) and for raw diff output (plain `git diff`).
Compress an expository note into readable prose backed by a certified Glossary via a standalone CLI — abstractive idea-compression, not extractive trimming. Re-expresses the note as flowing prose (carrying the thesis and the relations among terms) above an optional `## Workflow` checklist of the note's actionable directives and a definitions-only `## Glossary` table, collapsing restatements to one entry each and keeping only operational tokens verbatim; a different model fidelity-grades the glossary definitions and the workflow steps against the source and surfaces anything that did not translate. Replaces /cut. Use on /distill, "distill this", "compress this note", "make a glossary of this note", "tighten this into its ideas", "summarize as a glossary", "compress this guide/procedure into steps", "this note is too long/verbose", «дистиллируй», «сократи в глоссарий», «выжимка», «сделай глоссарий», «сократи гайд в шаги»; route whole-repo glossary maintenance to /glossary.
Route the current context to one expert persona and return that lens's candid second opinion. Auto-classifies to the best-fit persona, or name one explicitly. Runs the persona as a spawned subagent so its reasoning stays out of the main context. Roster spans engineering, product, go-to-market, and craft. Out of scope: generating new designs (use /design), arguing both sides (use /debate), stress-testing one plan (use /probe), scoring confidence in a claim (use /grade). Invoke explicitly with /opinion.
Personal knowledge management in an Obsidian vault. Use whenever the user wants to save, find, review, or organize knowledge, even without saying "vault". Triggers: saving links/articles as references, distilling concepts into cards, writing original notes, searching or quizzing saved content, listing active projects ("what am I working on"), explicit /vault commands, weekly-log operations (backlog/бэклог, planning, completing tasks, sleep). Excludes direct file edits not routed through /vault (editing a .md file in a code repo that is not a vault artifact), Obsidian app features (kanban, canvas, plugins, .base), web search. Skip for session save/resume ("wrapping up", "where did we leave off") — use /track.
Orchestrate a multi-step task by delegating to fresh subagents, keeping the orchestrator session small. Triggers: /work <task>, "orchestrate this", "delegate this work". Skip one-shot questions, single-file edits, and the ambient "let's work on X" / "start working on X" phrasing.
Test an existing thing's behavior against a falsifiable claim and capture the result as a standalone Markdown record in the current working directory. Self-contained — no vault, no external templates, no project linking. Triggers: /experiment, "run an experiment", "test this claim", "verify whether", "does X actually", "check if X works", "is X true", "falsifiable claim".
Read or save a per-repo track — the rolling handoff file in `<repo-root>/.tracks/track-<slug>.md`. Triggers on explicit `/track` and `/track save` commands. Also triggers on session save/checkpoint phrases: "wrapping up", "save what we did", "log what we accomplished", "save our progress", "end of session", "save session", "we finished X and still need to do Y". Triggers on resume phrases: "what was I working on", "where did we leave off", "continue where I left off", "pick up the track". Track creation, status changes, Decisions/Backlog/Log edits, atomic write to disk all live here. Self-contained: no vault, no external config, no extra tools — just the repo working tree.
Rewrite negative instructions as positive directives and remove hedging language. Use when user invokes /affirm or asks to make instructions direct, remove hedging, flip negatives to positives, or strengthen language in skill files, docs, or prompts. Works on inline text, files, or conversation context. Target instruction and directive text only; route general prose editing to /distill.