「fix」の検索結果

Onboard a repository to skillsaw — run the linter, triage the findings by rule, apply autofixes, manually fix what remains, set up CI, and create a baseline. Use when adopting skillsaw on a new or existing project.

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

Pytest testing patterns for Python — fixtures, behavioral naming, behavior/risk-driven coverage, property-based testing with Hypothesis when useful, and mutation testing when justified. Use when writing tests, designing fixtures, configuring coverage, or applying parametrize, async testing, or property-based strategies.

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

Runs deterministic Python quality checks against a path or scope — formatting, linting, type checking, and typing-boundary policy. Use when checking or fixing code quality via prek, ruff, ty, pytest, or the check-typing-boundaries policy script. Reports results grouped by category; fixes only when explicitly requested.

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

Investigate pytest failures without treating tests or implementation as automatic authority. Use when diagnosing regressions, debugging test errors, or deciding whether to fix a test or code; trace the contract, product, fixture, and observation before choosing an evidence-backed correction.

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

Use when creating, grooming, planning, or closing a backlog item. Bridges backlog items to SAM planning with issue, project, and milestone tracking against the configured backend. Activates on interactive browsing with no arguments, loading an item by issue reference or title match to run grooming and SAM planning, autonomous unattended runs that substitute evidence-derived decisions for clarifying questions, a quick path for one-file fixes where full grooming is disproportionate, dismissing an item without completion under a required reason (duplicate, out of scope, superseded, wontfix, blocked), marking an item done with an evidence trail and required summary, or initializing GitHub tracking infrastructure for a project. Stops when the item already has a plan or is blocked on missing information.

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

Activates Standard of Excellence enforcement for the current session. Load before starting any task to apply completion standards: finish the whole thing, fix the root cause, ship the complete working result. Blocks partial solutions, workarounds, deferred threads, and invented content limits when the permanent solve is within reach. Triggers: 'do the whole thing', 'boil the ocean', 'standard of excellence', 'finish it completely', before starting any implementation, refactoring, or multi-step task where partial output is a risk. Does NOT apply to: read-only queries, one-line typo fixes, pure knowledge questions, or single-output summarize requests.

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

Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".

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

Find failing PR checks, inspect logs or external check links, and apply focused fixes

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

Run a high-thoroughness end-to-end implementation loop using clean worker worktrees, per-slice planning, implementation, explicit review/fix iteration, orchestrator integration, and final commit/PR drafting. Use when the user explicitly wants a Ralph/Wiggum-style loop, autonomous multi-agent execution, a delegated feature/bugfix carried from confirmed scope through review-ready completion, or RFC-driven implementation that should be reviewed, bumped to In Progress, decomposed into phases, and executed through nested sub-loops. Supports Codex subagents by default and external CLI workers such as OpenCode when explicitly requested and available.

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

Orchestrate a named multi-skill loop such as /loop /review /fix until clean or blocked. Use when the user explicitly asks to loop skills, rerun a review/fix cycle, or says /loop with one or more skill names.

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

Resolve Problem: Use when user wants to "bugfix" or "fix" code or "resolve" a problem.

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

Guide for performing Node.js version upgrades in the Electron project. Use when working on the roller/node/main branch to fix patch conflicts during `e sync --3`. Covers the patch application workflow, conflict resolution, analyzing upstream Node.js changes, building, running the Node.js test suite, and proper commit formatting for patch fixes.

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

Guide for performing Chromium version upgrades in the Electron project. Use when working on the roller/chromium/main branch to fix patch conflicts during `e sync --3`. Covers the patch application workflow, conflict resolution, analyzing upstream Chromium changes, and proper commit formatting for patch fixes.

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

Conversion rate optimization audit — analyze a landing page, signup flow, or checkout funnel using the 5-layer CRO stack (technical performance, traffic quality, offer/pricing, design/layout, copy/messaging). Produces prioritized fix list with expected impact. Use when "CRO audit", "conversion audit", "why isn't this converting", "improve conversion rate", "landing page not converting", "optimize funnel", "signup flow audit", or any request to diagnose and fix conversion problems.

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

Run Squirrelscan from a coding agent to audit SEO, performance, security, accessibility, and agent-experience issues, then feed exact fixes into an agent repair loop.

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

Client-side initial access and social-engineering attack module. Use when the operator selects a human/client/browser/identity-delivery attack direction: ClickFix/FileFix, AiTM session phishing, OAuth device-code or consent abuse, Teams/helpdesk social engineering, HTML/file delivery, QR/mobile handoff, legacy HTA/OLE/Office paths. This is an Attack module: own the chain until host shell or remote interactive foothold. Credential/token/session are intermediate results, not the stop condition. If endpoint AV/EDR/AMSI/application-control blocks an otherwise-valid client execution path, the operator may temporarily select /edr-bypass and then resume this phishing chain until shell.

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

Systematic root-cause isolation and minimal fix proposal for software bugs.

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

Fix a GitHub issue end to end -- read it, reproduce, patch, add a regression test, verify, and open a PR. Use when given an issue number or URL in this repo.

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

Comprehensive Playwright E2E testing skill combining planning, generation, and healing. Trigger: When writing, debugging, or planning E2E tests, working with *.spec.ts files, Playwright config, test fixtures, or when asked to create/fix/plan browser tests.

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

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.

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

Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. Use when the task involves `improve Core Web Vitals`, `fix LCP`, `reduce CLS`, `optimize INP`, `page experience optimization`, or `fix layout shifts`.

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

Use when the user asks 'is my site secure', 'run a security audit', 'check for vulnerabilities', 'was my site hacked', or 'fix the vulnerable plugins'. Runs the Respira security audit, reads its indicators, coverage and known vulnerabilities honestly, never calls a partial scan clean, and fixes what it finds one approved step at a time.

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

Use when the user says 'fix my catalog for ai', 'improve my ai readiness score', 'get my catalog to 90', or 'my products keep getting rejected by google'. Runs an ordered fixlist that writes the missing alt text, descriptions, brands, GTINs, and category mappings, snapshotting before each change.

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

Read GitHub Actions CI for the current branch or open PR, triage failing checks, reproduce locally, and fix scoped issues until green. Use whenever the user mentions CI failures, red checks, failed pipeline, GitHub Actions, merge blocked, fix the build, babysit CI, gh run failed, ruff/ty errors, failing pytest, example run failed, or asks to check CI on this branch — even if they only paste a log snippet. Also use after implementing a feature when tests, lint, or typecheck might have broken.

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