Comments
Code comments and annotations
searchable-events
by vitorpamplona
The NIP-50 indexing surface of Quartz — the SearchableEvent interface, which event kinds are searchable, exactly what text each kind's indexableContent() contributes, how the SQLite/filesystem stores consume it, and the NIP-50 SearchQuery extension grammar plus SearchRelayListEvent (kind 10007). Use when making a kind searchable, changing what a kind indexes, diffing the searchable set at a Quartz version bump (external search engines mirror this table), debugging why an event is or isn't found by search, or working with search extensions (include:spam, domain:, …).
vera-language
by aallan
Write programs in the Vera programming language. Use when asked to write, edit, debug, or review Vera code (.vera files). Vera is a statically typed, purely functional language with algebraic effects, mandatory contracts, and typed slot references (@T.n) instead of variable names.
author-migration
by nrwl
Author or scope a first-party Nx migration. Use whenever code removes, renames, or deprecates an option/flag/executor/generator-schema field, changes a default, or bumps a dependency, and someone asks whether existing workspaces need a migration so they don't break on nx migrate/upgrade. Covers writing the colocated update-VER/NAME.{ts,spec.ts,md} set, the migrations.json entry (version, requires, implementation, prompt, documentation) or packageJsonUpdates group, and the AI-agent prompt/runbook .md for prompt-only or hybrid (generator + prompt) migrations. Also covers porting an upstream framework's own migrations into Nx. Invoke BEFORE writing, fixing, or editing any migration, migration prompt/runbook, or packageJsonUpdates group, and before concluding a breaking change needs no migration at all.
code-compaction
by dotnet
Use when a code/test/comment diff is called bloated, slop, LLM slop, bullshit, WTF, crap, rubbish, embarrassing, overengineered, adhoc, or "not paid by LOC"; or when symptoms include bloated comments, superfluous planning .md / .tools / one-time setup / phase-or-sprint tags, huge-file growth instead of new-file extraction, 5 copy-pasted tests that should be 1 parametrized test, duplicated test setup, reinvented helpers, near-duplicate logic across files, low reuse, 4+ new module-level helpers for one bugfix, fresh whole-AST/IR/syntax-tree walkers, or 150+ added LOC for one bugfix. Also use proactively before opening a PR whose diff smells like any of the above.
pr-description
by dotnet
Use when drafting, proposing, creating, or editing prose for a dotnet/fsharp GitHub PR or issue — body, title, comment, review summary, edits — including bare asks like "open a PR", "ship this", "write up what I did", "summarise the change", "reply on the PR", "edit the issue body", "gh pr create", "gh pr comment", "gh pr edit --body", "gh issue comment", "gh pr review --body". Primary use case is PR descriptions; same rules apply to PR/issue comments and review summaries. Not for labels, reviewers, merging, or code-review findings (just the prose write-up of them).
pr-finalize
by dotnet
Finalizes any PR for merge by verifying title/description match implementation AND performing code review for best practices. Use when asked to "finalize PR", "check PR description", "review commit message", before merging any PR, or when PR implementation changed during review. Do NOT use for extracting lessons (use learn-from-pr), writing tests (use write-tests-agent), or investigating build failures (use azdo-build-investigator and ci-analysis).
issue-triage
by dotnet
Queries and triages open GitHub issues that need attention. Helps identify issues needing milestones, labels, or investigation.
ben-code-quality
by BryanHarrisScripts
Apply PlotPickle's coding-agent discoverability standard and review deterministic BEN code-quality evidence. Use whenever an agent writes, renames, moves, or reviews JavaScript/TypeScript code for PlotPickle.
sequence-director
by BryanHarrisScripts
Provider-neutral procedure for turning one approved 24/96 Mini-Block into PLAN intent, STORYBOARD visual beats, PREVIS timing, deterministic render-clip prompts and post-generation Sequence Evidence.
notion
by atrislabs
Notion integration via AtrisOS API. Search pages, read/create/update pages, query databases, manage blocks and comments. Use when user asks about Notion, pages, databases, wikis, or docs.
deft-directive-portfolio-priority
by deftai
Pre-promotion portfolio prioritization: cluster competing open RFCs/issues from the local github-issue cache, emit a propose-not-apply priority brief (conflict matrix, shortlist, park), with epistemic citation gates, then hand off for operator dispose. Use when the operator asks for portfolio priority, a priority brief, competing RFCs, or to cluster open issues. Do NOT trigger on single-item "what's next?" ranking (deft-directive-triage / triage:queue) or post-promotion capacity prioritization (#1419/#1511).
imaging-data-commons
by ImagingDataCommons
Query and download public cancer imaging data from NCI Imaging Data Commons using idc-index. Invoke for any question about IDC collections, cancer imaging datasets, DICOM data access, radiology (CT, MR, PET) or pathology AI training sets, metadata queries, visualization, or license checks — even when the user doesn't explicitly mention "IDC". No authentication required.
handle-review-feedback
by SiinXu
Process external review feedback on your own open PR by converging the full business contract instead of stacking point patches.
masm-inline-comments
by tomevault-io
Enforce inline commenting conventions for Miden Assembly (.masm) files. Use when editing, reviewing, or creating .masm files. Use when this capability is needed.
sd-socratic-review
by platypeeps
Use when the user wants a bounded, adaptive Socratic review that asks one question at a time, tests demonstrated understanding, repairs misconceptions, and reports evidence without grading.
sd-explain
by platypeeps
Use when the user wants one complex topic explained accurately for a stated audience, purpose, prior-knowledge level, and depth, with explicit analogy and limitation boundaries.
sd-diagram
by platypeeps
Use when the user wants an evidence-backed technical diagram. Prefer Archify when available; support explicit Mermaid requests and tool-neutral briefs.
sd-humanizer
by platypeeps
Remove signs of AI-written prose while preserving facts, structure, and the author's voice.
sd-video-notes
by platypeeps
Use when the user wants one or more supplied videos converted into source-faithful, timestamped notes with explicit transcript coverage, claim extraction, comparison, and read-only downstream handoffs.
monaco-milestone
by Munyon-Canyon
Names the Monaco command for each step of shipping a ticket or running a milestone. Use when writing, batching, dispatching, verifying, landing, restacking or promoting milestone tickets.
hook-authoring
by Mike-Byrne-AI
Hook script authoring conventions for tools/cc/hooks/. Use when writing or extending a hook, adding a bash extraction pattern to write_guard, modifying _normalize_path or path-handling helpers, reasoning about hook event ordering, or when the user mentions hook authoring, hook contract, hook regression, or path traversal in the harness. Codifies the contract every hook script must satisfy.
update-docs
by meta-pytorch
Update documentation across the repo after API changes. Finds stale references in docs, examples, docstrings, and fixes them.
pr-comments
by ccch1mneyyy
Read and triage existing pull request review comments, or address them when requested. Use for PR comment requests or /pr-comments; use review to inspect code without existing reviewer feedback.
practice
by ccch1mneyyy
Guide a programming exercise using dsh-tui or a topic the user wants to learn. Use for practice and coaching requests, rather than requests to deliver a product change.