'impact' 검색 결과

Carry out an engineering plan through stepwise code changes, dependency impact checks, tests, and focused commits. It also handles small, bounded tasks directly, checking the code relationship index before relying on its results.

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

• Implementing an existing engineering plan
• Making a small change across one or two files
• Testing each step before committing

Turn local Claude Code session history into a personal activity report, cross-checked with local Git history. Generate Markdown and standalone HTML showing project activity, touched files, related commits, and each project's share of compute usage.

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

• Explaining Claude Code usage to a manager
• Reviewing monthly activity across projects
• Preparing evidence for a personal performance review

Plan and coordinate authorized penetration tests across multiple stages, from reconnaissance to access, privilege escalation, movement between systems, and impact assessment. Assign specialist skills, revise blocked paths, and maintain evidence and progress records for the final report.

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

• Plan a penetration test across multiple stages
• Assess how far a vulnerability could lead
• Replan from existing credentials or system access

Model how an acquisition changes the buyer’s earnings per share. Compare purchase prices, cash and stock payment mixes, and synergy assumptions, then produce an Excel workbook and a one-page summary of the deal’s financial effects.

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

• Estimating how an acquisition changes earnings per share
• Comparing cash and stock payment mixes
• Testing purchase premiums and synergy assumptions

Create a structured review after a production incident, focusing on systems and processes without blaming individuals. Reconstruct events, quantify impact, investigate causes, and document specific follow-up actions with named owners and deadlines.

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

• Write a review after a production outage
• Reconstruct an incident timeline from records
• Separate root causes from contributing factors

Audit landing pages and checkout flows to find obstacles to purchases or signups. Review ad consistency, mobile layout, forms, trust signals, and tracking, then receive specific fixes ranked by expected revenue impact.

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

• Investigate paid traffic that produces few conversions
• Review a landing page before increasing ad spend
• Find checkout steps where shoppers drop off

Assess an Azure resource using logs and performance measurements, investigate failures and their impact, and produce a prioritized remediation plan with concrete steps, validation procedures, rollback options, and monitoring recommendations.

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

• Investigating Azure service failures
• Finding causes of slow responses
• Prioritizing fixes by operational impact

Compare C# Web API source code with its TypeScript or JavaScript clients to find mismatched data fields, required inputs, and response handling. Receive an audit report showing client impact, severity, and confidence in each match.

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

• Check client impact before merging a DTO or controller change
• Audit API compatibility before a release
• Find stale request fields and missing response fields

Analyze bid–ask spreads, order books, and buying and selling imbalances to assess liquidity, or how easily an asset trades. Estimate large-order price impact and transaction costs, with additional guidance on Chinese A-share auction and block trades.

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

• Estimate transaction costs for large orders
• Assess liquidity using order book depth and spreads
• Study trading imbalances and signs of liquidity stress

Draft malware incident communications for internal teams, executives, IT responders, customers, and regulators. Provides structured templates and severity-based notification workflows to organize impact details, response actions, decisions needed, and the timing of updates.

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

• Prepare an initial internal notification about a malware incident
• Summarize business impact and decisions for executives
• Draft technical response instructions for IT teams

Rewrite vague resume bullets into concise achievement statements that show actions, measurable results, and scale. Use structured writing methods and role-specific wording to explain accomplishments clearly, including experience from projects, internships, and career changes.

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

• Rewriting resume bullets to highlight achievements
• Finding numbers that explain the scale of work
• Tailoring past experience to a new role or industry

Plan refactoring with dependency analysis, which shows how code parts rely on each other. Find candidates and unreferenced code, preview and apply renames, and compare the resulting impact with the original plan.

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

• Finding refactoring candidates and unreferenced code
• Previewing edits before applying a rename
• Checking affected dependencies and execution paths

Model how a delayed, reduced, or lost deal changes progress toward a sales target. Compare forecast totals, the remaining gap, and pipeline coverage—the open deal value relative to that gap—and identify realistic replacement deals and actions.

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

• Checking the impact of a deal moving to next quarter
• Recalculating target gaps after a deal shrinks or is lost
• Finding replacement deals that could close this quarter

Research competitors' messaging, product positioning, and content strategy, then build a comparison brief showing strengths, gaps, opportunities, and threats. Use the findings to shape marketing messages, choose content topics, or prepare sales comparison guides.

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

• Compare competitors' messages and positioning
• Find overlooked content topics and audiences
• Prepare a competitive reference for sales

Turn interview notes, survey responses, and customer feedback into findings supported by evidence. Group recurring themes, assess frequency and impact, and produce prioritized recommendations to guide product improvements and future research.

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

• Finding shared issues across user interviews
• Organizing themes in open-ended survey responses
• Prioritizing improvements from support tickets

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

Find unused components, files, translation keys, and other unnecessary code across a codebase. Document every consumer and removal impact in a tracking issue, then turn one maintainer-approved candidate into a focused pull request.

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

• Periodically checking for accumulated unused code
• Finding orphaned translation keys
• Recording removal candidates and their impact in an issue

Review code for privacy risks, prepare data protection impact assessments, and track personal data requests and deadlines. The skill supports GDPR and German privacy compliance work, with final compliance decisions referred to a data protection officer or legal counsel.

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

• Checking a service's code for privacy risks
• Preparing a data protection impact assessment
• Tracking deadlines for access and erasure requests

Plan and evaluate product A/B tests with clear hypotheses, success metrics, sample size estimates, and stopping rules. Rank proposed experiments and interpret results using effect sizes and uncertainty to support practical product decisions.

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

• Turn a product improvement idea into a testable hypothesis
• Estimate the sample size needed for an A/B test
• Rank experiments by impact, confidence, and ease

Manage multiple apps and shared packages in one repository. Analyze dependencies and change impacts, limit builds and tests to affected packages, configure caching, and plan repository consolidation while preserving Git history.

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

• Checking which apps a shared package change affects
• Limiting CI builds and tests to affected packages
• Combining repositories while preserving Git history

Design SaaS cancellation flows, match retention offers to exit reasons, and prepare payment retry schedules and recovery emails. Get flow copy, survey options, email templates, and metrics for reviewing cancellations and failed payments.

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

• Designing a cancellation flow
• Matching retention offers to exit reasons
• Preparing failed-payment recovery emails

Compare feature ideas by expected impact, required effort, uncertainty, and fit with product goals. Get five ranked recommendations, with reasons for each choice, trade-offs, and explanations of which ideas should receive lower priority.

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

• Ranking a backlog of feature ideas
• Choosing the scope of the next development cycle
• Comparing opportunities using customer importance and satisfaction

Review a product requirements document, roadmap, or strategy by challenging the assumptions it depends on. Rank potential failures by impact, likelihood, and testing cost, then propose small tests, evidence to gather, and criteria for stopping or changing course.

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

• Challenging critical assumptions before starting a plan
• Preparing a strategy document for executive review
• Choosing low-cost tests to run this week

Find and organize technical debt, the code issues deferred for later improvement. Maintain a register, rank items by impact and repair effort, and report unresolved work and changes over each sprint.

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

• Scan code for signs of deferred maintenance
• Record known issues and reasons for deferring fixes
• Prioritize fixes by impact and effort