「fix」の検索結果

worktree 준비 경로 fixture에 기존 파일을 심는 법과 spawn-block 정리 판정 3종

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

receipt 기반 이행 의존(transitive) 결함 재현 fixture

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

planning-review-stale-pending-fixture

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

named fixture 실행 전 Yardlet 바이너리 신선도를 판정하고 clean, rebuild, retry로 복구한다

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

provider-refusal fixture 수동 재현 절차

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

process fixture 외부 mutation 계수 분리

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

process fixture summary.json 증거 확보

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

builtin-bundle-reverify에 CLI fixture leg 절차 추가

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

generic fixture 워커의 attempt별 env-scrub 단언은 last-secret 사본으로

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

lint-fix 주장 과거 커밋 실증법

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

failover process fixture worker에는 model을 지정하라

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

범위 밖 선행 fix의 RED는 이슈 관찰 revision에서 재현

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

실제-process Git finish 중단 fixture

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

process fixture의 cross-worker failover는 opt-in 명시 필요

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

Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.

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

Capture a solved, verified problem as a durable learning in `docs/solutions/` so the next agent or engineer does not repeat the mistake or redo the investigation, and keep the `CONCEPTS.md` glossary in step. Use after a fix, debugging session, or design decision whose reasoning is not readable from the final code, tests, or existing docs — "document this", "write up what we learned", "capture this learning", "add it to solutions", "that worked, save it for next time". Writes nothing for routine fixes the code already explains. For auditing or cleaning up existing learnings, use `learn-with-docs-refresh`.

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

Create or review dygo Fixtures and explicit Patches for reference data, setup Records, backfills, renames, and unsafe lifecycle transitions. Use when metadata sync alone cannot express the required data change.

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

Review failing CI checks on pull requests, diagnose root causes, and fix issues. Covers common failures: tests, linting, type checks, security scans, and builds.

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

Complete shadcn/ui component management for adding, searching, fixing, styling, and composing UI in any React project. Use this skill whenever the user mentions shadcn, shadcn/ui, adding UI components, building forms or dashboards with Radix, working with component registries (@shadcn, @magicui, @tailark), or any task involving npx shadcn CLI commands. Also trigger when the user asks to fix styling issues, build a settings page, dashboard, or modal flow in a project that uses shadcn/ui — even if they don't say "shadcn" explicitly. This skill manages the full component lifecycle: search, add, view, diff, smart-merge upstream updates, and enforce critical rules for forms, composition, styling, and icons.

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

Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.

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

Verify and test Jupyter notebooks with iterative fixing. Arguments: [target] [--quick] [--fix] [--python-only] [--dotnet-only]

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

ALWAYS invoke this skill when delegating, planning, or managing any development task. Do not implement features, fix bugs, or start coding directly without first loading and following this orchestrator pipeline. Use when implementing features, fixing bugs, managing tasks, reviewing code, orchestrating work, or any task that needs structured delegation. Trigger on words like orchestrate, manage, implement, build, develop, organize, delegate, team lead, pipeline, or project manage.

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

Phased workflow for delivering a Drupal feature or non-trivial change: plan, implement, review, test, finalize. Use when building a new custom module, adding a route/form/plugin, changing entity structure or schema, or any task touching more than a couple of files. Do NOT use for typo fixes, CSS tweaks, or single-line changes — use the tiny-fix skill instead. Each phase has an exit condition; do not move to the next phase until it is met.

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

Own goal-first engineering outcomes: investigate, find root cause, design, plan, then delegate implementation unit-by-unit to cursor-implementation-loop, this plugin's kernel skill, with verification and honest reporting. Use to fix, build, or own an outcome end to end; investigate-and-fix; "make X work"; or plan-then-execute in one request. A request with an approved plan or equivalently precise spec that needs nothing beyond implementation belongs directly to cursor-implementation-loop. Requires this plugin's cursor-implementation-loop skill; they ship together.

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