「review」の検索結果

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit," "first 30 days," "QA mentorship," "joining QA team." Not for: setting up QA on a brand-new project from scratch — use `qa-start`. Related: qa-start, qa-project-context, shift-left-testing, ai-qa-review.

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

Write effective unit tests with Jest, Vitest, or pytest. Covers the test-doubles taxonomy (stub/spy/mock/fake), Arrange-Act-Assert, coverage threshold configuration and CI gating, snapshot testing, fake timers, and mutation testing with Stryker/mutmut. Use when: "unit test," "Jest," "Vitest," "pytest," "mock," "coverage threshold," "test doubles," "mutation testing," "fake timers," "snapshot test." Not for: interpreting coverage reports or finding coverage gaps — use coverage-analysis; AI generating the test code for you — use ai-test-generation; auditing existing tests for smells — use ai-qa-review; browser/component rendering assertions — use cypress-automation or visual-testing. Related: coverage-analysis, ci-cd-integration, ai-test-generation, shift-left-testing.

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

Implement visual regression testing with Playwright screenshots, Chromatic, Percy, and Argos CI. Covers baseline management, diff threshold tuning, dynamic content masking, responsive viewport testing, and review/approval workflows. Use when: "visual test," "screenshot," "visual regression," "pixel diff," "snapshot diff," "update baselines," "Chromatic," "percy snapshot," "argos screenshot." Not for: bulk baseline regeneration after a redesign broke many tests — use selector-drift-recovery; cross-browser rendering matrices — use cross-browser-testing; general Playwright test structure — use playwright-automation. Related: playwright-automation, ci-cd-integration, cross-browser-testing.

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

Use when starting, continuing, updating, exporting, or sharing a running transcript of a MATLAB AI tutoring session, especially when the transcript will be shared with an instructor, attached to a learner session report, or passed to an evaluation workflow for quality review.

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

Use when reviewing, auditing, scoring, or improving a real or synthetic MATLAB AI tutor transcript, tutoring prompt, generated lesson, exercise, feedback sequence, or skill behavior for MATLAB accuracy, active learning, assignment guardrails, feedback quality, debugging support, transfer prompts, and instructor-facing quality recommendations.

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

Use when an instructor wants to create, interview for, configure, install, update, or review a course AI-use policy for MATLAB AI tutoring. Produces an AI-POLICY.md file for LMS sharing and local tutoring-session enforcement by assignment guardrails.

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

Run the konsistent CLI, review all reported violations, and fix them in the codebase. Use when the user wants to "fix konsistent violations", "resolve konsistent errors", "clean up konsistent diagnostics", "make konsistent pass", "address structural convention violations", or asks to run konsistent and act on the results. The skill is interactive: it requires explicit user decisions when many violations stem from the same rule (rule vs. code question), explicit user confirmation before modifying any code, and a triage step for non-trivial violations. For editing `konsistent.json`, this skill defers to the `konsistent-config` skill.

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

Execute approved, bounded work in an isolated implementation conversation and return a structured evidence receipt. Use with inherited history or an explicitly identified source; no particular planning, testing, or review skill is required.

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

Convene a roundtable of sub-agents that debate a decision or proposal from opposing perspectives — parallel independent statements, anonymous cross-review, then a chaired verdict reporting consensus and dissent.

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

Review and adapt vllm_metax/registry registrations, quantization configurations, CustomOps and kernel dispatch against a target vLLM revision and installed MetaX APIs. Verify registration, inherited state, weight layouts and actual backend selection. Use for registry compatibility work, not standalone attention algorithms or monkey patches.

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

Review and adapt MetaX attention backends, MLA, sparse indexers, cache layouts, and their kernel wrappers against a target vLLM revision and the actually installed MetaX component APIs. Verify dispatch, supported configurations, and GPU numerical behavior. Use for attention adaptations outside vllm_metax/patch/; do not apply monkey-patch headers or patch audit requirements.

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

Review and upgrade MetaX model support against a target vLLM revision and installed MACA components, recursively including model-dependent attention and kernels. Establish quantization and cache differences, preserve upstream structure, and distinguish shared upstream bugs from adaptation defects. Use for model support work, not standalone monkey-patch or registry audits.

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

Generate a structured implementation plan from an evidence draft. Validate paths, obtain configured independent Codex and Qoder reviews, synthesize available advice against repository evidence, preserve the draft, and produce testable acceptance criteria and validation steps.

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

