'diff' 검색 결과

Reconcile general ledger and subledger extracts for the same entity, asset class, and date. Match transactions or positions, report differences in amounts, quantities, or posting dates, and summarize likely causes alongside the matching rate.

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

• Running daily ledger reconciliations
• Checking ledger differences at month-end
• Finding entries recorded in only one ledger

Investigate incorrect, missing, or unexpectedly changed OpenViking memories by tracing memory files back to archived change records and, when needed, source messages. Return an evidence trail, identify gaps, and suggest next steps without modifying data.

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

• Investigate incorrect memory content
• Check unexpected memory paths or owners
• Trace missing or deleted memories

Clarify how a product differs from competitors and test whether buyers value that difference. The skill guides competitor messaging reviews, assessments of hard-to-copy strengths, wording comparisons, and a phased rollout of validated positioning.

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

• Clarifying differences from competitors
• Testing website headlines and sales wording
• Planning a phased positioning rollout

Analyze Git changes, group related files for staging, and create commits using Conventional Commits, a structured message format. Infer the change type and scope from the diff, with optional user overrides for the type, scope, and description.

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

• Committing changes with a structured message
• Grouping related files into a logical commit
• Choosing a change type and scope from a diff

Analyze current Git changes to choose a branch for a feature, release, or urgent fix. Create a descriptive name and switch to the new branch using Git Flow, a structured approach to managing development branches.

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

• Create a branch for a new feature
• Separate release preparation changes
• Create a branch for an urgent production fix

Resolve a design question by building a temporary, runnable prototype. Explore logic through clickable scenarios or compare three structurally different interface variants, then record the user's decision while keeping the prototype separate from production code.

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

• Comparing three different interface structures
• Exploring state transitions through clickable scenarios
• Resolving design discussions that need a visible example

Create a competitive brief comparing products or specific features, including pricing, positioning, customer feedback, and market changes. Translate findings into product priorities, differentiation choices, and practical material for sales teams or executive discussions.

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

• Set development priorities using feature comparisons
• Decide where to differentiate or match competitors
• Prepare competitive analysis for boards or investors

Analyze data distributions, trends, unusual values, and differences between groups using suitable statistical methods. The skill guides interpretation of effect sizes, meaning the magnitude of differences, alongside uncertainty and business impact, while checking for misleading conclusions.

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

• Summarize business metrics beyond averages
• Assess differences in A/B test results
• Investigate outliers and unusual time-series values

Have a different AI model review code, analysis, or documents against the original skill's stated requirements. Receive evidence-based findings and a comparison of agreement and disagreement, then decide which recommendations to accept.

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

• Getting a second opinion on substantial code changes
• Reviewing authentication and other security-sensitive changes
• Checking work before a bulk operation

Challenge business plans, prepare for difficult board questions, and work through decisions with painful tradeoffs. This skill identifies assumptions and failure risks, examines stakeholder impacts, and turns postmortems into changes with clear owners and verification dates.

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

• Find weaknesses in a business plan
• Prepare answers to difficult board questions
• Compare options for a difficult management decision

Research five direct competitors and compare their features, pricing, strengths, and weaknesses. Use the findings to understand market positions, identify unmet customer needs, and recommend ways to differentiate a product.

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

• Prepare a competitive research brief
• Compare competitors' features and pricing
• Identify unmet customer needs

Review code changes for newly introduced security issues with a plausible attack path. Produce findings for the Warden security summary, including affected lines, severity, a minimal fix, and observable conditions for confirming the issue is resolved.

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

• Checking a PR for newly introduced vulnerabilities
• Reviewing CI changes that expose secrets or write access
• Inspecting Electron changes for unsafe permissions

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

Review a GitHub pull request or branch and receive a concise summary of its purpose, design choices, and notable code. Check linked issue acceptance and highlight evidence-based concerns through their observable impact on users.

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

• Understand a pull request before reviewing it
• Summarize changes in a branch without a PR
• Review design decisions with file and line references

Build distinct, working versions of one interface component and compare them at full size using a visual picker. Explore differences in layout, interaction, or motion, then integrate the version you choose into the project.

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

• Compare different layouts for a pricing card
• Try several notification interaction designs
• Explore motion choices for a hold-to-delete button

Review an existing bug-fix pull request using validated reproduction tests and the complete code diff. Assess root-cause coverage, scope, and regressions, then document behavioral evidence and follow the workflow's branch and approval rules.

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

• Independently verifying an existing bug-fix pull request
• Checking a complete diff for scope and root-cause coverage
• Recording the user journey on the proposed fix

Run a quick first review of code changes with six specialist agents working in parallel. They check logic, input and output, shared state, resources, missing behavior, and API completeness, then combine duplicate findings into a report ranked by confidence.

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

• Running a quick first review of a patch
• Screening diffs to prioritize further investigation
• Checking for missing cleanup and handlers

Compare a regulatory change with an indexed company policy library. Identify affected policies, missing or conflicting provisions, responsible owners, and specific changes needed, with source labels and flags for uncertainty about whether the rule is in force.

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

• Identifying policies affected by a regulatory change
• Comparing new requirements with existing policy wording
• Finding requirements that need a new policy

Prepare English pull requests for Apache SeaTunnel from a change summary, branch history, and file differences. It builds titles and bodies that follow project conventions, records actual testing, and can submit the pull request when requested.

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

• Drafting an English PR from current branch changes
• Choosing a PR title that follows SeaTunnel conventions
• Completing the PR template with changes and actual test results

Review an agent's saved context and unread coordination messages at the start of a task. Summarize relevant assignments, move handled messages aside, and prompt the agent to preserve lasting decisions and outcomes before finishing.

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

• Resume work using context saved in a previous session
• Check new messages and assignments for an agent
• Preserve decisions and outcomes for the next session

Compare a file’s current content with its intended replacement before writing. Skip matching files to avoid unnecessary rebuilds and timestamp changes, with guidance on readable diffs, line endings, encoding, and exact content requirements.

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

• Replacing configuration files only when content changes
• Avoiding rebuilds caused by unchanged generated files
• Reviewing differences before replacing a whole file

Reviews code changes for security risks using Git history, caller counts, and test coverage. Produces a Markdown report with evidence, potential attack scenarios, affected code, and clear limits on what was reviewed.

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

• Reviewing a pull request for security risks
• Checking whether a fixed bug has returned
• Assessing which callers a change could affect

Create an interactive HTML guide to a branch’s code changes, with complete file diffs arranged in a logical reading order, explanations of design choices, and review findings labeled by severity.

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

• Understanding a branch’s changes in a logical order
• Reviewing diffs alongside design explanations
• Checking findings labeled by severity

Create a clear statement of your product’s market position using Geoffrey Moore’s framework. Define the target customer, unmet need, product category, customer benefit, and meaningful differences from the alternatives buyers actually consider.

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

• Define the market position of a new product
• Sharpen differentiation against specific competitors
• Align product, sales, and marketing teams