'impact' 검색 결과

Review game code for likely performance bottlenecks in processing, memory, rendering, and data loading. Compare available estimates with configured limits and produce ranked optimization recommendations, including expected impact, effort, risks, and areas needing runtime measurement.

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

• Finding performance bottleneck candidates in one game system
• Reviewing performance across the whole game
• Comparing available estimates with configured performance limits

Explore relationships between functions and files using a prebuilt code graph, a map of code dependencies. Trace bugs, inspect callers and execution paths, and assess the impact of refactoring or proposed changes.

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

• Explore callers and dependencies in unfamiliar code
• Trace a bug across multiple files
• Assess the impact of renaming or removing code

Trace where BigQuery and Cloud Storage data comes from and where it goes. The skill summarizes table or column lineage, meaning data origins and movement, in a readable Markdown report to support data quality investigations.

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

• Investigating data origins during a quality issue
• Summarizing data sources and destinations
• Tracing the flow of a specific column

Execute development subtasks under a supervising agent, starting with an implementation plan and impact analysis. Deliver code and a three-question self-review in a defined completion format for the supervisor to assess.

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

• Delegating an implementation subtask to an agent
• Planning changes and assessing their impact before coding
• Handing over code with a structured self-review

Set up Sentry error tracking, investigate production failures, and prioritize issues by user impact. Configure useful alerts and analyze performance traces, which show how time is spent across application operations and services.

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

• Setting up application error tracking
• Investigating production errors
• Prioritizing issues by user impact

Assess Web3 vulnerability findings before submission by checking scope, reproducibility, prerequisites, and attack costs. Organize the root cause, measurable impact, working proof of concept, and proposed fix into an Immunefi report, with examples for comparison.

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

• Checking whether a finding is ready for submission
• Drafting an Immunefi vulnerability report
• Reviewing reproduction code and measurable impact

Audit an app’s animations for responsiveness, performance, and accessibility, then rank the findings by impact and effort. Produce detailed implementation plans that another agent can follow, while leaving source code unchanged during the audit.

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

• Audit animations across an entire app
• Prioritize motion issues by impact and effort
• Prepare implementation plans for another agent

Assess the full code change for effects on callers, configuration, and related behavior. Organize focused tests, execution evidence, and unverified areas to support decisions about whether a fix or pull request is ready.

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

• Check effects on callers of shared code
• Organize test evidence before approving a pull request
• Report unverified areas before handing off a fix

Implement a feature from its design and connect each covered user journey, a sequence of user actions, to a meaningful test. Run focused checks and assess the full change for effects on existing behavior.

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

• Implement a feature from an agreed design
• Connect key user journeys to tests of new behavior
• Assess effects on existing behavior before preparing a demo

Manage service incidents from initial assessment through recovery review. The skill organizes severity, impact, roles, status updates, and timelines, then drafts a blameless postmortem with root cause analysis and action items assigned to owners.

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

• Assess the severity and impact of a new incident
• Draft internal and customer status updates
• Record mitigation steps and an incident timeline

Update an existing AI governance profile through guided changes. Adjust risk posture, escalation contacts, registered use cases, vendor positions, or assessment formats, while checking downstream effects and inconsistencies before saving each change.

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

• Adjusting risk posture for AI use-case reviews
• Updating escalation contacts and approvers
• Changing approved or conditional AI use cases

Compare proposed employee handbook wording with the current version, identify affected policies and state supplements, and flag reductions in promised benefits. Receive a change summary, impact tables, and a checklist for preparing publication.

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

• Comparing proposed policy wording with the current handbook
• Finding cross-references affected by a policy change
• Checking updates needed in state supplements

Review SaaS subscription terms against your team's standards, covering renewals, price increases, data export, and service availability commitments. Examine AI training rights and liability, with findings rated for both legal risk and business impact.

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

• Checking renewal dates and cancellation deadlines
• Reviewing price increases and data export terms
• Examining AI training rights and liability limits

Understand software architecture, trace request flows, and assess the impact of code changes using Ontoly’s graph of software relationships. Answers include supporting graph evidence, confidence, and relevant limitations.

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

• Explain a repository’s architecture
• Trace requests through routes and services
• Assess dependencies before refactoring

Review an interface across accessibility, layout, writing, typography, color, and visual polish. It coordinates specialist skills, combines evidence from code and rendered screens, and produces one report with findings ranked by their impact on users.

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

• Reviewing a screen or complete user flow
• Checking loading, error, and narrow-screen states
• Prioritizing interface fixes by user impact

Analyze code structure with Trailmark to identify complex functions, trace input flow, assess impact across connected code, and locate privilege boundaries. The resulting JSON provides detailed evidence for deciding where to focus a code audit.

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

• Prioritizing code audit targets
• Tracing input flow and assessing impact
• Inspecting unresolved calls and type references

Connect static analysis results and human audit notes to a Trailmark code graph. Group findings by severity and compare them with input flow, impact, and privilege boundaries to prioritize investigation and understand findings in their code context.

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

• Connecting Semgrep or CodeQL results to code structure
• Combining human audit notes with automated findings
• Prioritizing findings using input flow and impact

Scan source code for security weaknesses with Semgrep after approving the target and rulesets. Choose full results or focus on important findings, then receive merged results and a record of failed or skipped scans.

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

• Audit source code for security weaknesses
• Check for vulnerabilities before code review
• Focus on findings with medium-to-high confidence and impact

Turn penetration test and red team results into reports for executives and technical teams. Structure findings, explain severity scores and business impact, organize evidence, and document remediation steps and retest plans.

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

• Preparing a final penetration test report
• Rewriting an executive summary for nontechnical readers
• Creating a reusable security reporting template

Evaluate older Wi-Fi clients and embedded devices for KRACK and FragAttacks vulnerabilities. Covers test suites, likely patch status, practical impact, and reporting findings by device, firmware version, and vulnerability identifier.

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

• Assessing older Wi-Fi clients
• Reviewing IoT firmware patch status
• Distinguishing KRACK and FragAttacks impacts

Draft customer announcements for retiring a product, feature, or plan. Match the message length and communication stages to the impact, explaining the reason, key dates, customer disruption, support, and next steps, including cases with no replacement.

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

• Writing a retirement notice for a product or feature
• Explaining migration from a legacy product to its replacement
• Preparing an exit announcement when no replacement exists

Analyze how a specific event or policy change affects listed companies, sectors, earnings, valuations, and portfolio decisions. Produce a report linking causes to equity impacts, separating evidence from assumptions and outlining scenarios, counterarguments, and monitoring signals.

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

• Assessing how a policy change affects listed companies
• Mapping sector winners and losers from an economic shock
• Comparing earnings and valuation scenarios

Analyze product or business data to recommend priorities and next steps. Check source reliability, metric definitions, and meaningful comparisons, then explain the evidence, potential impact, and uncertainty behind each recommendation.

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

• Prioritize product improvements using data
• Evaluate the impact of a change
• Compare opportunities across user segments

Compare Sentry issues across selected time windows and releases to find new or recurring problems and changes in frequency or affected users. Prioritize findings using user impact and the strength of available evidence.

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

• Compare issues before and after a release
• Find recurring issues and frequency changes
• Prioritize issues by affected users