Results for “remark”

Pauses mid-conversation to reassess direction, assumptions, and bias, then recommends whether to continue, pivot, or pause.

Makes completion state obvious at the end of every response using a red/yellow/green status block.

Track open comment periods and draft a substantive, on-the-record comment that argues your position within the docket's rules and deadline.

通用多轮迭代改进：对任意研究制品反复调用 /review → 解析反馈 → 修复 → 更新 wiki，直到达标

Write React hooks with clean effect boundaries and measured memoization. Use when working with `useEffect`, custom hooks, refs, transitions, or hook dependency problems in React.

`task-agent`/`review-agent`: use when broker delivery, ordering, acknowledgement, DLQ, backpressure, or replay changes; skip synchronous retry without message semantics.

Computes the Recall metric using torchmetrics, including configuration for binary, multiclass, and multilabel tasks.

Watermark component for adding watermarks to content areas. Invoke when user needs text or image watermarks, fullscreen watermarks, or content protection in Naive UI.

Guidance for writing Remotion React markup with animation patterns, media handling, sequences, effects, and advanced features like 3D, audio visualization, and parameterized videos.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

通用跨模型审查：Review LLM 对任意研究制品进行独立评审，输出结构化评分、wiki 实体映射与改进建议

Police the project's vocabulary — bust vague terms, keep the CONTEXT.md glossary sharp, and lock in decisions worth remembering as ADRs. Use when the user debates naming, says "what should we call this", asks to pin down terminology, wants a decision recorded, or when another skill (hot-seat, whiteboard) surfaces a decision that clears the ADR bar. Just reading the glossary for vocabulary is NOT this skill — trigger only when the words or decisions are being changed.

Write a useful, author-consistent article and substantively improve it before verification.

The single highest-leverage convention in code review is prefixing every comment

Turn owner feedback about agent behavior into concrete system changes. Use when the owner says something is off, wants the assistant to improve how it operates, asks for a reflection, or wants a durable fix instead of a one-off apology.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Resolve GitHub PR feedback end-to-end for the branch you are on. Use when you need to fetch all comments on the branch PR, evaluate whether each comment still applies, decide whether it should be addressed, implement fixes, run compile/tests with retry-on-failure, then commit and push the result.

spec-ship

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

Produces ultra-compressed, one-line code review comments that cut noise while preserving actionable signal. Each comment includes location, problem, and fix.

Generates a structured post-task reflection capturing surprises, patterns, prompt improvements, and gotchas, writing it to a markdown file without modifying project rules.

Run a trademark clearance search before adopting a new brand name, mark, or logo and risk-rate it clear, caution, or high-risk with a proceed/modify/abandon recommendation.

Weekly engineering retrospective. (gstack)

Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

Reranking retrieved documents with cross-encoders and LLM rerankers. Cohere Rerank v3, Voyage rerank-2, BGE reranker, ColBERT late interaction, Jina reranker. Cost and latency tradeoffs, top-K in / top-N out strategy. USE WHEN: user mentions "rerank", "reranker", "cross-encoder", "Cohere Rerank", "Voyage rerank", "BGE reranker", "ColBERT", "Jina reranker", "bi-encoder" DO NOT USE FOR: initial retrieval - use `advanced-retrieval` or `hybrid-search`; query rewriting - use `query-transformations`; agent decisions - use `agentic-rag`

Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs

Adds a persistent pattern or rule that Ralph will remember and apply to future stories.

Ask Gemini via local CLI and capture a reusable artifact

A mention input component for @mentions with dropdown suggestions, supporting both text and textarea modes

Weekly engineering retrospective. (gstack)

Ask a local external advisor CLI (Claude or Gemini) and capture a reusable artifact

Readability Review

Audit and reconcile the shared project glossary — find stale terms, missing definitions, conflicts, shadows, inheritance gaps, and cross-path divergences across research docs

Apply a text watermark to a photo using layer-based image composition for brand protection and copyright.

Simulator.Company reactions specialist — comments, events, approvals, ratings and other feedback attached under an actor. Use when the user wants to comment on an actor, reply in a thread, read/like/pin the discussion, mark comments read, or get reaction stats. Activate when the user says "comment on this actor", "leave a note", "reply to", "show the comments/discussion", "pin this comment", "mark as read", "прокоментуй актор", "залиш коментар", "відповісти на коментар", "закріпи коментар", "оставь комментарий", "ответь в треде", "закрепи комментарий". For attaching FILES to a reaction use `simulator-attachments`; for the actor's own fields use `simulator-actors`.