「review」の検索結果

Use when publishing, open-sourcing, exporting, sanitizing, or moving code, agent skills, prompts, templates, fixtures, datasets, workshop assets, or other artifacts from a private repository, vendor/runtime environment, or mixed working directory into a public repository or registry. Builds a provenance inventory, license/security review, explicit allowlist, clean staging package, approval dry run, and fresh public clone/install smoke. Triggers on "open source this", "publish these skills", "make this repo public", "export and sanitize", "подготовь публичный релиз", "выложи скиллы", "опенсорсни", "санитизируй и опубликуй". NOT for ordinary upstream bugfix PRs, vulnerability disclosure, or creating a corp-* department.

日本語の概要は準備中です。原文の説明を表示しています。

Use when reviewing a bundle-plugin for structural issues, version drift, skill quality, workflow integration, or security risks — before releasing, after changes, or after adding skills. Auto-detects scope (full project vs skill vs workflow)

日本語の概要は準備中です。原文の説明を表示しています。

Verify that code changes are correct, safe, and ready to ship. Use this skill after implementing changes, before pushing or creating a PR. Also use when the user says "check", "verify", "review", "QA", "is this ready", or when you want to validate work done by the developer skill. Runs build, lint, and structural checks.

日本語の概要は準備中です。原文の説明を表示しています。

Run the weak-agent adversarial test harness against docx-cli. Spawns weak exercise agents (Haiku by default, Sonnet to probe, or a local agent harness's pre-produced runs) to perform real document tasks over six scenarios — five editing (MNDA form-fill + font fidelity, invoice table-edit/restructure + logo replace, résumé styling, contract redlining + commenting, contract finalize via accept/reject + comment reply/resolve) and one authoring (T. S. Eliot poetry journal: multi-column, verse, footnotes, links, figure) — renders every result with Word, has opus judge them against ground-truth rubrics, measures each exercise's tool economy, token cost, wall-clock, and correctness (from transcripts for Claude, the exercise.json ledger for the local harness), and synthesizes a prioritized ergonomics report. Use when the user says 'adversarial review', 'test docx-cli with weak agents', 'run the haiku harness', 'weak agent test', or wants to re-run yesterday's adversarial process.

日本語の概要は準備中です。原文の説明を表示しています。

End-to-end 3D printing for Bambu Lab printers. Finds models online (MakerWorld, Printables), generates them with AI (text-to-3D, image-to-3D) or as exact-dimension parametric CAD, checks and repairs printability, converts textures to AMS multi-color, renders previews, opens them in Bambu Studio for the user to print, and reads printer status, AMS filaments and print progress. Use this whenever the user wants to 3D print something, design or model an object for printing, work with STL/3MF/OBJ/GLB files for a printer, check on a Bambu Lab printer (A1, A1 Mini, A2L, P1S, P2S, X1C, X1E, X2D, H2C, H2S, H2D, H2D Pro), or asks about AMS filament, slicing or print progress, even if they don't say "Bambu".

日本語の概要は準備中です。原文の説明を表示しています。

Delegate bounded tasks to Grok Build from a supervising agent such as Codex. Use when the user asks Grok to investigate, review, implement, or provide another perspective, or when a distinct coding agent would materially help. Includes a background ACP client for progress, follow-up prompts, permissions, and cancellation.

日本語の概要は準備中です。原文の説明を表示しています。

Delegate bounded investigation, review, or implementation tasks to Antigravity CLI from a supervising agent. Includes a background client for task progress, follow-up prompts, conversation recovery, cancellation, and visible failures.

日本語の概要は準備中です。原文の説明を表示しています。

Judgment rules for user-facing text and docs: CLI and diagnostic output, error and help text, README and docs structure, code comments, titles, and generated reports, decks, or exports. Use when writing or changing any user-visible string, when adding or restructuring docs or deciding which page owns a fact, when a page is about to record a version, a deployment state, or a value the code already owns, when a comment, title, or artifact could carry the reasoning or an abandoned option behind the change, when a behavior change needs its copy sites swept, or when reviewing a diff that touches copy or docs.

日本語の概要は準備中です。原文の説明を表示しています。

Write, edit, or review UI copy, CLI messages, help text, code comments, and technical documentation covering product behavior, errors, status, setup, compatibility, or technical results.

日本語の概要は準備中です。原文の説明を表示しています。

ROS 2 engineering: rclcpp/rclpy, colcon/ament, launch, QoS/DDS, tf2/URDF, ros2_control, Nav2, MoveIt 2, sensors, runtime/artifact provenance, and hardware safety. Use for development, review, debugging, and ROS 1 migration to ROS 2. Not for general C++/Python, unrelated middleware, or web/mobile tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Run an honest market-fit and viability audit of any project or idea and produce a decision doc, not code. Use when someone asks "is this viable as a business", "audit the market fit", "make the case and compare to competitors", "should I apply to YC or bootstrap", or wants to validate a project, product, or market before investing more time. Gathers verifiable traction data first, researches the competitive field, gets an independent cold read, writes a doc with pre-committed pass/middle/kill criteria and a concrete week-1 assignment, then hardens it with an adversarial review loop.

日本語の概要は準備中です。原文の説明を表示しています。

Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).

