Results for “maker-comment”

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`.

Refactors a Python script into a beginner-friendly project with clear comments and a complete markdown tutorial.

Create new skills, modify existing ones, and measure their performance through iterative evaluation and benchmarking.

Transforms git diffs and change descriptions into narrative commit messages that explain why a change was made, following Conventional Commits format.

Create repository-adaptive checkpoint commits for coherent work, including requests to split changes into commits and push; publication remains separately authorized

Use when writing or editing a code comment or a documentation block, and when reviewing the comments and documentation in a diff before presenting it. Decides what stays in the source, what moves to reference documentation, and what gets deleted.

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

Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.

Resolves an approved article comment task into a publishable AI markdown reply by fetching article context from a local HTTP API (with sf-cli fallback), reasoning with the selected quote and full article content, and writing the final reply to a backend-provided local result file path.

Create new skills, modify and improve existing skills, and measure skill performance through iterative evaluation and benchmarking.

Decide which pull-request review comments are actionable. Use when addressing review feedback, monitoring a PR, or filtering already-handled comments.

Eloquent, model, migration, relationship, hasMany, belongsTo, belongsToMany, Acorn Eloquent, custom table, wp_posts, wp_users, wp_postmeta, factory, query scope, scopePublished, global scope, make:model, make:migration, lando acorn migrate, $fillable, $casts, $timestamps, $primaryKey, HasFactory, db:seed, seeder — Eloquent ORM for custom and WordPress tables via Acorn

Builds a Power × Interest stakeholder map and generates a communication plan per quadrant. Use when managing a complex launch, aligning cross-functional teams, or preparing stakeholder engagement strategy. Triggers on: stakeholder management, stakeholder map, stakeholder alignment, communication plan, power interest grid, cross-functional alignment, executive alignment, managing up.

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.

Create an experiment for the MATLAB Experiment Manager app from user code, script, or problem description. TRIGGER when: user asks to create an experiment from a script/function, wants to sweep parameters or hyperparameters, asks to compare configurations, or describes a problem suitable for experimentation. DO NOT TRIGGER when: user is debugging an existing experiment, wants to run/resume trials, or already has a working experiment set up.

Generate user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria, with descriptions, design links, and acceptance criteria.

prd-writer

Generates ultra-compressed commit messages in Conventional Commits format with a subject line ≤50 characters and a body only when the 'why' isn't obvious.

Generate a Conventional Commits message from staged changes and wait for confirmation before committing. Use when the user asks to commit or generate a commit message.

Generate clear, descriptive commit messages following conventional commits format. Use when committing code, writing commit messages, or when the user asks for help with git commits.

Create user stories using Mike Cohn format with Gherkin acceptance criteria, translating user needs into development-ready work with clear outcomes and testable conditions.

Turn a diff or plain description into a conventional-commit message - honest type and scope, a why-focused body, breaking changes flagged, nothing invented.

Create meme concepts with trending formats, captions, and brand alignment. TRIGGERS - Use when user needs help with meme-creator related tasks.

Knowledge Craft

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

Creates a complete change proposal with design, specs, and tasks in one step, ready for implementation.

Generate or improve MATLAB help text (documentation comments) for a function, class, or script file following MathWorks standards (H1 line, syntax paragraphs, See Also, 75-char lines). Read BEFORE writing MATLAB help — default patterns (Inputs:/Outputs: lists, block comments, uppercase See Also) produce non-conforming output. Use when writing, rewriting, fixing, or reviewing MATLAB help comments or function documentation.

Create meme concepts with trending formats, captions, and brand alignment. TRIGGERS - Use when user needs help with meme-creator related tasks.

当用户已有确认过的行为规格（理想来自 write-spec），要在编码前把技术问题问清楚、比较方案、锁定技术决策——技术选型、架构、数据模型、接口契约、错误处理、测试策略——并沉淀成可 review 的技术设计依据时使用。不要用于：行为/需求还没钉死（先 write-spec）、想法还模糊（先 refine-idea）、任务拆解或实现计划（那是下游 split-task）、调试或代码评审。

Add a comment to a GitHub issue or pull request

Extract warm prospects from competitor and industry post engagers across LinkedIn, Twitter, and blogs

Monitor social platforms and forums for brand mentions, category discussions, and competitor activity

Annotate the outline with where to mention specific brand products. Designed-in at outline time so product callouts feel natural in the draft, not bolted on.

Creates a complete change proposal with design, specs, and tasks in one step, ready for implementation.

Craft messages that are understood, remembered, and drive action using the SUCCESs checklist (Simple, Unexpected, Concrete, Credible, Emotional, Stories). Use when the user mentions "make it memorable", "sticky messaging", "tagline", "value proposition", "why the message isnt landing", "knowledge curse", "surprise gap", or "concrete language". Also trigger when writing pitch decks, simplifying complex product explanations, or making presentations more compelling and memorable. For narrative brand frameworks, see storybrand-messaging. For viral sharing, see contagious.