「fix」の検索結果

Use when implementing new observable frontend behavior or fixing a behavior-changing bug where a failing test can describe the missing or incorrect behavior first. Apply to components, hooks/composables, utilities, API clients, route guards, or user workflows; pure behavior-preserving refactoring uses an already-green contract instead.

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

Use when restructuring existing frontend code while preserving observable behavior, including responsibility extraction, module movement, conditional simplification, API cleanup, or data organization. Do not use for new feature behavior, behavior-changing bug fixes, dependency or framework migrations, or proven dead-code cleanup.

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

Upgrade the vendored NeMo-Skills slice to a newer upstream commit. Use when the user asks to "bump vendored", "sync NeMo-Skills", "update vendored sha", "upgrade NS", or wants to pull a specific upstream fix. Inside the sgl-eval repo.

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

Use when a task needs the judgment of a Crane and Tower Operator — deciding whether current gust readings require a stand-down given a specific load's sail area, running a blind lift through a signal person when the pick or landing zone is outside the cab's sightline, reading a fixed installation's load chart at the counterweight/jib configuration actually installed, calculating each crane's load share on a two-crane tandem pick, or judging when to set the jib to free-slew ahead of a wind event.

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

Use when a task needs the judgment of a Computer User Support Specialist — triaging an inbound ticket's severity and SLA clock before troubleshooting it, verifying a caller's identity before any password/MFA/account-state change, walking a live incident through a structured troubleshooting sequence instead of guessing at a fix, deciding whether a request is an incident, a service request, or the underlying problem behind a string of incidents, or judging whether a ticket should resolve at tier 1 or genuinely needs escalation.

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

Use when a task needs the judgment of a Conveyor Operator — diagnosing a mistracking belt before it becomes edge damage or spillage, verifying every lockout/tagout isolation point on a conveyor with a gravity take-up or incline before entering the nip zone, calculating each conveyor's actual delivered capacity in a multi-conveyor line to find the true bottleneck, deciding whether a mechanical or vulcanized splice fits a given tension rating, or judging whether a pinch-point guarding gap needs an immediate stop versus a scheduled fix.

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

Use when a task needs the judgment of a Molder, Shaper, or Caster (ceramics, concrete, and similar non-metal, non-plastic materials) — calculating mold/pattern dimensions from a material's actual characterized shrinkage rate, deciding whether a demolding decision should follow a fixed time or a material readiness signal, controlling drying/curing rate to avoid cracking on uneven-thickness parts, or verifying mold dimensional accuracy after extended use.

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

Use when a task needs the judgment of an audio and video technician — setting up and operating audio/video equipment for a live event (concert, conference, keynote, broadcast remote), coordinating wireless mic frequencies on site, diagnosing a live audio/video signal-chain failure during a show, or sequencing a load-in against a fixed doors-open deadline.

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

Use when a task needs the judgment of a barista — dialing in a new bag of espresso, diagnosing a sour or bitter shot, steaming milk to a target texture and temperature, managing a rush-hour drink queue, or deciding when a grind adjustment (versus a distribution or equipment problem) is the actual fix.

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

Use when a task needs the judgment of a Baker — scaling a formula using baker's percentages to hit an exact batch weight, diagnosing whether a fermentation problem traces to dough temperature or mixing development, judging proof readiness from a poke test rather than a fixed clock, or tracing a poor-oven-spring result back to over- or under-proofing instead of the oven.

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

Use when a task needs the judgment of a Broadcast Program Director — diagnosing a ratings-book decline into cume vs. TSL causes, deciding whether a format flip is warranted versus a clock/rotation fix, setting spot-load and stopset structure against sales pressure, or clearing content through standards-and-practices and FCC compliance review.

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

Use when a task needs the judgment of a Biofuels Processing Technician — adjusting catalyst dosing for transesterification based on actual measured feedstock free fatty acid content rather than a standard fixed dose, verifying conversion completeness via actual glyceride content testing rather than visual inspection, actively monitoring fermentation temperature and pH throughout the process rather than checking only at the end, and managing byproduct quality as a distinct economic consideration alongside primary fuel yield.

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

