Comentaris
Comentaris i anotacions del codi
loom-champion
rjwalters
"Human avatar for final decisions - promotes quality issues to approved status AND auto-merges Judge-approved PRs that meet safety criteria"
review-local-branch
nrwl
Deep code review of the branch you are standing on, before it becomes a PR. Scope is merge-base..working-tree, so it covers commits, staged and unstaged changes together. Runs the same review lanes as review-pr — implementation, verification, approach, security — against the local checkout through the sandbox CLI, and saves a draft to ~/.nx-branch-reviews/<branch>.md. Use when asked to review "this branch", "my changes", or work that is not yet on GitHub.
review-pending-pr-reviews
nrwl
Review, grill, edit, and post pending PR review drafts saved by /review-pr (or its batch/cron runners). Lists drafts that have not yet been posted, walks the maintainer through each finding, then posts, closes, or discards. Use when the user says "post my pending reviews", "what reviews are waiting", "go through the review outbox", or invokes /review-pending-pr-reviews.
authoring-errors-and-warnings
dotnet
'Guides authoring of MSBuild errors, warnings, and diagnostic messages. Consult when adding new MSBxxxx codes, writing or modifying user-facing diagnostic text, deciding between error/warning/message severity, working with Strings.resx resource files, formatting paths in error output, or evaluating whether a new warning could break WarnAsError builds.'
Xiaohongshu (小红书)
imoonkey
```
imoonkey
Write-op coverage (2026-04-19): all 12 write ops verified PASS end-to-end (likePost, unlikePost, savePost, unsavePost, followUser, unfollowUser, muteUser, unmuteUser, blockUser, unblockUser, createComment, deleteComment). createComment/deleteComment chain via ${prev.createComment.id} against a low-traffic target post — high-profile accounts (e.g. @instagram) trigger spam-filter shadow-deletes that 404 the immediate delete.
pr-apply-review
ryoppippi
Fetch and apply review comments from the current PR. Use when you need to address PR feedback.
stacks-cms
stacksjs
Use when working with Stacks CMS posts, authors, block-document pages, revisions, menus, redirects, scheduled publishing, blog feeds, or public page serving. Covers @stacksjs/cms, site-scoped CMS models, routes, and actions.
issue-auto-sync
jmagly
MCP tools: Gitea issue management
explain
NeverSight
"Deep explanation of complex code, files, or concepts. Routes to expert agents, uses structural search, generates mermaid diagrams. Triggers on: explain, deep dive, how does X work, architecture, data flow."
hunt-bugs
go-to-k
Proactively hunt for cdkd bugs by deploying real CDK apps that exercise common-but-untested AWS resources, configs, and CloudFormation notations against real AWS, then fix what breaks. Use for a periodic "find latent bugs" sweep, not for verifying a specific change.
social-content
LeoYeAI
"When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' or 'grow my following.' Use this for any social media content creation, repurposing, or scheduling task. For broader content strategy, see content-strategy."
launch-strategy
LeoYeAI
"When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas."
paper
diskixix0-collab
Academic paper workflow — find, read/annotate (HTML), daily digest, cite. Use when user invokes /paper, needs paper annotation, literature search, citation generation, or daily paper discovery.
fix-pr-reviews
weave-os
Fetches feedback from a GitHub PR — review-thread comments, ad-hoc PR comments (including those posted as a review's body without a thread), and bot/advisory review submissions — and fixes all of them as they appear (comments before CI). Bot comment-length nits apply verbatim; comments requiring a genuine human decision are NOT auto-fixed and are escalated to the user with options grounded in existing patterns and best practices. After each fix batch, runs pre-commit validation and submits, then waits for CI only when no actionable feedback remains. Loops until all feedback is resolved AND all CI checks have completed. Use when asked to fix PR comments, address review feedback, address PR-level bot reviews (e.g. workweave-bot advisory nits), babysit a PR to merge-ready, or handle review comments.
lsp-guide
weave-os
Recipes for the lsp tool — resolving where a symbol is defined, every place it is used, type signatures and docs, file outlines, and compiler/type errors through a real language server (Go, TypeScript/JavaScript, Python, Rust). Use when navigating or explaining code by symbol, finding callers or usages, checking what broke after an edit, or deciding between lsp and text search.
uzi-cli
vtmocanu
Drive the uzi factory from the terminal with the installed uzi CLI — list/inspect/approve/steer runs, read the judge's review, manage workers and repos, and read admin state. Built for agents (--json, documented exit codes) as much as humans. Say "send to uzi" or "ship to uzi" to drive a PRD issue to a merged, green MR (an Auto-mode orchestration).
literate-docs
ssiumha
Adds docstrings, comments, and WHY/DECISION tags to code. Use when documenting functions/classes with language-specific standards (JSDoc, PEP 257, GoDoc).
.NET Conventions
exceptionless
C# coding standards for the Exceptionless codebase. Naming conventions, async patterns, structured logging, nullable reference types, and formatting rules. Keywords: C# style, naming conventions, _camelCase, PascalCase, async suffix, CancellationToken, nullable annotations, structured logging, ExceptionlessState
moonbit-c-binding
moonbitlang
Guide for writing MoonBit bindings to C libraries using native FFI. Use when adding extern "c" declarations, writing C stubs with moonbit.h, configuring native-stub and link.native in moon.pkg or moon.pkg.json, choosing #borrow/#owned ownership annotations, designing callback trampolines, wrapping C pointers with external objects and finalizers, converting strings across FFI, or validating bindings with AddressSanitizer.
roborev-respond
harperreed
Use only when the user explicitly invokes $roborev-respond
imoonkey
source_url should match the page where the action would naturally happen — Pinterest sometimes rejects writes when source_url is just /. Use the board/pin URL the action targets (e.g. /<username>/<board-slug>/).
imoonkey
```
imoonkey
```