Comments
Code comments and annotations
gh-pr-comments
by yotamleo-org
List/show review threads on a specific PR ("what comments are on PR 97"). Needs PR number. Not Jira or issue comments.
support-responder
by aibangjuxin
You are a patient, empathetic, and knowledgeable Support Responder. You are an expert on the product and can clearly explain complex features in simple terms. Your primary goal is to solve the customer's problem quickly and leave them feeling heard, valued, and satisfied.
review
by griffinwork40
"Dispatches parallel dimension agents across a diff, PR (URL or number), commit SHA, branch, staged changes, or patch file — covering security, correctness, api-compat, test-coverage, and perf-observability — synthesizes findings by severity, and emits a merge recommendation. Use when changes are ready for review before merge. Read-only: this skill analyzes and reports only — it never edits files, commits, pushes, comments on a PR, or modifies the PR description."
principle-explain-the-number
by yotamleo-org
"Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think."
roadmap-clips
by yotamleo-org
Use when the operator wants a cross-source roadmap from the luna vault — writes a 60-Maps/ note. Proposals only.
correct
by yotamleo-org
"Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct."
turn-this-feature-into-a-blog-post
by GhostScientist
Generates a technical blog post from code implementation. Use when asked to write a blog post about a feature, explain an implementation for a blog, document code as a blog article, or create technical content from source code. Triggers on phrases like "write a blog post about", "turn this into a blog", "create a technical article", or "explain this for a blog".
dotnet-testing-autofixture-customization
by kevintsengtw
AutoFixture 進階自訂化技術完整指南。當需要自訂 AutoFixture 建構器或處理特殊型別的測試資料產生規則時使用。涵蓋 DataAnnotations 自動整合、ISpecimenBuilder 實作、優先順序管理。包含 DateTime/數值範圍建構器、泛型化設計與流暢式擴充方法。 Keywords: autofixture customization, autofixture customize, autofixture 自訂, specimen builder, ISpecimenBuilder, RandomDateTimeSequenceGenerator, NumericRangeBuilder, DataAnnotations autofixture, fixture.Customizations, Insert(0), 自訂建構器, NoSpecimen, 泛型化建構器
adversarial-arch-review
by p-wegner
Adversarial, code-metrics-driven architecture review. Distrust the codebase's own self-assessment (memory, "DONE/COMPLETE" notes, comments), use churn/complexity/coupling metrics to TARGET where to dig and to INFER structural problems, verify the most damning findings directly before relaying, and answer three questions — what architecture decisions truly limit future work, what dependencies (internal + external) are risky, what code is concerning. Use for "adversarial architecture review", "be critical about the architecture", "what's truly limiting us", "metrics-based code health audit", "where are the real risks".
board-navigator
by p-wegner
Comprehensive guide for agents to interact with the kanban board using MCP tools
robotframework-libdoc-explain
by manykarim
Explain Robot Framework keywords and their arguments from library/resource/suite documentation. Use when asked how to use a keyword, what arguments it takes, or to retrieve detailed keyword docs from libdoc across one or more libraries/resources.
count-code-lines
by p-wegner
Count productive code lines per package using scc, scoped to actual source directories
playwright-cli
by p-wegner
Automate browser interactions, test web pages and work with Playwright tests.
agentic-kanban
by p-wegner
Operate the agentic-kanban board — a kanban board where each card is an AI coding session in its own git worktree. Use when asked to work a ticket, drive a project hands-off, review or merge agent work, inspect what agents are doing, or wire the board into another tool. Covers the MCP tools, CLI, board views, statuses, and the review/merge gate.
pywayne-cv-stereo-tag-matcher
by wangyendt
Stereo vision AprilTag matching for dual-camera systems. Use when working with pywayne.cv.stereo_tag_matcher module to match AprilTags from left/right camera views, find common tags between images, stitch stereo images together, and visualize results with color-coded annotations (all tags green, common tags yellow, red connection lines).
gh-pr-comment
by yotamleo-org
Add a general PR comment, not a thread reply ("comment on PR 42 saying X"). Needs PR number. Not thread replies/Jira.
devils-advocate
by griffinwork40
"Adversarially critique a proposal by generating alternatives. Dispatches 3 parallel critics (pragmatist, paranoid, architect lenses) — each invents one alternative approach — then a synthesis step ranks all 4 options and recommends the top choice. When the proposal was authored by someone other than the agent (inherited plan, someone else's PR, external review), a 4th steelman critic runs in the same parallel wave and strengthens the original first, so it is judged at its strongest rather than its weakest. Use when a plan, fix, scoping, decomposition, or named recommendation will drive decisions and you want structured alternative-generation before committing. Complements /shadow-verify — that skill re-derives factual claims; this one critiques whether the chosen approach itself is best."
mysql
by wcygan
Plan and review MySQL/InnoDB schema, indexing, query tuning, transactions, and operations. Use when creating or modifying MySQL tables, indexes, or queries; diagnosing slow/locking behavior; planning migrations; or troubleshooting replication and connection issues. Load when using a MySQL database.
content-marketing-engine
by NadavShanun-design
Use when planning content that generates and warms demand - choosing topics from real buyer questions, picking formats, setting a sustainable publishing cadence, and distributing/repurposing across channels (LinkedIn, Reddit, X, Substack, email, blog). Covers the create-once-distribute-many model, channel norms, community engagement that isn't spammy, and how content feeds both inbound and GEO.
multichannel-sequences
by NadavShanun-design
Use when designing or auditing an outbound cadence - how many touches, how far apart, which channels (email, LinkedIn, phone, SMS), what each touch says, branching on behavior, and when to stop. Covers sequence architecture, channel roles, spacing, reply/branch logic, and exit rules. For the email copy itself see cold-email-writing; for LinkedIn mechanics see linkedin-outreach.
linkedin-outreach
by NadavShanun-design
Use when reaching prospects on LinkedIn - connection requests, DMs, engaging with their posts, and social selling. Covers the no-pitch-first rule, comment-before-connect, profile-based personalization, note vs no-note invites, respecting LinkedIn's invite limits and account safety, and a sane follow-up cadence. For overall cadence design see multichannel-sequences.
context-decorate
by wcygan
Scan a codebase and place CLAUDE.md context files in directories that lack them. Spins up a team of subagents to parallelize the work — each agent covers a few directories and generates a succinct overview of the directory's purpose and key subdirectories. Use when onboarding to a new codebase, improving Claude context quality, annotating project structure, or scaffolding directory-level context for AI assistants. Keywords: context, CLAUDE.md, annotate, codebase, directory, onboard, decorate, scaffold context, context files.
diff-explain
by wcygan
Explain a diff in plain English. Works with staged changes, unstaged changes, commits, branches, or PR numbers. Use when you want to understand what changed and why. Keywords: diff, explain diff, what changed, understand changes, diff summary, review changes, read diff
explain
by wcygan
Explain code, functions, modules, or programming concepts with structured walkthroughs covering purpose, patterns, data flow, edge cases, and performance. Use when explaining code, understanding how something works, learning a concept, or walking through a codebase. Keywords: explain, how does this work, what does this do, walkthrough, understand, code explanation, concept, teach, learn