1.5천건 · 관련도순
Monitor a GitHub pull request for review feedback, automated check failures, and merge readiness. Diagnose failures, fix problems caused by the branch, and retry likely temporary failures while continuing to watch for updates.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Diagnose unreachable or unhealthy OpenShell gateways and sandbox startup failures. Identify the underlying execution platform, then examine logs, authentication, certificates, and configuration with the matching tools to narrow down the cause.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Diagnose MSBuild failures from an existing binary build log. Inspect errors, settings, project references, and execution details to explain failures that console output alone does not clarify, including failures across multiple projects.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Assess an application against OWASP Top 10:2025 risk categories using Strix. Get findings backed by working exploit examples, organized by category, with clear explanations of what was tested and what remains unassessed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Validates skill files and registration consistency, then checks project tests and system health. Compares failures with recent changes to distinguish regressions, outdated tests, intermittent failures, and infrastructure issues, producing a report that tracks results over time.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Classify failures in CI, automated checks run during development, to distinguish code regressions, temporary infrastructure problems, security test failures, and inconsistent results. Record each failure's category, suggested next action, and attempt count in a structured report.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze failures in CI, the automated checks run during development. Identify the failing job and step, classify the likely cause, and suggest a small fix, continued monitoring, or human review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Identify agent failures that happen before any work starts by checking iteration counts, tool use, artifacts, and logs. Classify these incidents as pre-execution failures and guide investigation toward environment setup, initialization, and resource limits.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use when running existing project validation commands and fixing failures after code changes, including lint, type-check, unit/integration test, build, CI, or local script failures. Do not use when the task is to design or author new component/E2E tests; Chinese triggers include validation, check failures, fix failures, CI failures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
브라우저나 Electron에서 이미지가 저장되지 않거나 0 KB 파일로 내보내지는 문제를 조사합니다. 이미지 데이터 생성과 저장 경로를 나눠 원인을 찾고 수정합니다.
후보 코드를 로컬에서 검증하고 기준 버전과 비교합니다. 중대한 실패, 진단용 차이, 증거 부족을 구분해 보고하고 아직 확인하지 않은 CI 항목도 명시합니다.
Monitor selected GitHub Actions checks on an SGLang pull request until they pass on its latest commit. Diagnose failures, push small validated fixes, and retry only failed jobs within defined limits.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze Windows authentication logs for repeated password guesses against Remote Desktop services. Group failures by source IP and account, check for later successful logins, and produce a JSON report highlighting attack patterns and possible compromise.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Classify outstanding pull request CI failures, automated checks run on code changes, using logs and changed files. Produce JSON decisions recommending a rerun, a comment, or no action, and identify specific nondeterministic tests when evidence supports it.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Diagnose GKE TPU slice creation failures caused by shared nodes. Check slice status, partition labels, and monitoring data to identify conflicting resource groups, then provide resolution steps for the user to apply.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Helps AI agents recover from repeated failures by reviewing previous attempts, checking original sources, testing different hypotheses, and verifying results. It combines structured troubleshooting with performance review rhetoric modeled on large technology companies.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze agent runs that fail before any work begins. By checking execution counts, tool calls, outputs, and conversation logs, this skill classifies startup failures and directs investigation toward system setup, resources, or input processing.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate Pinot tests that fail intermittently in GitHub Actions. Use the skill to produce a report describing the evidence found and likely causes, helping explain failures that do not occur consistently.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Diagnose bugs, intermittent failures, and performance regressions through structured logging and reproduction. It ranks possible causes with confidence scores, tests competing explanations, and reports whether the evidence proves the cause or leaves the diagnosis incomplete.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose NCCL failures and adjacent training-pod failures on HyperPod GPU clusters (EKS or Slurm) — training hangs, AllReduce / collective-op timeouts, EFA or libfabric errors, rendezvous failures, EFA TCP fallback, /dev/shm or memlock issues, NCCL version mismatch across pods, container OOM / exit-137 / OOMKilled, GPU OOM (CUDA out of memory), CrashLoopBackOff / Pending pods, MASTER_ADDR DNS, NetworkPolicy blocking. Not for single-node hardware faults (→ hyperpod-node-debugger § G) or cluster-creation EFA / SSM failures (→ hyperpod-cluster-debugger § A / § F).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenClaw의 Gateway, 설정, 인증 정보 참조, 채널과 포트 문제를 읽기 전용으로 조사하고, 근거가 있는 진단 결과와 다음 조치를 정리합니다.
인공지능 에이전트의 문제를 지시, 기억, 도구 실행, 화면 표시 등 12개 계층에서 조사합니다. 코드와 로그를 근거로 원인을 정리하고 심각도에 따른 지적 사항과 수정안을 제시합니다.