'debug' 검색 결과

Routes quality checks to the appropriate skill, covering code review and fixes, debugging, security checks, acceptance testing, AI response evaluation, and interface reviews. It also directs requests for validating phase outputs or reviewing plans across AI systems.

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

• Review code and fix reported issues
• Investigate feature failures and errors
• Check security and acceptance testing

Investigate errors and unexpected behavior through reproduction, isolation, diagnosis, and a proposed fix. Receive a structured report covering the root cause, necessary code or configuration changes, and suggested tests to prevent the issue from returning.

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

• Investigate an error message or stack trace
• Diagnose behavior that differs between staging and production
• Trace a failure that appeared after deployment

Find and load the appropriate skill for an agent working inside OpenRig. This index maps situations such as recovery, handover, debugging, and planning to relevant guidance, with commands that retrieve content matching the installed CLI.

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

• Find relevant guidance when an agent first starts
• Locate skills for recovery or seat handover
• Find procedures for debugging or implementation planning

Coordinate temporary agents for code exploration, independent implementation tasks, verification, reviews, or complex debugging. Define self-contained assignments, run independent work in parallel, and check returned evidence before combining the results.

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

• Delegating codebase exploration to inform a decision
• Running independent implementation tasks in parallel
• Getting an independent check of a high-risk change

Investigate Python script failures by capturing regular output, error details, and exit codes. Log the working directory and resolved file paths to expose missing files, permission problems, missing modules, or differences in automated execution.

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

• Investigating Python failures with unclear error messages
• Checking paths when file reads or writes fail
• Debugging scripts that fail only in automation

Debug PowerPoint generation with python-pptx, a Python library for presentations. Follow a sequence of installation checks, minimal tests, error logging, and fixes for tables and charts, then inspect the generated slides.

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

• Diagnosing errors in PowerPoint generation
• Fixing table and chart code
• Saving detailed error logs

Plan a browser game's architecture before coding. Choose an engine, separate game rules from rendering, and define input, assets, menus, saves, debugging, and performance checks within a shared design.

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

• Choose an engine for a 2D or 3D browser game
• Separate game state from rendering responsibilities
• Plan input mappings and asset organization

Test and debug rendered web apps by reproducing interaction bugs, checking layouts and console errors, making focused fixes, and validating again. Results include screenshots, observed state changes, and a QA report explaining coverage and remaining gaps.

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

• Reproducing and fixing broken UI interactions
• Checking desktop and mobile layouts
• Investigating blank pages and console errors

Set up a repeatable build, launch, and debugging workflow for macOS apps using Xcode or SwiftPM, Swift’s package manager. A project script handles relaunching, connects to the Codex Run button, and supports logs and process checks.

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

• Build and launch a macOS app with one script
• Connect a project to the Codex Run button
• Investigate build errors or startup failures

Build and debug Python agents with Swarms, a framework for coordinating multiple AI agents. Covers tool connections, saved memory, autonomous execution, and workflow choices such as sequential steps, parallel work, specialist delegation, and combined answers.

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

• Building an agent that calls Python tools
• Coordinating sequential or parallel agent workflows
• Saving agent memory across restarts

Inspect and control live Chrome pages to investigate display problems, console errors, failed requests, and slow loading. Capture screenshots, automate page interactions, and record performance traces to identify where delays or layout shifts occur.

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

• Investigating page errors and failed network requests
• Finding causes of slow loading and layout shifts
• Capturing screenshots of pages or individual elements

Design specialized assistants that work with their own separate context. Define responsibilities, delegation conditions, working steps, and report formats for reusable subagents handling verification, debugging, security audits, or code reviews.

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

• Creating an independent agent to verify completed work
• Defining a debugging specialist
• Creating a security audit agent

Add or debug web animations with GSAP, from entrance effects to scroll-driven sequences. Coordinate timing across multiple elements, adjust motion, and address rendering performance and cleanup when using animations in React.

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

• Animate a hero section with staggered entrances
• Build scroll-driven animated sections
• Coordinate navigation, headings, and buttons

Guide AI agent development from requirements and project setup through implementation, behavior evaluation, deployment, and monitoring. Provides coding rules, debugging steps, and links to specialized skills so each phase follows a defined process.

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

