「fix」の検索結果

Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.

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

Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

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

Use for Nauthilus Lua plugins, Lua callback tests, policy compiler and registry work, Lua environment and subject sources, Lua actions, hooks, backend scripts, policy facts, obligation targets, `server/lualib`, `server/lua-plugins.d`, `server/policy`, and JSON fixtures under `testdata/lua`.

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

Use when starting, stopping, or inspecting the dev stack for this Hydrolix Grafana datasource plugin — Grafana (with the plugin bind-mounted), ClickHouse, Keycloak (OAuth), and the on-demand playwright runner. Covers `docker compose up` semantics, the `dist/` prerequisite, serving plugin artifacts from an alternate folder (any path, live or frozen, via an ephemeral compose override), switching Grafana versions, hot-reload behaviour, delve attach, log streaming, OAuth/anonymous auth, and ClickHouse fixture access. Apply whenever a task needs the plugin running locally, needs to reset the stack, or needs to debug why Grafana won't come up.

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

Scan downstream specs for contradictions with locked decisions and apply approved fixes with consistency checks

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

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

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

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

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

Use when about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims. Evidence before claims, always.

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

Layer-by-layer remediation loop using adversarial audits, targeted fixes, and fresh-run verification enforcement

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

Execute per-layer adversarial audit/remediation loop, persist fixes metadata, and manage fresh-run advancement

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

Present and apply contradiction fixes one-by-one, flag assumptions, run consistency checks, and write propagation record

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

Structured methodology for adversarial thinking — generating attack scenarios, abuse cases, race conditions, and security edge cases against specs and implementations. Produces spec-level gap items, not code-level fixes.

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

Senior Kotlin specialist code review — framework-agnostic. Use whenever the user asks to review, audit, critique, or get feedback on Kotlin code, a file, a class, a function, a module, a diff, a branch, a commit, or a pull request. Judges Kotlin language idioms, logic correctness, architecture and layering, concurrency (coroutines, Flow, structured concurrency, cancellation, race conditions), null safety, exception safety, testability, performance, and security. Detects force-unwraps, unchecked casts, GlobalScope, leaked mutability, broken structured concurrency, hidden side effects, weak abstractions, untestable seams, allocation hot spots, weak crypto, input-validation gaps, and PII logging. Outputs prioritized findings with file:line anchors and minimal-diff fixes. No assumptions about DI framework, UI framework, or build system.

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

Optimize a single Jetpack Compose @Composable function. Use when the user wants to improve, polish, animate, or refactor ONE Composable — keywords like "optimize this composable", "make this smoother", "add animation to this", "split this composable", "fix recomposition", "this composable is laggy", "polish this UI", or when user pastes/points to a single @Composable function. Analyzes the target for recomposition issues, missing animations, size/concern splits, and stability problems, then iterates with the user via AskUserQuestion to pick which optimizations to apply, then delegates implementation to the kta-compose-developer agent and summarizes changes. Input MUST be exactly one Composable (file path + function name, or function name alone).

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

Use test-driven development for behavior-changing feature or fix work, and whenever the user mentions TDD, test-first, red-green-refactor, tracer bullets, integration tests, or public-interface behavior tests. Skip for docs-only, path-only rename, formatting-only, or purely mechanical chores unless explicitly requested.

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

TanStack Query (React Query) v5 best practices for data fetching, caching, mutations, and server state management. Use when building data-driven React applications, setting up query configurations, implementing mutations/optimistic updates, configuring caching strategies, integrating with SSR, or fixing v4→v5 migration errors.

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

Verify an open factory PR before human review - re-runs gates, checks the test proves the fix, checks scope and test tampering. Use when reviewing a factory PR, running the PR review routine, or asked to independently check a change.

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

Inspect factory health, stale work, CI, security advisories, and recent run evidence without implementing fixes.

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

Structured build workflow: branch, delegate to coding agent, test, screenshot, and commit. Triggers on: "$devprocess", "build this properly", "use the coding agent workflow", or any feature/refactor/infrastructure change that is too large for a direct edit. NOT for: one-line fixes, doc edits, prompt tweaks, or simple config changes — do those directly.

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

Autonomous build-ship-verify loop that ends with code committed, deployed, and confirmed live. Triggers on: "$ownership", "execute X with ownership", "build this overnight", or any request for an autonomous product loop with no human checkpoints until production is verified. NOT for: one-off tasks, quick fixes, or supervised dev work (use devprocess for those).

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

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.

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

Diagnose and fix WhatsApp connectivity issues for OpenClaw agents. Use when: a PA is not responding, WhatsApp shows connected but messages don't arrive, the agent is online but not replying, or troubleshooting a new agent setup.

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

Step-by-step setup and troubleshooting for connecting an owner's Google Calendar to an OpenClaw agent with read and write access. Use when: setting up calendar access for the first time, fixing read-only access, re-authenticating a broken Google connection, explaining the difference between the owner's Google account and the agent's Google account, how an OpenClaw agent accesses Gmail or Google Workspace, where credentials are stored, how to use the agent inbox, how to give the agent write access to the owner's calendar, or guiding another agent or user through the email or calendar setup model.

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

Proactive self-monitoring of infrastructure, services, and health. Tracks disk/memory/load, service health, cron job status, recent errors. Auto-fixes safe issues. Triggers on: health check, heartbeat, monitor status, service status, infrastructure check.

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