'duplication' 검색 결과

코드 변경과 호출부를 읽고 버그, 보안, 부하, 테스트, 속도, 불필요한 구현을 점검합니다. 구체적인 문제 사례와 최소 수정안, 미해결 시 영향을 우선순위에 따라 보고합니다.

• PR이나 최근 커밋을 검토합니다
• 보안과 데이터 손실 위험을 확인합니다
• 예상 부하의 문제와 테스트 누락을 확인합니다

코드를 기능별 흐름도로 정리하고 중복 로직을 조사합니다. 근거가 있는 통합안과 각 시스템을 `/make-plan`에 넘길 요청문을 작성합니다.

• 리팩터링 전 기능별 처리 흐름 파악
• 기능 내부와 기능 간 중복 로직 조사
• 통합안과 기존 호출 위치 비교

Review source code for readability, complexity, duplication, and maintainability without changing files. Receive a structured report with prioritized issues, refactoring suggestions, positive findings, and estimates of technical debt—the work needed to address accumulated code problems.

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

• Review the quality of an authentication module
• Find duplicate code and overly long methods
• Assess accumulated code problems and repair effort

Review image alt text, the descriptions read by screen readers, for unnecessary phrases and duplication of nearby text. Identify specific images to fix and make their descriptions concise while preserving information about what the images mean.

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

• Reviewing image descriptions for accessibility
• Removing alt text that repeats nearby captions
• Checking screen reader output after fixes

Review images and their visible captions, then connect them with figure and figcaption markup. Check caption placement and alternative text so screen readers can present the relationship between an image and its description.

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

• Reviewing HTML for images with captions
• Checking captions and alternative text for duplication
• Improving screen reader access to image descriptions

Clean up AI-generated code in branch changes or selected files while preserving behavior. Establish passing regression tests first, then remove unnecessary code and complexity, run project quality checks, and report both changes and skipped issues.

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

• Cleaning up recent AI-generated changes
• Removing redundant comments and dead code
• Simplifying duplication and excessive complexity

Maintain Cherry Studio documentation by checking it against source code, placing facts in appropriate files, and removing duplication. Review documentation affected by code changes and keep relevant English and Chinese counterparts aligned.

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

• Organizing READMEs and reference documentation
• Reviewing documentation affected by code changes
• Checking comments and agent instructions against code

Improve existing code structure while preserving its behavior. Review dependencies and tests, identify maintainability problems such as duplication or long functions, and plan small changes with testing, reversible commits, and a final comparison of results.

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

• Splitting long functions into smaller, clearer functions
• Removing duplicated logic and unused code
• Planning improvements to hard-to-maintain legacy code

Research social discussions using public posts or authorized exports, and produce reports that link each claim to inspected evidence. Track duplicate posts, distinguish speakers, document access gaps, and audit conclusions that exceed the observed sample.

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

• Comparing product discussions across social platforms
• Creating cited reports from supplied post exports
• Checking repost duplication and comment attribution

Design and refactor Python components with clear responsibilities and simple structure. Assess when to split large classes, combine objects instead of extending them, and extract shared code without introducing unnecessary abstractions.

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

• Defining responsibilities for a new Python component
• Splitting oversized classes and functions
• Deciding when to extract shared code

Organize parallel code reviews across security, performance, architecture, testing, and accessibility. It helps assign review areas, merge duplicate findings, apply consistent severity ratings, and produce one report with locations, impacts, suggested fixes, and prioritized actions.

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

• Assigning review areas for a code change
• Merging duplicate findings from multiple reviewers
• Aligning severity ratings across review reports

Consolidate established lessons from domain memory files into reusable agent instructions. Review proposed additions before merging, preserve details while reducing duplication, and remove merged entries from the memory file afterward.

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

• Turn accumulated lessons into reusable instructions
• Consolidate overlapping guidance
• Maintain project-specific instructions

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

Clean up working code by identifying duplication, dead code, unnecessary layers, and error paths that hide failures. Preserve behavior with targeted tests, simplify the requested files in stages, and report verification results and remaining risks.

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

• Simplify bloated or repetitive AI-generated code
• Remove unused code and unnecessary wrappers
• Review fallback paths that hide errors

Manage LinkedIn connection requests and follows with the Curviate CLI. Review pending invitations, preview actions, withdraw requests, and list connections or followers, with guidance on duplicate requests and delays before invitations appear.

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

• Sending connection requests with a personal note
• Reviewing received invitations
• Withdrawing pending connection requests

Evaluate Vitest tests by the observable behavior and realistic regressions they protect. Guide new test authoring and review existing suites for duplication, dependence on implementation details, and code used only by tests, with evidence for retention or removal.

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

• Checking the value of a new or changed Vitest test
• Finding overlapping tests that can be consolidated
• Reviewing tests that break during behavior-preserving refactoring

Maintain LangBot skill assets by organizing operating rules, reference guides, test cases, fixtures, and troubleshooting entries. Check existing material before adding files, keep detailed instructions in one place, and verify that indexes stay current.

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

• Add a skill without duplicating existing guidance
• Organize reference guides and test cases
• Consolidate troubleshooting for shared causes

Research prospective customers from public sources, add company and contact details, score their fit, and merge duplicate records. Organize the findings into prioritized lead lists with source information, using CSV, JSON, or Markdown tables.

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

• Find companies matching an ideal customer profile
• Add funding and hiring details to lead records
• Score prospects to set sales priorities

Turn rough meeting notes, customer requests, and product ideas into structured backlog entries, a list of possible improvements. Capture who needs each idea and why, categorize it, and update matching entries with new evidence.

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

• Capturing feature ideas after a meeting
• Recording requests from customers or sales
• Logging product gaps found in competitor research

Review assigned code changes against project conventions, architecture, and intended behavior. Verify findings with source code and tests, classify their severity, and record a merge readiness verdict, with an optional deeper process for independent reviews and resolving disagreements.

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

• Reviewing assigned code changes
• Checking duplication and inconsistent patterns
• Reviewing fixes that lack a written specification

Process SARIF files, a standard format for static analysis results, to filter alerts, remove duplicates, combine findings from multiple tools, and produce reports. It also supports comparing runs and integrating result checks into CI/CD pipelines.

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

• Combine findings from multiple security scanners
• Filter alerts by severity and remove duplicates
• Compare earlier and current results for new issues

Add, extend, or review OpenAI Ads conversion tracking for purchases, signups, and other confirmed outcomes. The skill covers browser Pixel events, server-side Conversions API events, duplicate-event prevention, secret handling, and local verification with a setup report.

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

• Add tracking for completed purchases and signups
• Send conversion events from a server
• Prevent duplicate counting across Pixel and CAPI

Guide code changes in iPolloWork by reusing existing implementations, limiting new files and dependencies, and keeping responsibilities clear. Review runtime costs, run focused checks, and audit the final changes for duplication and maintainability issues.

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

• Checking for reusable code before implementing a feature
• Removing duplicate implementations during refactoring
• Reviewing the need for new files and dependencies

Find business logic repeated across software components, such as notifications, auditing, and validation. Compare responsibilities and dependencies, then recommend a shared service, shared library, or component merger with a prioritized consolidation plan.

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

• Finding duplicate business logic before refactoring
• Reviewing whether notification components should be merged
• Identifying candidates for shared services or libraries