'output' 검색 결과

Investigate MSBuild failures caused by projects or build configurations writing to the same output folders. Compare build logs, output paths, and project settings to identify collisions behind overwritten files, restore errors, or failures that disappear on retry.

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

• Investigate file access errors during parallel builds
• Find shared intermediate folders causing NuGet restore errors
• Check output paths when building for multiple frameworks

Complete guide for xUnit test output and logging. Use when you need to implement test output, diagnostic logging, or ILogger alternatives in xUnit tests. Covers ITestOutputHelper injection, AbstractLogger pattern, structured output design. Includes XUnitLogger, CompositeLogger, performance test diagnostic tool implementations. Keywords: ITestOutputHelper, ILogger testing, test output xunit, test output, test logging, AbstractLogger, XUnitLogger, CompositeLogger, testOutputHelper.WriteLine, test diagnostics, logger mock, test log, structured output, Received().Log

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

Create output schemas, definitions of result fields and display settings, for an Apify Actor by inspecting its source code. Generate dataset and output files, add key-value storage definitions when needed, and update actor.json to reference them.

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

• Creating output schemas for a new Actor
• Updating schemas after output fields change
• Configuring result table columns in Apify Console

Add a new safe-output message type to gh-aw, connecting configuration validation, Go parsing, and JavaScript rendering. Follow the required updates through tests, exports, documentation, and generated action bundles so the message reaches workflow output.

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

• Add a new safe-output message type to gh-aw
• Support custom templates with placeholders
• Test default and customized message output

Validates agent outputs against expected schemas and quality criteria. Ensures outputs meet structural requirements and content standards. Activate on 'validate output', 'output validation', 'schema validation', 'check output', 'output quality'. NOT for confidence scoring (use dag-confidence-scorer) or hallucination detection (use dag-hallucination-detector).

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

Create a Dubai time card as an SVG image and a Markdown summary from supplied time values. It fills the included templates and saves both files in the designated output directory without fetching or recalculating the time.

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

• Turning supplied Dubai time into a visual card
• Saving a time card with a Markdown summary
• Creating time cards from a consistent template

Analyze large logs, test results, API responses, and files outside the conversation, then return focused findings. It guides agents to save, process, index, and search outputs while limiting how much raw data enters their working context.

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

• Extracting errors from large logs
• Summarizing test failures and build warnings
• Inspecting JSON and CSV data

Diagnose unexpected terminal-tools results, including empty output, missing exit codes, expired output handles, and busy sessions. Use returned status fields to distinguish ongoing work, output limits, shell behavior, and failures, then choose a recovery step.

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

• Investigate empty or truncated command output
• Interpret missing exit codes and conflicting status fields
• Resolve job limits and busy terminal sessions

Diagnose unnecessary rebuilds in MSBuild by examining build logs, file timestamps, and declared inputs and outputs. Identify why work repeats, guide fixes when requested, and verify that a second unchanged build skips the expected targets.

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

• Investigating rebuilds when no files changed
• Reviewing inputs and outputs on custom targets
• Checking generated files and cleanup behavior

Extend safe-output jobs, which execute agent-generated actions, to reference newly created issues through temporary IDs. The guide covers job dependencies, issue-number resolution, input validation, tests, and warning-based handling of unresolved references.

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

• Linking sub-issues to a parent created in the same run
• Adding temporary ID resolution to another safe-output job
• Testing temporary ID validation and job dependencies

Check a paper's numerical claims against saved analysis outputs before submission. Receive a report identifying verified figures, unsupported claims, missing files, unreferenced outputs, and citation keys absent from the bibliography, without changing the manuscript.

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

• Check manuscript numbers before submission
• Verify table and figure references against output files
• Find analysis outputs not referenced in the paper

Orchestrator for the eval-output skill suite — evaluate LLM and agent outputs for quality, accuracy, helpfulness, and safety using structured rubrics and LLM-as-judge techniques. Load when the user says "evaluate this output", "score this response", "run an eval", "LLM as judge", "evaluate agent output", "how good is this response", "rate this answer", "eval this", or provides an LLM output that should be assessed for quality. Single entry point for all output evaluation workflows.

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

Validates agent outputs against expected schemas and quality criteria. Reports structural and content checks within the declared evidence scope. Activate on 'validate output', 'output validation', 'schema validation', 'check output', 'output quality'. NOT for confidence scoring (use dag-confidence-scorer) or hallucination detection (use dag-hallucination-detector).

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

