'duplicates' 검색 결과

Reconcile accounting records with payment service payouts, identify discrepancies, possible duplicates, and missing receipts, then prepare a plain-English profit and loss summary with an Excel workbook and a one-page PDF for month-end review.

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

• Reconcile monthly payment payouts with accounting records
• Find possible duplicates and missing receipts
• Prepare month-end documents for an accountant

Look up a project's existing UI components in Storybook, including their props, or configuration inputs, and usage examples. Use the findings to answer questions and identify components to reuse before building duplicates.

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

• Find existing UI components
• Check component props and usage examples
• Answer questions about component usage

Organize open GitHub issues by category, risk, linked pull requests, duplicate candidates, and inactivity. Optionally analyze selected issues in depth, draft responses, and apply approved comments, labels, or closures to keep the backlog actionable.

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

• Sorting a growing backlog of open issues
• Checking whether suspected duplicate issues are truly duplicates
• Prioritizing security risks and breaking changes

Organize scattered files by type, purpose, or date, find duplicates, and review older material. Get a proposed folder structure, then approve file moves and renaming, with confirmation required before any deletion.

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

• Sorting a cluttered Downloads folder
• Finding duplicates and choosing which copies to keep
• Separating active projects from archived work

Explore a table or data file before starting analysis. Summarize its structure, missing values, duplicates, and distributions, flag potential quality issues, and suggest useful measures, grouping columns, and follow-up analyses.

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

• Understanding an unfamiliar table or data file
• Checking missing values, duplicates, and suspicious entries
• Choosing measures and grouping columns for analysis

Organize Happy's GitHub issues, find duplicates, and check whether reported bugs are fixed on main, the primary development branch. Prepare replies and proposed actions for maintainer review, with explicit approval required before changes affecting contributors.

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

• Grouping open issues and identifying duplicates
• Checking whether reported bugs are fixed on main
• Drafting replies and issue closure comments

Organize scattered files by type, purpose, or date, find duplicates, and review older material. Get a proposed folder structure, then approve file moves and renaming, with confirmation required before any deletion.

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

• Sorting a cluttered Downloads folder
• Finding duplicates and choosing which copies to keep
• Separating active projects from archived work

Use when designing, reviewing, or troubleshooting Salesforce duplicate prevention, matching rules, duplicate rules, and merge governance. Covers cleaning up duplicates that already exist at ordinary volume: merge sequencing, survivorship, stewardship ownership. Also covers the deployable MatchingRule / DuplicateRule metadata, the Alert-vs-Block action pair, DuplicateRecordSet reporting, and the Apex DMLOptions.DuplicateRuleHeader.allowSave bypass. Triggers: 'duplicate rule', 'matching rule', 'merge strategy', 'dedupe', 'survivorship', 'D&B', 'same contact twice', 'clean up duplicate records', 'clean up duplicate accounts', 'DUPLICATES_DETECTED', 'allowSave', 'FindDuplicates'. NOT for cleanup at volume — hundreds of thousands of records, batch merge jobs, DemandTools/Cloudingo — use data/large-scale-deduplication. NOT for which field values and child records the platform keeps in a merge - use data/record-merge-implications.

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

OpenClaw의 PR과 Issue가 기존 작업과 중복되는지 근거로 판단하고, prtags에서 관련 작업을 하나의 그룹으로 묶어 판단 이유와 확신도를 기록합니다.

• PR과 기존 작업의 중복 여부를 확인합니다
• 같은 문제를 보고한 Issue를 찾습니다
• 관련 작업을 하나의 중복 그룹으로 묶습니다

Prepare LLM training datasets with NeMo Curator by removing duplicates, filtering low-quality content, and redacting personal information. The skill also covers image, video, and audio curation, including GPU processing and distributed workflows.

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

• Clean web-scraped text for LLM training
• Remove exact, near, and meaning-based duplicates
• Remove or replace personal information in text

Turn git changes since the last tag into clear App Store release notes. Identifies updates users will notice, groups new features, improvements, and fixes, removes internal work and duplicates, and checks each bullet against the actual changes.

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

• Drafting App Store What's New text for a release
• Turning technical commits into plain release notes
• Collecting user-visible changes between specified tags

