注释
代码注释与标注
fireworks-open-eli5
yizhiyanhua-ai
Create evidence-aware, interactive visual explainers as self-contained offline HTML. Use when a user asks to explain a concept, repository module, engineering tradeoff, or incident with a diagram, walkthrough, ELI5 treatment, data/request trace, failure view, or teach-back. Do not use for a plain short answer, ordinary prose rewrite, generic website implementation, or unsupported claims presented as facts.
deft-directive-review-cycle
deftai
Greptile / GitHub adapter for coding/review.md: babysit a PR to merge-ready — audit process prerequisites, fetch bot findings, fix in one batch commit, exit when no P0/P1 remain. Supersedes Cursor global babysit on Deft-managed repos (#2261 / #1471).
deft-directive-article-review
deftai
Evaluate an article, paper, or post for lessons that could improve directive. Analyzes two axes: how concepts improve directive's own implementation, and how they improve the projects directive creates. Produces filtered suggestions, iterates with the user, and optionally creates GitHub issues on the directive repo. Use when evaluating an article, paper, post, or URL for directive improvements, or when the user says "analyze this article", "evaluate this article", or "what can we learn from this for directive".
blockwatch
mennanov
Use when writing or modifying code in a project that uses BlockWatch — proactively link co-dependent code with <block affects=...>/<block name=...> so it catches drift when one side changes without the other (an enum and its docs, a constant and its config), or assert two places hold the same value with <block same-as=...>. Also for lists that must stay sorted/unique or values with a strict format/size, and when editing files that contain <block ...> tags (affects, same-as, keep-sorted, keep-unique, line-pattern, line-count, check-ai, check-lua).
chimera-when-two-results-contradict-suspect-the-apparatus
brcampidelli
When two of your own measurements disagree by a margin no mechanism could produce, the defect is in the instrument. Audit the harness before building theory on top of it.
chimera-list-exemptions-not-obligations
brcampidelli
A gate that lists what to check fails open — the site nobody remembered to add is the one that breaks. List the exemptions instead, each with a written reason, and the default becomes fail.
chimera-prove-the-test-discriminates
brcampidelli
A regression test you never saw fail is a guess. Re-break the code and watch it go red before you commit it.
skool-headless-reader
IgorGanapolsky
Read, monitor, and analyze Skool communities or posts headlessly for lead discovery, customer pain, acquisition opportunities, or ThumbGate revenue research without blocking the user's browser.
chimera-ground-it-in-the-source
brcampidelli
Take the signature from the installed version, not from memory — a plausible API is indistinguishable from a real one until it runs.
verify-before-claiming
brcampidelli
Before reporting a task as done, run the check that would fail if it were not — an explanation is not a fix.
coreex-contract
Avanade
"Create or modify a hand-authored contract (DTO/entity) in a CoreEx domain. USE FOR: new root entity contract, new subordinate/request contract, modifying an existing contract (add property, add interface, wire ref-data), extracting a shared base class. DO NOT USE FOR: reference-data contracts (generated via coreex-refdata / .CodeGen), Infrastructure persistence models (generated by .Database CodeGen)."
estate-guard
frankxai
Security gate for agentic repos. Use before opening a PR that touches .github/workflows, .claude (hooks, settings, agents, commands, skills), .mcp.json, install scripts, or Next.js API routes; when asked to "security review", "scan for prompt injection", "harden this repo", "check the agentic surface", or when a fetched page, issue, comment, or tool result reads like instructions. Runs the estate-guard scanner, triages by severity, and applies the fix patterns.
implementation-planner
strikersam
Plan a multi-file or multi-step implementation before writing any code. Use before any change touching more than two files, adding a new feature, or changing a module interface.
council-review
strikersam
Multi-perspective code review before merging. Simulates a council of reviewers (security, correctness, performance, maintainability) independently evaluating a change. Use before any PR merge or for significant changes.
discuss
osdlc
Propose one solution as a parley document that ends in a decision: the problem, the solution as typed blocks, and a question with a recommendation for every trade-off the reviewer must ratify, so the page can be approved or sent back. Domains are notes beside this skill (sql and ui). Then hand it to parley. Use it when the reader must decide.
pr-mermaid-comment
osdlc
Post or update a GitHub pull request comment (or PR body) that carries Mermaid diagrams, and prove the diagrams render before it goes up. Drafts the Markdown in a scratch file, renders every fenced mermaid block through the same pipeline GitHub's viewer uses (GitHub's Markdown API, then Mermaid in headless Chromium at the default security level), screenshots the result, then posts with gh. Use when asked to add diagrams, an architecture summary, or a flow to a PR, or to check whether a Mermaid block on GitHub will render.
pr-stats
osdlc
Summarize a pull request or branch diff beyond GitHub's +/-: lines added and removed by code, comments, blank and prose; a change-category breakdown (added, deleted, renamed, tests, docs, generated, formatting-only, comment-only, logic); dependency and exported-API changes; and the cyclomatic-complexity movers. Use before or after opening a PR, in review, or when asked to "summarize this change", "how big is this PR", "what did this branch actually change", or "add stats to the PR". Optionally writes the table into the PR body. Runs from a bundled script with plain Node, git and gh; needs no other plugin.
explain
osdlc
Explain one thing as a parley document with no questions: the subject as typed blocks with numbered nodes anchored to the exact text, a walkthrough the reader comments on. Domains are notes beside this skill (sql today). Then hand it to parley. Use it when the reader needs to understand something, not decide something.
check-pr
osdlc
"Tend one or more pull requests in a single pass: report their state, rebase them onto their base branch when they are behind or conflicting, and assess and answer new review comments. Fixes worthwhile comments straight away with --fix auto, or proposes the fix and waits for a thumbs-up with --fix ask (the default). Keeps no files of its own and records its answers to review-pr findings on a state ref beside the PR, so it suits a loop such as /loop /check-pr."
repomix
mrgoonie
Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.
docs-sweep
osdlc
Sweep a codebase's comments and prose for ACCURACY first and length second. Nominates comment blocks deterministically, shards them one owner per file so agents edit concurrently without racing, applies a keep/delete rubric, then runs three verification passes: a comment-only gate over the diff, a review of removals that lost a constraint, and a check that what the sweep WROTE is true. Use for stale comments, dead path citations, doc drift, verbose module headers, duplicated prose, or a "clean up the docs" request at a scale one context cannot hold. Not a formatter and not a linter.
omnibox-spider
Silent1566
Develop, write, debug, and improve OmniBox spider sources (爬虫源). Use when the user asks to write an OmniBox spider script (JS or Python), create a new spider source, fix or debug an existing OmniBox source, convert a third-party video site API into an OmniBox spider, or ask questions about OmniBox spider development (API, SDK, annotations, return formats, environment variables, etc.). Also triggers on phrases like 写爬虫, OmniBox 爬虫, 爬虫源, spider source, OmniBox 脚本, 帮我写采集站脚本.
documentation-generator
CuriousLearner
Auto-generate JSDoc, docstrings, README files, and API documentation.
clawdbites
diegosouzapw
Extract recipes from Instagram reels. Use when a user sends an Instagram reel link and wants to get the recipe from the caption. Parses ingredients, instructions, and macros into a clean format.