'debugging' 검색 결과

Build Claude Code hooks, automated checks triggered by events such as tool use or session start. The guidance covers prompt-based decisions, command scripts, configuration, testing, and debugging for validation and workflow automation.

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

• Checking commands and file writes before execution
• Verifying task completion before an agent stops
• Loading project context when a session starts

Set up and use gstack in Capy or Claude Code for planning, code review, debugging, and release work. It checks the local environment, handles installation or repairs when needed, and selects the workflow instructions for the task.

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

• Set up gstack in a Capy environment
• Choose a workflow for planning or code review
• Check and repair an existing installation

Limit file edits to a chosen directory and block Edit, Write, and NotebookEdit operations outside it. Keep debugging or module changes within scope, with the restriction remaining active until explicitly removed.

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

• Keeping debugging edits within one folder
• Limiting changes to a single module
• Preventing accidental edits to unrelated files

Build a narrative project history from records stored in claude-mem. The report traces architectural changes, breakthroughs, debugging efforts, and work patterns, with timeline statistics and estimates of token savings from reusing recorded knowledge.

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

• Reviewing a project's development history
• Tracing architectural decisions and their consequences
• Examining recurring debugging and work patterns

Work with AI as a coding partner, choosing who writes code and who guides the work. Supports role switching, test generation, ongoing code review, debugging, and step-by-step explanations for learning.

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

• Write code with ongoing AI review
• Direct AI implementation while reviewing its output
• Develop features by writing tests first

Fetch execution traces, records of an agent’s actions, from LangSmith Studio to debug LangChain and LangGraph agents. Inspect errors, tool calls, memory operations, execution times, and token usage, or export records for further review.

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

• Investigating an agent failure
• Checking tool selection and execution order
• Investigating memory storage and recall

Investigate failed GAIA benchmark questions by inspecting execution records and classifying causes such as missing tools, reasoning errors, or answer extraction bugs. Follow targeted fixes, verify them through another run, and save findings for future debugging.

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

• Investigate an incorrect answer for a specific task
• Diagnose a question that timed out
• Investigate a drop in benchmark pass rate

Work with AI as a coding partner, choosing who writes code and who guides the work. Supports role switching, test generation, ongoing code review, debugging, and step-by-step explanations for learning.

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

• Write code with ongoing AI review
• Direct AI implementation while reviewing its output
• Develop features by writing tests first

Research existing code, documents, and relevant sources before producing a practical plan for implementation, migration, debugging, or evaluation. The plan explains key decisions, ordered steps, and validation checks, giving users something concrete to review before execution.

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

• Plan implementation steps before changing code
• Design a phased migration with rollback steps
• Break work into separate commits or pull requests

Test changes interactively in Codex's terminal interface. The skill explains how to launch it, save detailed logs for debugging, and send test messages programmatically with text and Enter submitted separately.

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

• Check changes in the Codex terminal interface
• Save detailed logs for debugging
• Send test messages programmatically

Guide implementation and debugging of visual Sequence editing in Remotion Studio. It documents how sequence identifiers, node paths, and stack traces behave during hot reload, and suggests how to track expanded UI state.

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

• Debug Sequence identity during hot reload
• Review how expanded Sequence state is tracked
• Check node-path and stack-trace mappings

Retrieve current documentation and code examples from Context7 for libraries, frameworks, and developer tools. Use the results to answer questions about API syntax, configuration, installation, version migration, and library-specific problems.

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

• Checking current API syntax
• Finding setup and configuration examples
• Investigating version migration issues

Find current documentation and code examples through the Context7 MCP server. Look up library setup, API usage, migration steps, and library-specific problems, using documentation for the requested version when available.

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

• Looking up documentation for a specific version
• Finding library setup and configuration steps
• Finding examples for code that uses external libraries

Inspect NSLogger logs from iOS and macOS apps, filter messages by severity, tag, text, or thread, summarize counts, export text, JSON, or CSV, and receive live logs for debugging.

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

• Review errors in a captured app session
• Find network failures by tag and message text
• Export logs as JSON or CSV for analysis

Debug programs with LLDB while keeping session state across commands. Set breakpoints, inspect variables and memory, and examine core dumps, with JSON results for agents and a debug adapter interface for editor clients.

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

• Inspect variables where a program stops
• Investigate a crash using a core dump
• Debug a running process

Investigate errors and unexpected behavior by finding related code, following function calls, and checking source files. GitNexus helps trace execution paths, while the diagnosis identifies the repository and reports how current its code index is.

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

• Finding where an error originates
• Investigating an endpoint that returns 500
• Tracing calls between two functions

Analyze software protections during authorized reverse engineering, the examination of compiled programs. Helps identify mechanisms that hinder debugging, obscure code, or prevent tampering, then choose safe analysis methods, document findings, and develop defensive recommendations.

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

• Analyze protected software with written permission
• Examine malware within an authorized scope
• Study protection mechanisms in CTFs or approved training

Automate Electron desktop apps with agent-browser through CDP, a browser debugging connection. Click controls, enter text, extract content, and capture screenshots while switching between app windows or embedded pages for routine work and testing.

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

• Automating clicks and form entry in desktop apps
• Extracting text and screen information from apps
• Capturing screenshots for application testing

Develop exploit code from a known memory corruption flaw, then investigate differences between local and remote execution. Covers stack, heap, and Linux kernel cases, with attention to library versions, debugging, and repeatable results.

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

• Developing exploit code for a known vulnerability
• Investigating why a CTF exploit fails remotely
• Checking library versions and memory protections

Generate independent options for design, implementation, explanations, or debugging, then compare them using one shared rubric. Code candidates use separate working copies and undergo independent verification before a winner is presented for review.

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

• Comparing several plausible design approaches
• Evaluating independent implementations of the same task
• Comparing explanations or debugging approaches

Investigate bugs and slow applications through reproducible examples, logs, environment comparisons, and hypothesis testing. The skill structures root cause analysis and performance measurement, helping developers narrow down failures and verify that a fix works.

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

• Investigate bugs that occur only occasionally
• Measure and locate performance bottlenecks
• Collect evidence and reproduce production failures

Build end-to-end tests with Playwright and Cypress to check complete user workflows, such as login and checkout. Improve test reliability through stable element selection, independent test data, appropriate waits, and debugging with traces and screenshots.

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

• Automate tests for login and checkout workflows
• Investigate tests that fail intermittently
• Run browser tests in CI/CD pipelines

Use OpenViking MCP tools to retrieve relevant knowledge before substantial tasks and save lasting preferences, decisions, and lessons during or after work. Import documents as searchable resources so later tasks can draw on previous findings.

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

• Retrieve previous fixes before debugging
• Save lasting preferences and working conventions
• Record decisions and their rationale

Build web apps connecting a CopilotKit React interface to agents hosted in Microsoft Foundry. Covers AG-UI, the communication protocol between them, plus tool approvals, conversation history, shared state, deployment, debugging, and dependency upgrades.

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

• Build a chat interface for a Foundry hosted agent
• Add approval screens for agent tool execution
• Investigate failures across the agent and web interface