588건 · 관련도순
Load when diagnosing a bug, exception, regression, wrong result, failing flow, or unknown root cause in repository code using callers/callees, execution flows, recent changes, and impact analysis; not for implementing a known fix without investigation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
4-phase root cause debugging: understand bugs before fixing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bring past diagnoses to a bug before fixing it, record the new root-cause hypothesis, and close it as confirmed or refuted once the fix is verified. Use when a bug could come from more than one layer, or looks like something seen before.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use after substantial web projects or repeated design defects to convert evidence into reusable skill improvements through root-cause analysis, regression scenarios, and controlled proposals without silently changing the core OS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use as an independent design-review pass after rendering a website; evaluates macro, meso, micro craft, applies the Design Quality rubric, identifies root causes, and prioritizes changes without defending the implementation intent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Repair and triage guide for the NV oOS PHPUnit test suite — Docker test environment (incl. cross-worktree one-off runners), CI log triage, and 71 recurring root-cause patterns (hook resets, singleton interference, WP_Error envelope drift, coverage-manifest drift, preset-accounting gaps, and more — see the patterns section). Covers the cluster-by-cluster PR workflow against alpha-working and validation gates. Use when fixing failing PHPUnit tests, triaging CI logs, repairing test drift, deciding between a production fix and a test fix, or starting a new fix cluster.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix red CI or set up GitHub Actions end to end: read the failing run, find the root cause, patch and validate the workflow, push only after GO, and watch the run go green on the pushed commit. Use for "CI is red", "the build fails on GitHub", "set up CI for this repo", "fix the workflow".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a GitHub issue into a tested fix on a branch with an open PR: read the issue as the contract, find the root cause, write the failing test first, fix, prove it, review the diff against the issue, push and open the PR only after GO. Merging stays with pb-ship. Use for "fix issue 42", "bug fix from this issue", "turn this issue into a PR".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reflection-first problem solving methodology for Convex development. Use before implementing any solution to ensure proper root cause analysis, 98% code confidence, and minimal change scope.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use immediately after RBR confirms a root cause, or after any confirmed finding from security-audit-lens, legacy-investigation-lens, a scan skill, or a Critical/Required code-review finding, before considering the finding complete. Checks whether the confirmed defect is one instance of a structurally identical pattern elsewhere in the same file family, workflow, or business-domain area, and folds in or explicitly defers every other instance found. Mandatory for Architect — not an optional lens the agent judges when to apply.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "identify web application vulnerabilities", "explain common security flaws", "understand vulnerability categories", "learn about injection attacks", "review access control weaknesses", "analyze API security issues", "assess security misconfigurations", "understand client-side vulnerabilities", "examine mobile and IoT security flaws", or "reference the OWASP-aligned vulnerability taxonomy". Use this skill to provide comprehensive vulnerability definitions, root causes, impacts, and mitigation strategies across all major web security categories.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
4-phase root cause debugging: understand bugs before fixing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a pipeline step fails, an error occurs, schema validation fails, ffmpeg crashes, or API returns an error. Diagnose the root cause and attempt automatic recovery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries. Use when the user reports an anomaly, asks "why did X change?", or needs root-cause analysis for a trend, funnel, retention, stickiness, or lifecycle metric.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix failing ToolUniverse tools by diagnosing test failures, identifying root causes, implementing fixes, and validating solutions. Use when ToolUniverse tools fail tests, return errors, have schema validation issues, or when asked to debug or fix tools in the ToolUniverse framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate errors, incidents, or product ideas using both internet research and repo-wide codebase research, then propose a concrete changeset plan with clarifying questions before any implementation. Use when a user asks to investigate, root-cause, or plan changes, or when an Issue or PR is referenced and needs a plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured bug diagnosis and fixing workflow — reproduce, diagnose root cause, apply minimal fix, write regression test, and scan for similar patterns
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.