Design engineering principles for making TUI interfaces feel polished. Use when building Textual widgets, reviewing TUI code, implementing transitions, focus states, alignment, spacing, or any visual detail work. Triggers on TUI polish, design details, "make it feel better", "feels off", layout alignment, color consistency, responsive sizing.

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

Make technology decisions for every product capability by discovering existing assets, evaluating vendor-aligned options, and categorizing as Reuse/Extend/Build/Buy/Integrate/Research during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on "tech stack", "build or buy?", "what technologies?", "technical decisions", "what do we reuse?", "existing stack", "vendor constraint", "IBM-first", "what tools do we need?", "evaluate solutions", "select tech stack". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and cross-references. Feeds v0.6 Architecture Design.

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

Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what technologies?", "select tech stack", "build or buy?", "what do we reuse?", "existing stack", "technical decisions", "what tools do we need?", "evaluate solutions". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and trade-offs. Feeds v0.6 Architecture Design.

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

Connect user journeys to screens, defining the UI structure and navigation paths during PRD v0.4 User Journeys. Triggers on requests to define screens, design screen flows, map UI structure, plan navigation, or when user asks "what screens do we need?", "define screens", "screen flow", "UI structure", "information architecture", "navigation design", "wireframe planning". Consumes UJ- (User Journey Mapping), FEA- (Feature Value Planning), BR- (constraints). Outputs SCR- entries for screens and DES- entries for design system elements. Feeds v0.5 Red Team Review.

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

Summarize a contributor's Git history, a provided work log, or both into a concise, review-friendly self-evaluation for quarterly, semi-annual, or promotion cycles.

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

Create, edit, evaluate, and package agent skills. Use when building a new skill from scratch, improving an existing skill, fixing a skill that never triggers or fires unreliably, running evals to test a skill, benchmarking skill performance, optimizing a skill's description, reviewing third-party skills for quality, or packaging skills for distribution — even if the user doesn't explicitly say "skill" (e.g. "teach Claude to do X", "make the agent always follow Y"). Not for using skills or general coding tasks.

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

Watch the current branch's PR — reply to and resolve review threads, fix failing checks, and optionally merge when ready

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

Review and assess every issue in the TMDb project board's Backlog column — re-verify each against current main with a read-only fan-out, close the mechanically dead, promote the actionable to Ready with priority, size and execution order, and leave the rest in Backlog naming the decision they need. Use to groom the backlog, before planning a release, or on a schedule. Runs headless: it decides for itself within the rules below.

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

Audit the knowledge/ base and the .claude/ skills, agents and workflows for staleness, self-contradiction, and drift from their own stated rules — four independent adversarial auditors (two lenses over two trees) verify every load-bearing claim against the current tree, cross-examine each other within their tree, and reach a consensus on if/what needs changing. Use periodically, after a run of deliveries that changed build config, target layout or the skills themselves, or whenever you suspect the docs have aged out of true.

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

Редактура текстов на русском языке по методу Людмилы Сарычевой — от смысла к словам, а не наоборот. Use this skill whenever the user asks to edit, review, improve, shorten, or polish any Russian-language text — articles, posts, emails, landing copy, docs. Триггеры: «отредачь», «отредактируй», «почисти текст», «сократи», «перепиши по-человечески», «убери канцелярит», «сделай проще», «причешите текст», «дай фидбек на текст», «разбери мой текст», «слишком водянисто», «звучит как робот». Also trigger when the user pastes a Russian draft and asks what's wrong with it or how to make it better. Для написания текста с нуля см. skill statya; для текстов интерфейса — ux-copy.

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

UX-тексты на русском языке: кнопки, формы, ошибки, пустые состояния, онбординг, подтверждения, уведомления, пуши и микрокопия. Use this skill whenever the user asks to write, rewrite, review, choose, or improve interface copy, product messages, UI strings, transactional emails, push notifications, toasts, snackbars, forms, empty states, onboarding, errors, confirmations, labels, tooltips, or button text. Триггеры: «текст для кнопки», «сообщение об ошибке», «текст в форму», «пустое состояние», «подпись к полю», «текст тоста», «снекбар», «онбординг», «пуш-уведомление», «микрокопия», «UX-текст», «что написать на экране…», «лейбл поля», «тултип», «подтверждение удаления», «письмо-уведомление». Для статей и постов см. skills statya и redaktura; для проектного словаря — redpolitika.

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