• Planning an agent's requirements and architecture
• Running and debugging an agent locally
• Evaluating responses and tool use before deployment

Guide Nexent backend design, implementation, debugging, and review across database schemas, FastAPI endpoints, services, and configuration. Check existing interfaces, consult references for each affected layer, and verify successful and failed behavior while preserving public contracts.

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

• Design relational tables, keys, and indexes
• Implement or review FastAPI endpoint changes
• Debug backend services and database access

Route GitHub Agentic Workflows requests to the appropriate task guide. It selects prompts for design, creation, updates, debugging, or upgrades, with additional guidance for specialized tasks and repository-specific instructions when available.

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

• Starting workflow design through an interview
• Selecting guidance for creating or updating workflows
• Finding debugging or upgrade procedures

Capture MSBuild execution records as binary logs during .NET builds, tests, packaging, publishing, or restores. It explains unique filenames, PowerShell quoting, and file checks so logs remain available for later failure or performance analysis.

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

• Saving logs before investigating a build failure
• Keeping separate logs for Debug and Release builds
• Choosing log filenames for CI artifact uploads

Investigate .NET app crashes on Apple platforms by converting runtime addresses in .ips logs into function names, source files, and line numbers. It locates matching debug symbols and supports retrieving logs from connected iOS devices.

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

• Investigating .NET MAUI or Mono crashes on Apple platforms
• Resolving runtime addresses to source files and line numbers
• Retrieving crash logs from a connected iPhone

Design error recovery for gh-aw workflows, including failed installations and API calls. Define retry limits, increasing wait times, error categories, and debug logs to handle temporary failures and prevent endless retries.

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

• Add bounded retries to network operations
• Plan recovery from installation failures
• Handle GitHub API rate limits

Inspect Kiln’s interface in a real browser, capture screenshots, and run or debug end-to-end tests that check complete user flows. A sandbox with sample project data provides populated screens for checking UI changes.

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

• Checking the appearance and behavior of a changed screen
• Capturing screenshots of Kiln
• Running or debugging the existing end-to-end test suite

Debug local Rust services in this repository by starting the crate's binary with debug logging, tailing service logs, and using those logs to answer runtime questions. Use when investigating service startup, runtime behavior, errors, or logs for a Rust binary in a crate.

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

Deterministic debugging with rr record-replay. Use when debugging crashes, ASAN faults, or when reverse execution is needed. Provides reverse-next, reverse-step, reverse-continue commands and crash trace extraction.

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

DOCA version handling: detect the installed release and validate the four-way match across pkg-config doca-common, applications/VERSION, doca_caps --version, and bfver/mlnx-release on BlueField; reason about NGC tags; look up whether a capability exists on this release; diagnose build-vs-runtime drift. Load it alongside doca-debug when a symptom smells of version skew: "built but nothing on the wire", "undefined reference to a symbol the docs claim exists", "DOCA_ERROR_NOT_SUPPORTED at runtime", "what does latest mean for this tag", or "is my LTS still supported". Once all four sources match, the component's build / run workflow belongs to its own library, service or tool skill. Refuse install / package choice (doca-setup), per-library API questions (matching library skill), DOCA_ERROR_* taxonomy (doca-programming-guide), and the general debug ladder (doca-debug).

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

Use this skill when the user is doing hands-on DOCA Management programming against BlueField / ConnectX devices — standing up a management or representor context (doca_mgmt_dev_ctx / doca_mgmt_dev_rep_ctx), querying device caps (data-direct, caps-general), toggling congestion-control global status, modifying diagnostics-data, setting ICM quotas, or issuing a raw firmware command via doca_mgmt_raw_cmd with the right scope (CONFIGURATION / DEBUG_READ_ONLY / DEBUG_WRITE / DEBUG_WRITE_FULL). Trigger even when the user does not say "DOCA Management" — typical implicit phrasings include "fleet tool that walks every BlueField and reads device state", "toggle data-direct on a VF", "set an ICM quota per representor", "send a raw firmware command from C", "DOCA_ERROR_IO_FAILED from raw_cmd", or "fwctl ioctl is failing". Refuse and route elsewhere for mlxconfig direct operation, BFB / firmware reflash, streaming telemetry, doca_caps CLI snapshots, or DOCA install itself — those belong to other skills.

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