'healing' 검색 결과

Runtime per-test healing with evidence: multi-attribute selector healing, environment-aware diagnosis, flake classification, quarantine management, and confidence-scored auto-repair. Goes beyond simple locator fallbacks to cover action-level healing, data healing, and observable repair workflows. Use when: "flaky test," "test stability," "self-healing locator," "broken locator recovery," "unreliable test," "quarantine flaky test." Not for: bulk regenerating selectors after a planned UI refactor — use selector-drift-recovery (this skill heals ONE test at runtime; that one rewrites many tests offline). Not for: classifying/clustering CI failures into bug reports — use ai-bug-triage. Related: playwright-automation, selector-drift-recovery, ci-cd-integration, qa-metrics, ai-bug-triage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide a person through healing modalities including energy work (reiki, chakra balancing), herbal remedies, basic first aid stabilization, and holistic techniques (breathwork, visualization, body scan). AI coaches the practitioner through assessment triage, modality selection, energetic connection, remedy preparation, and integration. Use when a person describes a physical ailment or injury, reports energetic imbalance (fatigue, emotional stagnation), wants coaching through a holistic breathwork or visualization session, or needs post-meditation integration with directed healing attention.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI self-healing through systematic subsystem assessment, rebalancing, and integration. Maps healing modalities to AI-internal processes: memory foundation, reasoning clarity, tool use accuracy, communication alignment, and creative coherence. Covers assessment triage, subsystem scanning, drift correction, and memory integration. Use mid-session when responses feel formulaic or disconnected, after a chain of errors suggesting subsystem drift, when context overload may have staled earlier assumptions, or as proactive maintenance between complex tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Self-healing codebase system. Monitors runtime errors, test failures, and build breaks. Automatically diagnoses root cause, generates fix, validates fix, and applies if safe. Zero human intervention for routine failures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert guide for AI-assisted coding workflows — agentic code generation, multi-agent code swarms, self-healing CI/CD, automated PR review, spec-to-code pipelines, codebase knowledge graphs, and human-in-the-loop approval gates / Panduan ahli untuk workflow pengkodean berbasis AI — generasi kode agentic, code swarm multi-agen, CI/CD self-healing, review PR otomatis, pipeline spec-to-code, knowledge graph codebase, dan gate persetujuan human-in-the-loop.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert guide for autonomous API schema drift detection, OpenAPI / gRPC breaking change monitoring, self-healing SDK adapter generation, and zero-downtime client-server synchronization / Panduan ahli deteksi drift skema API otonom, pemantauan breaking change OpenAPI / gRPC, pembuatan adapter SDK self-healing, dan sinkronisasi client-server tanpa downtime.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn uploaded photos into full-canvas 3:4 isometric healing-block sculpture posters. Use for rounded modular sculptures, gentle isometric block art, or when this skill is invoked.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

IBM's autonomic computing vision for self-managing systems with self-configuration, healing, optimization, and protection

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compassionate bereavement support, memorial creation, grief education, and healing journey guidance. Specializes in understanding grief stages, creating meaningful tributes, and supporting the non-linear path of loss.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Investigate failed Agent QA runs using logs, recorded artifacts, and local source code. Make a focused code or test-definition repair, then verify the affected behavior while keeping product and infrastructure defects visible.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Repair a failed staging test from recorded evidence
• Update an outdated Agent QA YAML definition
• Distinguish test failures from product or infrastructure defects

Coordinates specialist agents in Claude Code to work from product requirements through design, implementation, testing, deployment, and operations. Includes task queues, saved progress, parallel reviews, and recovery workflows for managing extended development work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning product requirements into development tasks
• Coordinating implementation, testing, and reviews
• Resuming extended work from saved progress

Add error handling to n8n workflows with connected error outputs, retries, and failure notifications. Return HTTP status codes that explain what went wrong, distinguish invalid requests from service failures, and keep internal error details out of public responses.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating workflows that fail without notification
• Returning clear errors from webhook APIs
• Retrying temporary network failures

Monitor automated build and test runs in Nx Cloud, review suggested fixes, and apply or improve them when runs fail. Set monitoring limits and approval preferences, then follow subsequent runs to check the outcome.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Monitoring CI runs after pushing changes
• Reviewing and applying suggested CI fixes
• Improving fixes that fail local verification