Configure output requests - field outputs, history outputs. Use when user asks what results to save, output variables, reduce output file size, or history output.

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

Integrate files generated during MSBuild into compilation or build output. Address missing generated source and content by choosing target timing, using the configured intermediate directory, and registering files so Clean can remove them.

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

• Including generated .cs files in compilation
• Copying generated configuration or data files to output
• Fixing file patterns that miss files created during a build

Establish repeatable performance measurements for MSBuild and .NET builds before optimizing. Compare clean-output, changed-source, and unchanged builds, record timing ranges, and assess output layouts, dependency references, and parallel build options against the measured baseline.

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

• Measure slow builds before choosing an optimization
• Compare build times before and after changes
• Check rebuild behavior after a small source edit

Choose when MSBuild copies files to build or publish folders. The skill explains settings that avoid unnecessary copies, restore output files changed by tests or apps, and apply shared copy behavior across existing projects.

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

• Reducing unnecessary file copies on every build
• Restoring test databases changed between builds
• Choosing copy settings for configuration files

Sysinternals DebugView CLI (DbgViewCli) for capturing and analyzing usermode and kernel-mode Windows debug output from the command line. USE FOR: capturing OutputDebugString output, kernel DbgPrint/KdPrint capture, boot-time debug logging, remote debug monitoring, filtering debug output by PID or process name, crash dump analysis, automated debug capture with bounded execution. DO NOT USE FOR: non-Windows platforms, application-level logging frameworks (log4j, serilog), Azure Monitor or cloud telemetry, ETW tracing (use WPR/xperf instead), user-mode crash dumps (use WinDbg). Triggers: "debug output", "DbgView", "DebugView", "kernel debug", "capture debug logs", "boot logging", "OutputDebugString", "DbgPrint", "KdPrint", "remote debug monitor", "debug capture CLI".

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

Manage for output using Grove's "High Output Management": a manager's output is their organization's output, raised by high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation", "meeting overload", "new manager", "how do I run a 1:1", or "just got promoted to manager". Also trigger when structuring a manager's calendar and meeting cadence, designing team metrics, running planning, coaching delegation, or preparing performance reviews. Covers leverage, production principles, meetings as the medium of management, decisions, OKRs, and task-relevant maturity. For intrinsic motivation, see drive-motivation. For a company operating system, see traction-eos.

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

Tested output format specifications for Claude prompts. Use when the user wants a specific deliverable structure — retrieving, reviewing, customizing, or building output formatting. Trigger on: "give me the Executive Brief format," "show me the output template for," "I need the Decision Matrix structure," "show me available output formats," "build a custom output format for." Provides 10 ready-to-use structures (executive briefs, technical designs, research summaries, implementation plans, decision matrices, competitive analyses, post-mortems, stakeholder updates, strategic memos, process documentation) plus a custom template, with per-section length guidance and format constraints tested against Claude formatting defaults. If unsure which format fits, use rootnode-block-selection first if available. Do NOT use for evaluating existing prompts (use rootnode-prompt-validation if available) or choosing reasoning/identity approaches (use rootnode-block-selection if available).

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

Score LLM and agent outputs using LLM-as-judge techniques — direct scoring against rubrics or pairwise comparison between two outputs. Includes built-in bias mitigation for position bias, length bias, and self-enhancement bias. Load when the user asks to score an output, judge a response, evaluate against a rubric, compare two outputs, do direct scoring, run pairwise comparison, or says "rate this", "which response is better", "score this against the rubric", "judge this output", "LLM as judge this". Sub-skill of eval-output orchestrator.

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

Control a running iTerm2 workspace from the command line. See what each terminal pane is doing, send commands, read current and past output, arrange windows and tabs, manage tmux integration, and change preferences.

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

• See what is running in every terminal pane
• Send commands and read terminal output history
• Create and restore layouts with multiple panes

Design AI agents and chatbots in n8n, choosing suitable nodes and connecting models, tools, conversation memory, and structured JSON output. Includes guidance on document retrieval and human approval before tool execution.

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

• Building a chatbot with conversation memory
• Connecting external tools to an AI agent
• Returning data in a defined JSON format

Guides edits to Worktrunk’s command-line messages, help text, and progress displays. Defines wording, colors, symbols, and where output goes, so command results and status messages follow consistent conventions in terminals, pipes, and redirected logs.

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

• Revising warning and error messages
• Separating command results from progress messages
• Checking color handling in redirected output