Results for “fix”

Apply comprehensive Python testing strategies using pytest, including TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

Provides Python testing strategies using pytest, covering TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

Diagnose and fix a bug through a disciplined reproduce, isolate, diagnose, fix, verify loop driven by evidence and one hypothesis at a time — not guesswork.

Root cause analysis skill — diagnose bugs systematically before fixing. Iron Law: no fix without a confirmed hypothesis. Uses scope lock, 3-strike escalation, and structured debug reports.

Diagnoses and fixes bugs in emergency mode with a maximum of two iterations, then commits, pushes, and creates a pull request.

Guides a structured root-cause investigation before any fix, covering reproduction, evidence gathering, hypothesis testing, and implementation with failing tests.

Guides implementing features and fixing bugs by writing failing tests first, then minimal code, with verification at each step.

Guides systematic debugging by investigating root causes before proposing fixes, with structured phases for analysis, hypothesis testing, and implementation.

Guides writing a failing test before production code, iterating through red-green-refactor cycles, and fixing bugs test-first.

Diagnose and fix oh-my-codex installation issues

Diagnose and fix oh-my-codex installation issues

Implements features, fixes bugs, and refactors code by orchestrating domain-specific skills, following existing patterns, and verifying tests and lint pass.

Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.

Diagnose and fix oh-my-claudecode installation issues

Investigating bugs via root cause analysis, reproduction steps, and impact assessment. Investigation-only — finds why bugs occur and where to fix them, no code. Use when a bug needs RCA before a fix.

Systematically repair a broken feature or module by scoping, tracing dependencies, diagnosing all issues, fixing them in order, and verifying end-to-end.

Guides systematic root-cause investigation before proposing fixes for any technical issue, with a four-phase process and red flags to avoid guessing.

Locates failing GitHub Actions checks on a pull request, fetches logs, summarizes failures, and proposes a fix plan for approval before implementing.

pytest Python testing framework. Covers fixtures, parametrize, and mocking. Use for Python testing. USE WHEN: user mentions "pytest", "python test", "fixture", asks about "@pytest.fixture", "@pytest.mark.parametrize", "conftest.py", "pytest coverage", "python unit test" DO NOT USE FOR: JavaScript/TypeScript - use `vitest` or `jest`; Java - use `junit`; E2E web tests - use `playwright`; Load testing - use locust

Automates end-to-end QA: starts the app, exercises screens and API endpoints, verifies functionality and design quality, runs domain analysis, and fixes issues found.

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.

Systematically QA test a web application and fix bugs found. (gstack)

Systematically QA test a web application and fix bugs found. (gstack)

Sets up Microsoft Testing Platform hot reload to iterate fixes on failing tests without rebuilding, covering package installation, environment configuration, and the iterative workflow.

Walks a running app across routes, states, and interactions to find real bugs, then root-causes, fixes, adds regression tests, and verifies each fix before committing.

Writes Python tests with pytest, including fixtures, parameterization, and plugins for coverage.

Guidelines for upgrading Expo SDK versions and fixing dependency issues

Diagnosing and fixing bimodal matching score distributions in MaxFuse

Processes a PR's review comments (Copilot or human), classifies them, applies the fixes that belong, replies to each thread, and pushes. Use whenever the user says "address the review", "fix what Copilot said", "handle the comments", mentions Copilot already reviewed a PR, or passes a PR number/URL with pending reviews — or in Spanish "revisá los comentarios", "arreglá lo que dijo Copilot", "atendé el review".

Diagnose and fix failing CircleCI builds quickly and safely. Use when users ask to investigate failed CircleCI jobs, triage flaky pipelines, identify root causes from logs, and implement minimal fixes in configuration, test setup, or build-related code paths.

Reproduces failures, gathers evidence, tests hypotheses, fixes root causes, and adds regression coverage.

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

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

Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

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

Fix F821 undefined name errors for optional dependencies using TYPE_CHECKING