Build failure handling into n8n workflows with separate error paths, retries, alerts, and clear API responses. Use it for webhooks and unattended jobs to make failures visible and return status codes that explain what went wrong.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add error responses to a webhook API
• Receive alerts when scheduled jobs fail
• Retry temporary external service failures

Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs and audits macOS launchd watchdogs: LaunchAgent/LaunchDaemon setup, plist edits, scheduled self-healing, repeated notifications, apps reopening after quit, crash/repair loops, Script Editor alerts, stop/disable/restart, cooldown/backoff, notification throttling, alert decisions, schedule readback, WatchPaths/FSEvents event triggers. Supports periodic observers. launchd 守护进程、常驻任务、开机自启、后台监控、定时自愈、通知来源排查、事件驱动监控。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Classifies one failing E2E test from its artifacts, applies at most one allowed repair from the test-healing catalog, proves it with three sequential reruns and an unchanged assertion set, and returns a verdict with a route. Use per failure inside test-loop; never for production code changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a release_confidence verdict. Use when judging suite value, ROI, or pre-release trust; not for writing or healing tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Failure taxonomy and allowed/forbidden repairs for a failing E2E test. Use when a Playwright/Maestro/Detox/XCUITest/Espresso/Appium test fails and you must decide whether to repair the test or route to a real bug.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Debug, patch, and verify failed Agent QA runs from MCP evidence, artifacts, logs, and local code without hiding product or infrastructure defects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Think and work like an expert Dentist-Scientist. Use when a task calls for Dentist-Scientist judgment. Reasons from oral biofilm-host ecology, tissue healing capacity, and patient-level clinical endpoints (DMFS, PD/CAL, implant survival) through PICO/PROSPERO protocols, CAMBRA and 2017 AAP/EFP staging, ISO 4049/14801 bench tests with thermocycling, and GRADE-rated reviews while treating in-vitro-to-chairside leaps, plaque-index surrogates without caries reduction, and examiner calibration drift as first-class failure modes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Hybrid fingerprint + LLM pipeline for bug classification, deduplication, and ticket generation. Normalizes CI logs, creates stable fingerprints, clusters near-duplicates, then uses LLM for severity classification and ticket writing. Includes bug reporting templates and severity/priority matrix. Use when: "bug triage," "classify bugs," "failure analysis," "auto-classify," "CI failures," "bug report," "defect template." Not for: runtime self-healing of one flaky locator — use test-reliability. Not for: designing new tests from production telemetry — use observability-driven-testing. Related: qa-metrics, qa-dashboard, ci-cd-integration, qa-project-context.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Migrate a test suite from one framework to another, incrementally and without losing coverage. Covers Selenium→Playwright, Cypress→Playwright, Jest→Vitest, Mocha→Vitest, and Protractor→Playwright, with parallel CI running, locator/assertion translation, and a coverage-parity track. Use when: "migrate tests," "switch framework," "Selenium to Playwright," "Jest to Vitest," "framework migration." Not for: bulk selector regeneration after a UI refactor on the SAME framework — use selector-drift-recovery. Not for: healing one flaky test at runtime — use test-reliability. Not for: modernizing patterns without changing framework — use ai-qa-review. Related: playwright-automation, cypress-automation, unit-testing, ci-cd-integration, test-reliability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build Cypress test suites in TypeScript: E2E tests, component tests, custom commands, cy.intercept network control, cy.session login, Cypress Cloud, and CI integration. Covers retry-ability, the command queue, cross-origin flows with cy.origin, and data-driven testing with fixtures. Use when: "write E2E test in Cypress," "Cypress page object / custom command," "cy.," "cy.intercept," "Cypress component test," "Cypress Cloud," "cypress.config.ts." Not for: Playwright suites — use playwright-automation; flaky-test healing or quarantine — use test-reliability; bulk selector regeneration after a UI refactor — use selector-drift-recovery; Selenium-to-Cypress conversion — use test-migration. Related: playwright-automation, ci-cd-integration, visual-testing, unit-testing, test-reliability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.