'exceptions' 검색 결과

Review SOC 2 Type II audit readiness through six questions about controls, the organizational safeguards assessed over an observation period. Identify evidence gaps, control changes, and exceptions, then organize readiness findings and three concrete next actions.

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

• Check readiness before the observation period begins
• Review control operation midway through the period
• Check evidence coverage before audit fieldwork

Find repeated tasks in recorded activity or starred examples, then describe their steps, exceptions, and human decisions. Assess a small automation candidate using captured evidence, available tools, permissions, and clear completion criteria.

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

• Finding recurring tasks in activity records
• Reviewing starred examples for workflow patterns
• Assessing a small automation candidate

Investigate slow or failing requests in Google Cloud using Cloud Trace. Filter traces by duration or error status, inspect spans representing individual operations, and retrieve related Cloud Logging entries to investigate bottlenecks and exceptions.

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

• Find requests exceeding a latency threshold
• Inspect operation hierarchies within a trace
• Investigate failures using related application logs

Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.

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

• Update billing logic and its specification together
• Review how trials and enterprise contracts are handled
• Find the code that defines prices and allowances

Reconcile Stripe activity and bank transactions against invoice records using consistent fee and timing allowances. Record explained differences in the reconciliation sheet and flag unresolved transactions with supporting references for a person to review.

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

• Reconcile monthly invoices, Stripe activity, and bank deposits
• Check differences caused by fees or deposit timing
• Recheck previously flagged transaction mismatches

Handle personal data access, deletion, portability, and correction requests through a structured checklist. Guide identity checks, data searches, legal exceptions, and deadlines, then draft separate acknowledgment and substantive response letters for attorney review and human delivery.

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

• Preparing a response to a personal data access request
• Organizing checks for deletion and portability requests
• Tracking data searches across internal systems

Structure a law course study outline from class notes, casebook excerpts, and a syllabus. Match an existing format, arrange topic and case placeholders, and use questions and gap markers to guide the student's own work.

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

• Creating a topic structure from a course syllabus
• Adding class notes to an existing study outline
• Finding missing cases and unclear exceptions

Review supplier agreements against your team's contract guidelines. Produce a memo explaining deviations, legal risks, business impact, specific wording changes, fallback positions, and required approvers, so a lawyer can decide how to proceed.

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

• Reviewing supplier contracts against internal guidelines
• Examining liability limits and their exceptions
• Preparing specific wording changes for negotiation

Identify who should approve a contract issue using the team’s approval matrix and contract guidelines. The skill checks authority limits and exceptions, then drafts a request with the relevant wording, options, recommendation, and decision deadline.

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

• Finding the approver for an unlimited liability clause
• Checking approval authority for a contract’s value
• Drafting an approval request from a contract review memo

Split changes exceeding 400 lines into linked pull requests with clear boundaries and dependencies. Choose a chain structure, keep tests and documentation with each work unit, and document review order, verification plans, and justified size exceptions.

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

• Splitting a change that exceeds 400 lines
• Planning PRs that can merge independently
• Coordinating a feature through a draft tracker PR

Apply ReportLab’s built-in paragraph styles to PDF titles, headings, and body text. Learn how to reuse existing styles and create named variations without duplicate style names that can cause KeyError exceptions.

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

• Applying consistent styles to PDF titles and body text
• Checking available built-in paragraph styles
• Creating a custom style based on an existing one

Design enterprise AI and automation product pages that explain permissions, approvals, audit records, and recovery from failures. Organize verified metrics and case studies, accessible workflow details, and demo or waitlist forms that clarify what happens next.

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

• Redesigning an enterprise AI product page
• Explaining permissions and approval workflows
• Presenting verified security controls and case studies

Investigate code errors through a structured process using reproduction steps, logs, and testable explanations. The workflow guides fault isolation, fixes, and follow-up checks, with common error patterns for Python, JavaScript/TypeScript, and Bash/Zsh.

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

• Investigating an error using logs and reproduction steps
• Finding why code broke after a recent change
• Troubleshooting common shell script errors

