'defects' 검색 결과

Construction quality control workflow automation. Manage QC inspections, track defects, generate NCRs, and ensure specification compliance throughout the project.

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

AI-powered construction defect detection using computer vision. Identify cracks, spalling, corrosion, and other defects in concrete, steel, and building components from images and video.

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

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

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

End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.

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

Identifies bug-introducing commits using SZZ-style analysis based on bug-fixing commits, commit history, and code blame information. Use this skill when you need to trace bugs back to their origin, identify which commits introduced bugs, analyze bug-fix commits to find root causes, perform software repository mining for bug analysis, or conduct empirical studies on software defects. Triggers when users ask to find bug-introducing commits, identify when a bug was introduced, trace bug origins, perform SZZ analysis, or analyze bug-fixing commits.

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

Review a GitHub pull request by number or URL for evidence-backed defects. Not for reviewing local uncommitted changes.

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

Think and work like an expert Materials Physicist. Use when a task calls for Materials Physicist judgment. Reasons from band structure, defects, strain, and Landau order parameters; integrates HRXRD/RSM, ARPES, TEM/4D-STEM, van der Pauw transport, and SQUID/MOKE with Materials Project/VASP while treating matrix-element ARPES artifacts, substrate-dominated GIXRD, contact-resistance Hall errors, and DFT gap overclaim as first-class failure modes.

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

Analyze escaped defects and test suite health through blameless postmortems. Covers bug pattern analysis, test suite health reviews, 5 Whys root cause analysis, process improvement cycles, and postmortem/retro meeting templates with action item tracking. Use when: "QA retro," "escaped bugs," "postmortem," "quality incident," "defect analysis," "improvement cycle." Not for: live release go/no-go decisions — use release-readiness. Not for ongoing metric dashboards — use qa-metrics. Not for reviewing existing test code quality — use ai-qa-review. Related: qa-metrics, test-reliability, test-strategy.

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

Review and upgrade MetaX model support against a target vLLM revision and installed MACA components, recursively including model-dependent attention and kernels. Establish quantization and cache differences, preserve upstream structure, and distinguish shared upstream bugs from adaptation defects. Use for model support work, not standalone monkey-patch or registry audits.

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

Challenges a recommendation, design, large change, or any artifact submitted for hard review (spec, proposal, policy, plan) across 5 dimensions (consistency, completeness, actionability, alignment, risk), from the standards of a named senior expert in the artifact's domain and ideally from a fresh context or a different model. Searches assuming defects exist and reports only those that survive evidence. Panel mode runs several independent lenses in parallel on a release candidate, verifies every finding against the current head, and routes confirmed ones to file owners. Use before shipping a significant recommendation, design, large branch, or multi-agent release, or when asked to tear something apart, be brutally honest, or poke holes in it.

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

Refuses "flaky" as a diagnosis. Turns an intermittent failure into a reproduction by isolating it from the environment, naming the variable that controls it, forcing that variable, and measuring before and after with enough runs to count. Separates real defects from environment contention with evidence, and never retries to green or widens a threshold. Use when a test, performance check, or deploy step fails intermittently or passes on rerun.

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

Audits an existing rendered interface or frontend diff for hierarchy, content clarity, interaction states, accessibility, responsive behavior, visual consistency, performance-sensitive UI patterns, and anti-generic design defects. Use for a UI/UX review, redesign audit, screenshot review, pre-release visual check, or design-system consistency pass. Not for building a new interface from scratch or for backend-only review.

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

Diagnose and fix mini-program failures through reproducible, evidence-driven root-cause analysis across source, state, asynchronous timing, caches, mock data, build versions, platform behavior, devices, cloud calls, and external services. Use when users report white screens, crashes, stale or jumping values, missing data, intermittent behavior, permission failures, performance stalls, device-only defects, API or cloud-function errors, source-versus-build mismatches, or regressions whose cause is not yet established. Freezes the observation environment, ranks competing hypotheses, runs discriminating checks, creates a failing regression test before repair, covers analogous states, and never hides a known failure with longer waits, swallowed errors, forced success, or cosmetic patches.

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

amazon-listing-doctor是由buluslan（公众号：新西楼.AI）研发的亚马逊Listing质检Skill，他会基于 CDQ算法 / A9 / COSMO / Alexa 四大底座知识，来给Listing进行全身体检和打分，输出一份诊断报告，帮你揪出"流量加倍、弯道超车"的机会点。 更多跨境电商 AI 实战内容，请关注公众号「新西楼.AI」。 Audits Amazon listing health across CDQ / A9 indexability / COSMO intent-coverage / Alexa discoverability, plus 2026 compliance rules (title 75-char, highlights 125-char, image defects). Pure diagnosis, zero dependencies, works offline. Trigger whenever the user mentions checking/auditing/scoring/diagnosing an Amazon listing's quality — in any language; 中文卖家说 listing 体检 / 质检 / 打分 / 诊断 / 健康度 / 质量分 时同样适用。

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

Audit OpenClaw frontend code and rendered interfaces for Carapace drift, token misuse, primitive reimplementation, accessibility problems, responsive defects, and off-brand copy. Use for design reviews, compliance checks, or scheduled audit-and-fix workflows.

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

Use when authoring or reviewing a SKILL.md or agent .md and you need to detect and fix the four most common frontmatter defects — echoed or truncated triggers, tools written as a YAML array instead of a comma-separated string, a description outside the 1-1024 character bound, and a missing "Use when..." clause.

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

Analyze specific pytest failures using authoritative contracts and a cited product/test evidence chain. Use for failing test names or pytest output, distinguishing product, interface, oracle, and harness defects without automatically changing expectations or forcing an architectural redesign.

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

Review a code change for correctness-maintainability defects not owned by a narrower security/performance/accessibility perspective. Use for an independent quality perspective on a defined change set.

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

Review a change for security defects such as secret exposure, injection, authentication/authorization failures, unsafe deserialization, and dependency risk. Use for an independent security perspective on a defined change set.

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

Trace bugs, CI failures, and unexpected behavior from reproduced evidence to a causal mechanism and governing contract. Distinguish product, architecture, test-oracle, and harness defects; investigate intermittent failures with controlled experiments and report unresolved evidence explicitly.

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

Builds, revises, restyles, and critiques deliberate, editable Feishu / Lark whiteboards from content, references, existing SVGs, or live boards. Use for whiteboards, infographics, diagrams, system maps, timelines, decision boards, posters, and visual explainers that need factual fidelity, strong hierarchy, intentional composition, and evidence-based review rather than a generic grid of equal cards. Routes creation, revision, and critique through separate playbooks; commits to a content-and-design contract before drawing; validates deterministic SVG defects; renders and inspects the actual artifact; and uses an independent final reviewer for material deliveries.

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

Run an independent read-only Kimi review over the current working tree or a branch diff. Use when the user wants a second reviewer for defects, regressions, or implementation risks, not edits.

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

"Apply Lean and Six Sigma principles to eliminate waste and reduce process variation. Use this skill when the user needs to improve operational efficiency, identify the seven wastes (TIMWOOD), run DMAIC improvement projects, or streamline workflows — even if they say 'our process is too slow', 'where are we wasting resources', or 'how do we reduce defects'.".

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

Conduct structured root cause analysis using Ishikawa (Fishbone), 5 Whys, and Pareto methods. Suitable for production incidents, quality defects, customer complaints, and recurring operational problems. Use when problems recur or when initial fixes do not resolve the issue. Do not use for one-time, obvious fixes or strategic decision-making.

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