'defects' 검색 결과

Reproduce, isolate, patch, and verify defects with explicit expected-versus-observed behavior.

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

Explore a feature or CLI, reproduce defects and record bounded findings. Use for "explore X", "find issues with X", or the exploration stage of feature- pipeline; standalone runs return findings without automatically expanding scope.

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

Explore a feature or CLI, repair verified defects, review adversarially, and leave one existing or new PR ready for its authorized reviewer. Use for "explore X", "test and ship X", "run the pipeline on X", "stress-test X", or "take X through the full pipeline" when exploration and integration matter. Supports lean autonomous, structured economy (default), and explicit hard-gated runs. Routine checkpoints do not require user approval; actual founder, L4, security, schema and merge gates always apply. Not for a one-file edit with no exploration need. Uses scripts/state.sh for resumable checkpoints.

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

Pre-launch quality gate for games: audit rendering and memory performance against platform budgets, run QA for crash-causing defects and platform certification blockers, review accessibility for CVAA and platform compliance, test security against cheating and save tampering.

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

Use this skill when writing acceptance criteria for Salesforce features, structuring UAT test scripts from user stories, classifying defects found during UAT, or planning regression testing before a Salesforce release. Trigger keywords: UAT, user acceptance testing, test script, acceptance criteria, defect classification, regression testing, test plan, test case. NOT for Given/When/Then AC syntax — use admin/acceptance-criteria-given-when-then. NOT for the per-case field schema and AC-to-case decomposition — use admin/uat-test-case-design. NOT for automated Flow or Apex test coverage — use flow/flow-testing. Also covers: UAT plan record, sandbox selection for UAT, pre-UAT environment checklist, sandbox email deliverability for testers, test-user personas, negative and bulk coverage, defect triage categories, go/no-go sign-off, quick-deploy window.

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

Trigger when: (1) the user mentions "noise", "slop", "frame audit", "video review", "letter spacing", "padding intrusion", "frame extract", "naive arrow", or Korean equivalents (노이즈, slop, 프레임 검수, 글자 깨짐), or (2) after rendering a new or modified Manim scene, or (3) the user asks to review an mp4 in `media/videos/` or `~/Downloads/`. Post-render audit workflow for Manim 1080p60 videos. Extracts keyframes via ffmpeg, inspects them through Claude Code's Read tool, and classifies any defects into four standing categories (naive arrow / padding intrusion / glyph kerning drift / frame-order error). Catalogues 12+ verified incidents across the four GEODE scenes so each is caught the first time, not rediscovered. The companion authoring skill is [[manim-scene-craft]].

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

Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.

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

Review code changes for correctness defects, regressions, security risks, data-integrity problems, concurrency hazards, and missing meaningful tests. Use for pull requests, branches, commits, patches, or working-tree reviews; do not use for implementation unless the user separately requests fixes.

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

Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.

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

Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.

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

Run a governed R&D session — diamond 1 of the double diamond, which defines the problem and names which fan-out artifacts are warranted. Use when the operator pastes external material and says "consider this for gzkit", asks "is there something here gzkit is missing or could improve on", opens an exploratory design discussion whose outcome is not yet known, or asks why a class of defects keeps recurring and how the issues carrying it should be restructured. Ends at a six-row disposition map and operator sign-off; produces no fan-out artifact itself. Operator-invoked only.

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

Builds a DRAFT data dictionary from a schema export, table definition, sample rows or a partial existing dictionary: one row per field with the name as stated, type as stated or observed, meaning quoted from the documentation supplied, owner, allowed values, and UNKNOWN wherever no source defines the field, plus a gap list for the data owner. Never infers a definition from a column name. Use when the user asks to "build a data dictionary for this table", "document these columns", "what does each field mean", "turn this schema export into a dictionary" or "fill in the field definitions from these documents". Do not use for profiling values or finding patterns in the data, use dataset-insight-pack instead; for metric definitions, use kpi-definition-sheet; for logging data defects, use data-quality-issue-log. Drafts for human review; never approves, authorises or signs off.

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

Comprehensive Lean Six Sigma consulting skill supporting all belt levels (White Belt to Master Black Belt). Use this skill for DMAIC/DMADV project execution, Lean waste elimination (VSM, 8 Wastes/DOWNTIME, 5S), statistical analysis (process capability Cp/Cpk, control charts, hypothesis testing), and Six Sigma training/education. Triggers include "improve process", "reduce defects", "sigma level", "DMAIC project", "value stream mapping", "Kaizen", "process capability", "control chart", "root cause analysis", "5 Whys", "Fishbone diagram", "FMEA", "DOE", or requests involving process improvement methodologies.

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

Upscale and prepare a selected video parent for delivery while preserving provenance and checking that enhancement did not create new defects.

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

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.

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

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

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

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.

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

Review a change, module, or surface for exploitable defects — trust boundaries, authn/authz, injection, secret exposure, filesystem and network reach, dependency risk. Use when the user asks for a security review, audit, or vulnerability check of concrete code. Not for general code review, lint, or compliance paperwork.

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

Summarize existing QA criteria, cases, evidence, defects, limitations, authorization, and verdict without mutation.

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

Assess release readiness from applicable criteria, all current defects, risks, limitations, and recorded human decisions without approving release.

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

Select traceable regression coverage from change impact, affected risks, criteria, dependencies, and prior defects rather than execution convenience.

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

Find the earliest decisive failure in an agent run trace and propose an evidence-backed targeted repair. Load when a run failed, results are wrong, or the user asks what went wrong in an agent session. Also triggers on "localize the fault", "first incorrect step", "debug this run", "trace attribution", "why did the agent fail", or after run-trace captures errors. Pairs with debug-and-fix for code defects and dynamic-routing for plan faults.

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

The Platform List: Arman's own register of large platform-level work he chose not to start yet. Use when the reminder hook says a row is due, when Arman says to add, snooze, kill, or finish a row, when you own a row, or when you think something belongs there. NOT for ordinary tasks, defects, or handoffs.

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

Diagnostic method for any bug, failure, regression, flake, or slowdown. Use before proposing a fix: something is broken, throwing, not saving, not showing, or 'worked yesterday'; on 'debug this' or 'find the root cause'; and immediately after a fix attempt did not work.

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