'bugs' 검색 결과

Per-toolkit hardening audit loop for NV oOS Pro tools. Systematically scans each addons/pro/includes/tools/<toolkit> (and its plugins/nvoos-content-graph-pro mirror) for the recurring production failure classes — unguarded shell calls that fatal on exec-disabled hosts, calls to nonexistent client methods, string-assuming parsing of provider responses that may be arrays, provider enum/service mismatches, metric/source column drift that silently returns 0, secondary-table denominator gaps, the Chart.js fixed-height loop, misleading native-source errors, and silent import truncation that reports partial writes as success — then fixes, tests (Docker PHPUnit), and validates (phpcs both standards) before moving to the next toolkit. Use when asked to audit a toolkit, review the X tools for similar issues, do the same for the other toolkits, or continue the toolkit audit loop. The first case study (document-generation) found 3 fatal bugs + 1 broken regex; the food-beverage pass added classes 5–9.

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

Review and implement WordPress query-cache usage on WP 6.9+, especially direct interaction with query cache groups now using salted cache helpers. Covers wp_cache_get_salted, wp_cache_set_salted, wp_cache_get_multiple_salted, wp_cache_get_last_changed, affected query groups like post-queries, term-queries, user-queries, comment-queries, site-queries, and why plugins should usually use WP_Query APIs instead of writing query cache entries directly. Use when optimizing expensive reads, persistent object cache behavior, or cache invalidation bugs.

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

Validates custom dotnet new templates for correctness before publishing. Catches missing fields, parameter bugs, shortName conflicts, constraint issues, and common authoring mistakes that cause templates to fail silently. USE FOR: checking template.json files for errors before publishing or testing, diagnosing why a template doesn't appear after installation, reviewing template parameter definitions for type mismatches and missing defaults, finding shortName conflicts with dotnet CLI commands, validating post-action and constraint configuration. DO NOT USE FOR: finding or using existing templates (use template-discovery), creating projects from templates (use template-instantiation), creating templates from existing projects (use template-authoring).

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

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

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

Trace BIRD routing-daemon behavior through the actual C source tree. Use for implementation questions, suspected upstream bugs, parser/keyword origins, filter instructions, protocol state machines, route attributes, birdc commands, stack traces, or BIRD 2 versus BIRD 3 source comparisons. Prefer a local checkout or exact upstream tag/commit and cite concrete files, functions, and revisions. Route config linting to bird-agent and active incidents to bird-troubleshooting.

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

Audits and fixes mobile accessibility across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including shared Compose UI and native hosts. Covers TalkBack/VoiceOver labels, roles, state, reading order, touch targets, text scaling, contrast and focus. Use for a11y audits, screen-reader bugs or accessible UI implementation.

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

Reviews mobile code for production bugs across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including KMP source-set and host API contracts. Covers lifecycle, concurrency, UI state and native boundaries with file:line evidence. Use for a code review, PR, project audit, quality check or /reis-mobile:review.

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

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

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

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

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

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

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

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing...

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

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

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

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

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

Systematically trace bugs backward through call stack to find original trigger

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

Validate at every layer data passes through to make bugs impossible

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

Expert en QA exploratoire v4 (tests systématiques, chasse aux bugs, preuves, rapports, régression)

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

When isolating and fixing unpredictable or complex software bugs.

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

Diagnose, fix, or validate SwiftUI animation and scroll behavior by temporarily instrumenting views with MotionEyes, capturing console traces over time, and comparing motion data to user intent or test expectations. Use when users report bugs such as wrong direction, premature fade, timing or easing mismatch, unexpected movement, missing movement, incorrect relative movement between views, scroll jumps, scroll restoration drift, content-offset desynchronization, or when they want to turn MotionEyes traces into focused assertions. Prefer XcodeBuildMCP log capture first and fallback to CLI log streaming; remove only agent-added MotionEyes instrumentation after validation.

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

Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the fastest proof path without making code edits.

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

Use when turning something that happened into something that makes the next run better - "write a retro", "record this paper cut", "this bug escaped verification", "make this an eval", "why do we keep hitting this", "did that change actually help", "scorecard", "what did we learn from that run", "lessons keep getting re-learned". Covers the six-step loop (capture, classify, convert, change, measure, retro), the repo artifact each step produces, and how escaped bugs become eval cases. Do NOT use to design or judge a single workflow experiment (see `workflow-experimentation`, which this loop feeds), to decide where to run work (see `dogfooding`), or to debug one failed execution in the moment.

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

Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.

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

Uses Microsoft RESTler to perform stateful REST API fuzzing by automatically generating and executing test sequences that exercise API endpoints, discover producer-consumer dependencies between requests, and Bul: security and reliability bugs. The tester compiles an OpenAPI specification into a RESTler fuzzing grammar, configures authentication, runs test/fuzz-lean/fuzz modes, and analyzes results for 500 errors, authentication bypasses, resource leaks, and payload injection vulnerabilities. ...

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

Provides binary exploitation techniques for CTF challenges. Use when you already have a vulnerable native target or service and need to turn memory corruption or low-level primitives into code execution or privilege escalation, such as buffer overflows, format strings, heap bugs,

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

4-phase root cause debugging: understand bugs before fixing.

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