Turn .NET runtime addresses in Android crash reports into function names, source files, and line numbers. The skill extracts build identifiers, downloads matching debug symbols, and uses llvm-symbolizer to produce a readable backtrace.

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

• Triaging native crashes in .NET MAUI or Mono Android apps
• Resolving libmonosgen-2.0.so and libcoreclr.so frames
• Investigating runtime-related SIGABRT or SIGSEGV crashes

Review MSBuild project files and build definitions for correctness and maintainability. Get prioritized findings with concrete recommendations, distinguishing confirmed defects from conditional risks and valid exceptions such as F# source ordering or required imports.

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

• Reviewing build files for maintainability
• Checking path portability across operating systems
• Reviewing import safety and required-file assumptions

Keep tests aligned with API changes and actual project files. This skill guides agents to update related tests in the same commit, refresh expected counts and lists, and check stale assertions when automated checks fail.

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

• Updating tests alongside API changes
• Refreshing expected lists after adding or deleting files
• Checking stale assertions when CI fails

Build and update Kiln screens using shared interface components and established styles. The skill guides component planning, comparison with reference screens, automated rule checks, and a review handoff containing evidence of consistency and any justified exceptions.

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

• Adding a Kiln screen using shared components
• Aligning forms and dialogs with established styles
• Checking Svelte changes for interface rule violations

Investigate code errors through a structured process using reproduction steps, logs, and testable explanations. The workflow guides fault isolation, fixes, and follow-up checks, with common error patterns for Python, JavaScript/TypeScript, and Bash/Zsh.

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

• Investigating an error using logs and reproduction steps
• Finding why code broke after a recent change
• Troubleshooting common shell script errors

Test local Tika changes with Jazzer, a tool that mutates inputs to uncover failures. Build parser fuzzers, check existing files, reproduce crashes, add starting samples, and retest fixes for memory exhaustion, hangs, and unexpected exceptions.

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

• Fuzzing local Tika parser changes before merging
• Running existing files through a parser once each
• Reproducing and retesting an OSS-Fuzz crash

Stock, capacity, and availability monitoring, acting on low-stock and slow-mover alerts, triaging order exceptions such as delays, return spikes, and complaints, and the operator's daily briefing; any start-of-day or what-needs-attention rundown is this flow, presented as a digest. Not needed for performance questions with no operational action attached.

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

Instrument browser/web apps with the Application Insights JavaScript SDK (@microsoft/applicationinsights-web). Use for Real User Monitoring (RUM) — page views, clicks, AJAX/fetch dependencies, exceptions, custom events, and browser-side GenAI agent traces correlated to backend OpenTelemetry traces. Covers SDK Loader Script and npm setup, framework extensions (React, React Native, Angular), Click Analytics, telemetry initializers, and OTel GenAI semantic conventions for agent/tool/model spans emitted from the browser.

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

Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.

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

Dialogue writing and revision for screen and stage (对白/台词/潜台词) — merged from Robert McKee's Dialogue (dialogue as action, said/unsaid/unsayable, exposition as ammunition, beat = action/reaction gerunds, flaws of credibility/language/content/design, character-specific vocabulary and grammar, seven scene analyses), Richard Walter (economy, subtext, argument, no small talk, no parentheticals, silence), Neill Hicks (listening, on-the-nose exceptions, energy, five-step exercise), Lu Jun (语言要美; 典雅美/通俗美, 对话三要求 动作性/性格化/潜台词), Lajos Egri (dialogue born of three-dimensional character, escalation), Blake Snyder (cover-the-names test), and screwball-comedy dialogue conventions. Use when writing or polishing dialogue, fixing on-the-nose or expository lines, giving each character a distinct voice, converting a two-hander into a trialogue, writing comedy exchanges, or cutting speeches. Chinese-opera lyrics (戏曲唱词) are in sw-chinese-opera-banqiang, not here.

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

Investigate AI traces, observations, exceptions, latency, sessions, prompts, datasets, annotation queues, and scores through Langfuse MCP. Use when the request names Langfuse or asks to diagnose recorded AI behavior.

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