Build data quality checks with Great Expectations, dbt tests, and data contracts, which define shared expectations between teams. Check missing values, duplicates, and freshness, then integrate validation into data pipelines and CI/CD.

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

• Check data for missing values and duplicates
• Build a dbt test suite
• Define shared data contracts between teams

Prepare spreadsheet data for analysis by finding extra spaces, inconsistent capitalization, numbers stored as text, mixed date formats, and duplicates. Review proposed fixes, apply traceable formula-based changes, and compare results before and after cleanup.

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

• Cleaning spreadsheet data before analysis
• Standardizing dates and text capitalization
• Finding duplicate rows and mixed data types

Build a workflow that extracts and deduplicates threat indicators such as URLs and IP addresses, creates readable reports with links disabled, and prepares standardized STIX 2.1 data for sharing through MISP or TAXII.

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

• Preparing threat reports with links disabled
• Consolidating indicators from multiple sources
• Distributing threat indicators through MISP or TAXII

Build a central vulnerability dashboard with DefectDojo to combine scanner findings, remove duplicates, and track remediation. Includes Docker deployment, automated scan imports from CI/CD pipelines, Jira ticket integration, and API queries for reporting metrics.

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

• Combining findings from multiple security scanners
• Importing scan results automatically from CI/CD pipelines
• Connecting vulnerability findings to Jira tickets

Analyze threat intelligence feeds to extract indicators of compromise, observable clues of possible attacks, and their campaign context. Assess source quality, standardize formats, remove duplicates, and enrich indicators for distribution to security monitoring systems.

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

• Assessing the quality and relevance of threat intelligence feeds
• Standardizing indicators into STIX 2.1
• Removing duplicates and adding attack campaign context

Check names, aliases, and existing pages before saving content to a gbrain knowledge store. The skill reads likely matches to identify duplicates, links to existing information, and routes new material to the appropriate ingestion skills.

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

• Check notes for duplicates before saving
• Resolve different names for the same person or company
• Review files before a bulk import

Collect public posts across a blog, newsletter, or feed archive and save clean Markdown pages for each article. The workflow avoids duplicates, supports resumed runs, repairs empty results, and hands articles to a separate enrichment skill.

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

• Importing a blog's public article archive
• Organizing public newsletter posts as knowledge pages
• Rerunning a feed import without duplicates

Investigate Apache ShardingSphere issues using official documentation, code, tests, and issue discussions. Distinguish bugs, unsupported usage, duplicates, and enhancement requests, then draft a concise maintainer-style reply explaining the evidence and next action.

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

• Distinguish bugs from unsupported configurations
• Check whether an issue duplicates an earlier report or fix
• Draft a GitHub issue reply with clear next steps

Assess Verdaccio issues against the code, affected release lines, and related reports. Distinguish bugs from configuration problems or duplicates, then propose existing labels, next steps, and a reply draft backed by evidence.

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

• Classifying a newly reported issue
• Checking which release lines a bug affects
• Finding duplicates and related fixes

Assess OpenShell issues by checking first-hand use cases, reproduction evidence, existing behavior, and duplicates. Prepare a concise technical assessment, request specific missing information, and leave acceptance and roadmap decisions to human maintainers.

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

• Checking reproduction evidence for a reported bug
• Clarifying a feature request’s use case and alternatives
• Identifying duplicates or already-fixed behavior

Turn GitHub issue reports into actionable work by searching for duplicates, attempting reproduction, and assessing user impact. Organize issues with existing labels, appropriate owners, and milestones, while clearly recording what was and was not verified.

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

• Assessing newly reported GitHub issues
• Finding duplicate reports and recurring bugs
• Reproducing bugs and recording the results

Turn rough bug reports or requests into Linear issues with clear symptoms, reproduction steps, evidence, and routing details. Check for duplicates, distinguish observations from guesses, and present the proposed issue for approval before creating it.

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

• Turn a rough bug report into an issue
• Check whether a bug is already tracked
• Organize reproduction steps and evidence

Review open issues and discussions to organize a project's backlog. Identify possible duplicates, suggest priorities and labels, and record the top five actionable items and cases needing human attention in a state file.

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

• Organizing a growing issue backlog
• Selecting the top five actionable issues
• Suggesting labels and possible duplicates