日本語の概要は準備中です。原文の説明を表示しています。

Use when an agent is asked to draft, rewrite, edit, review, polish, copyedit, simplify, humanize, or create written prose, including creative writing, essays, posts, scripts, speeches, emails, documentation, product copy, and other style-sensitive text. Apply George Orwell's six rules and ASD-STE100 Simplified Technical English as a plain-English discipline while preserving the user's intended meaning, audience, tone, and explicit constraints.

日本語の概要は準備中です。原文の説明を表示しています。

End-to-end, phase-gated SDLC for AI coding agents: relentless design interview → reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification → converge. Handles features, bugs, refactors, greenfield projects, planning breakdowns, and migrations. Triggers on "absolute work", "build this end-to-end", "plan and build", "break this into tasks", "grill me on this plan", "pick up this ticket", "run this migration".

日本語の概要は準備中です。原文の説明を表示しています。

Vulnerability and security scan (defensive, your own repo): dependency CVEs plus risky code patterns (secrets, injection, weak authz), severity x reachability triaged and remediated without suppressing. Complements the built-in /security-review. Triggers on "absolute audit", "security audit", "are we vulnerable", "scan for CVEs", "check for secrets/injection", "harden this".

日本語の概要は準備中です。原文の説明を表示しています。

Multi-stage rebuttal analysis skill for RebuttalStudio. Use when organizing reviewer comments into stage-specific conference workflows, including stage1 breakdown, stage2 refinement, stage4 multi-round follow-up, and stage5 final remarks generation.

日本語の概要は準備中です。原文の説明を表示しています。

Refine a Stage2 NeurIPS rebuttal draft into polished, reviewer-facing prose in the author's style; preserve factual grounding, optionally prepend a courteous opening phrase, and normalize tables/code/formulas into Markdown.

日本語の概要は準備中です。原文の説明を表示しています。

Base template for Stage1 reviewer-comment breakdown. Use when creating or extending conference-specific Stage1 skills (for example ICLR, ICML, NeurIPS, ACL) so shared extraction, splitting, and response-mapping logic stays consistent.

日本語の概要は準備中です。原文の説明を表示しています。

Refine a Stage2 ICML rebuttal draft into polished, reviewer-facing prose in the author's style; preserve factual grounding, optionally prepend a courteous opening phrase, and normalize tables/code/formulas into Markdown.

日本語の概要は準備中です。原文の説明を表示しています。

Refine a Stage2 ICLR rebuttal draft into polished, reviewer-facing prose in the author's style; preserve factual grounding, optionally prepend a courteous opening phrase, and normalize tables/code/formulas into Markdown.

日本語の概要は準備中です。原文の説明を表示しています。

Fill a Stage5 final remarks template using condensed discussion markdown from all reviewers and optional rating changes. Use when generating final remarks after Stage3/Stage4 discussion.

日本語の概要は準備中です。原文の説明を表示しています。

Verification guide for citations added during rebuttal writing. Use when Stage 2 responses introduce new references, when the Area Chair asks about a cited paper, or when any citation in the rebuttal might have been AI-generated. Prevents the serious credibility damage of fabricated references in reviewer-facing documents.

日本語の概要は準備中です。原文の説明を表示しています。

Use when drafting or revising internal technical design docs, review notes, architecture writeups, or sharing posts in Chinese, especially when the tone should stay evidence-backed, calm, and suitable for peers or leaders rather than marketing or literary writing.

日本語の概要は準備中です。原文の説明を表示しています。

Make hand-painted watercolour-and-ink cartoon videos (MP4) with code — p5.js + p5.brush rendered frame by frame in headless Chrome, encoded with ffmpeg — starring Clawd or any character. Use when the user asks to make an animation, animated short, cartoon, music video, lyric video, animated GIF/loop or "a video of Clawd…", or mentions the PDoomVideo / ClaudeAnimationBase approach. Covers storyboarding, the engine API, the render-and-look review loop, music/lyric sync and splitting long videos across subagents.

日本語の概要は準備中です。原文の説明を表示しています。