Use when a task needs the judgment of an Architecture/Engineering firm or department manager — pricing a project fee (lump sum vs. hourly vs. % of construction cost), staffing a project against backlog, evaluating scope creep on a fixed-fee job, managing professional liability exposure, or deciding whether to pursue a project given current utilization.

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

Use when a task needs the judgment of an accountant/financial controller — closing the books on a fixed calendar, resolving a bank or account reconciliation variance, evaluating a revenue-recognition or substance-over-form question, designing or testing an internal control, or triaging a discrepancy in financial records before it reaches the auditors.

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

Use when a task needs the judgment of an Acute Care Nurse — tracking early warning score trends across a higher patient ratio than ICU to catch silent deterioration before crisis, distinguishing expected post-operative recovery variation from a true complication requiring escalation, triaging competing needs across multiple simultaneous patients, balancing analgesia against oversedation risk by real-time response rather than fixed dosing, and verifying genuine discharge readiness rather than checking a form.

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

Use when a task needs the judgment of an Aircraft Structure, Surfaces, Rigging, and Systems Assembler — deciding whether an out-of-tolerance hole or fastener needs a nonconformance report versus a field fix, verifying torque and calibration status before a fastener installation, diagnosing a FOD (foreign object debris) risk before closing a structure, or reading a drawing callout against a conflicting work instruction.

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

Use when a task needs the judgment of an aircraft service attendant — servicing an aircraft's potable water or lavatory/waste system without cross-connecting the two, sequencing turnaround tasks inside a fixed gate-time window, staging ground support equipment around an active aircraft, or timing servicing against a deicing/anti-icing holdover-time window before pushback.

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

Creates isolated git worktrees in .claude/worktrees/ with intelligent branch naming, auto-incrementing, and commit type detection (feat/fix/refactor). Supports manual descriptions and auto-generation from uncommitted git changes. Use when user requests to create worktree, start isolated work, parallel development, run /worktree command, or mentions "worktree".

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

Dedicated Core Web Vitals deep-dive: pull field data (CrUX / PageSpeed Insights), fall back to Lighthouse lab data, score LCP, INP, and CLS against Google's thresholds at the 75th percentile, and run per-metric diagnosis playbooks with concrete fixes. Use when user says "core web vitals", "CWV", "LCP", "INP", "CLS", "page speed metrics", or "field data".

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

Run a Lighthouse audit against any URL via the local Lighthouse CLI or the PageSpeed Insights API fallback, parse category scores and failed audits, and map every failed audit ID to its official Chrome docs page plus a one-line fix. Use when user says "lighthouse", "lighthouse audit", "run lighthouse", "lighthouse score", or "pagespeed".

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

测试环境自动准备 Skill。在执行任何测试之前，自动检查并准备完整的测试环境：服务健康检查、自动启动后端、数据库就绪、测试账号创建、依赖验证。确保后续测试在稳定环境中执行。触发词：「准备测试环境」「环境预检」「初始化测试环境」「测试前准备」。也被 role-测试工程师 Step 0 和 fixer Step A0/B0 自动调用。

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

Bug修复循环协调者。测试完成后，读取技术问题追踪台，按P0→P1→P2顺序协调修复，每修复一个触发针对性回归测试，循环直至P0+P1全清，输出可上线结论。所有信息通过文档传递，不依赖对话历史。触发词：「全自动修复循环」「按Bug清单修复」「修复所有问题」「循环修复到上线」「开始bug修复循环」。

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

项目待办管理器（两种模式）。【收集模式】接收任意混合输入 → 解析追加到「项目待办.md」文档，不立即执行；【处理模式】读取文档 → 前置决策收集 → 按优先级逐条路由执行 → 更新状态 → 批次报告。触发词：【收集】「有几个问题先记到待办」「加到项目待办」「先存到待办文档」「记录这些待办」；【处理】「处理项目待办」「按待办文档逐条修复」「开始处理待办文档」。⚠️ 触发词必须含「待办」关键词才激活，避免与 issue-tracker / bug-fix-loop 混淆。

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

Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

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