'coverage' 검색 결과

Add end-to-end tests, which check complete usage flows, and API tests for features that already work. Follow the project's existing test setup to extend automated coverage without introducing a separate testing approach.

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

• Adding automated tests to an existing feature
• Testing complete usage flows with E2E tests
• Adding API tests using the existing test setup

Read, query, filter, and write genomic files with pysam in Python. Extract regions, summarize variants, and count aligned bases while handling coordinate conventions, file indexes, headers, and the reference sequences needed to decode CRAM files.

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

• Inspect genomic file formats, headers, and indexes
• Filter alignment records by quality and flags
• Summarize variants and genotypes in a genomic region

Draft and revise scientific manuscripts while linking claims to verified evidence. The skill organizes source records, checks consistency across text and results, tracks reporting requirements, and reviews references and disclosures, with human verification and final approval.

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

• Drafting manuscript sections from verified evidence
• Checking consistency across text, tables, and results
• Reviewing references and reporting checklist coverage

Prepare and analyze genomic intervals, regions defined by chromosome coordinates, with Gtars. Validate BED files, compare overlaps and coverage, combine region sets, and plan tokenization or reference storage while tracking data provenance and resource limits.

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

• Validating BED coordinates and reference assemblies
• Counting overlaps and comparing genomic region sets
• Converting genomic intervals into token IDs

Plan reviews of AI-generated code before running or merging it. Define language-specific checks, tests in isolated environments, and evidence requirements, while recording coverage limits and gaps that prevent approval.

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

• Planning reviews of AI-generated code before merging
• Defining language-specific security checks
• Recording test evidence and unresolved gaps

Create and organize Python tests with pytest. Use reusable setup, mock replacements for external services, controlled test time, and coverage reports to check normal behavior, failures, retries, and interactions between application components.

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

• Add unit and integration tests to Python code
• Replace external services with mocks in tests
• Check retry behavior and time-dependent logic

Identify a project's existing test tools and conventions, then run the smallest useful test suite for a specific change. Add or update tests when authorized, and report commands, results, and remaining gaps without overstating coverage.

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

• Run relevant tests for a specific code change
• Identify existing test tools and conventions
• Add or update tests with authorization

Convert feature requirements and implementation plans into a test strategy, task checklist, and quality assurance plan for GitHub projects. Define test coverage, priorities, dependencies, estimates, and quality checkpoints using established testing and software quality frameworks.

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

• Plan testing from feature requirements and implementation documents
• Break testing work into tasks for GitHub issue management
• Prioritize performance, security, and accessibility checks

Organize SGLang GPU operations when adding or moving code. It guides API placement, operation registration, test organization, and migration checks to preserve existing behavior, references, and continuous integration coverage.

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

• Choose where to place a new GPU operation
• Split or move existing operation files
• Review API registration and test placement

Check investment research for bias before searching and before writing conclusions. A short checklist broadens coverage beyond large companies and English sources, challenges bullish assumptions, and checks whether important figures are current.

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

• Include smaller companies and suppliers in stock screens
• Expand supply chain research to local language sources
• Test investment theses against opposing evidence

Finds and retrieves paid financial datasets when free sources lack coverage or detail. Guides comparison of providers, success rates, prices, and required inputs, while keeping execution costs and remaining credits visible.

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

• Finding financial data missing from free sources
• Comparing paid providers by cost and success rate
• Checking parameters before a paid data request

Investigate attempts to gain higher privileges on Windows and Linux using endpoint and security logs. Guide hypothesis testing, evidence analysis, false-positive checks, and reporting to help assess suspicious privilege changes and the scope of a compromise.

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

• Hunting for signs of privilege escalation
• Investigating alerts about suspicious privilege changes
• Assessing compromise scope during incident response

Investigate stolen Kerberos tickets, authentication credentials that can be reused without a password, by correlating Windows security events. Build Splunk or Elastic detection rules for cross-host reuse, weaker encryption, and unusual request volumes, and report risk-scored findings.

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

• Investigating suspected reuse of stolen Kerberos tickets
• Building Splunk or Elastic detection rules
• Finding unusual ticket request volumes

Investigate Pass-the-Hash attacks, where stolen password hashes are reused for authentication. Examine unusual NTLM logins alongside credential theft indicators, validate suspicious findings across security logs, and document evidence, affected hosts, confidence, and recommended responses.

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

• Hunting for movement using stolen password hashes
• Triaging suspicious NTLM login alerts
• Assessing the scope of a compromise

Investigate signs of Mimikatz credential theft using command lines, access to Windows authentication memory, file indicators, and known modules in memory. Correlate endpoint and security logs to assess suspicious alerts, document evidence, and recommend response actions.

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

• Investigating alerts about Windows authentication memory access
• Hunting for signs of credential theft
• Assessing compromise scope during incident response

Analyze Sysmon logs to investigate process injection, where malicious code hides inside legitimate processes. Correlate remote thread creation, cross-process access, and unusual DLL loading, then organize findings by injection type, risk level, and ATT&CK technique.

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

• Investigating EDR alerts about suspicious cross-process access
• Hunting for malicious code hidden inside legitimate processes
• Checking Sysmon coverage for process injection detection

Investigate suspicious privilege increases, including Windows UAC approval bypasses and Linux sudo or setuid abuse. Use registry changes, process relationships, and permission changes to identify possible abuse and document affected hosts, methods, and risk levels.

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

• Investigating Windows UAC bypass activity
• Tracing how administrative access was obtained
• Monitoring Linux sudo and setuid abuse

Set up decoy credentials, storage, and secrets across AWS, Azure, and GCP to detect suspicious access. Connect audit logs to security alerts, verify detection, and document permissions, resource inventories, and maintenance plans.

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

• Detecting use of leaked cloud credentials
• Monitoring suspicious access to decoy storage and secrets
• Extending on-premises deception coverage to cloud environments

Build dashboards and reports for security operations teams using incident and alert data. Track detection and resolution times, false alarms, analyst workload, and detection coverage to assess operational trends and the effects of improvement initiatives.

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

• Preparing monthly or quarterly security operations reports
• Reviewing analyst workload and shift staffing
• Comparing performance before and after tool adoption

Write and run tests for features and fixes, starting with likely failures and boundary cases. Use behavior-focused checks, suitable test environments, and coverage results to assess whether changes are ready.

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

• Writing tests for a new feature
• Adding regression tests for a bug fix
• Updating existing tests after behavior changes

Validates skill files and registration consistency, then checks project tests and system health. Compares failures with recent changes to distinguish regressions, outdated tests, intermittent failures, and infrastructure issues, producing a report that tracks results over time.

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

• Validating definitions and registration for new skills
• Running daily tests and system health checks
• Classifying failures after code changes

Check your gbrain setup and receive prioritized suggestions for overdue updates, pending migrations, stalled jobs, and other maintenance issues. Findings include repair commands, while any fixes require your approval.

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

• Reviewing your gbrain setup
• Getting a weekly maintenance check
• Prioritizing updates and stalled jobs

Build or refresh a strategic customer account plan from sales records, emails, and meeting transcripts. Organize goals, stakeholders, growth opportunities, risks, and dated actions into a document, then sync approved highlights to the customer relationship management system.

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

• Creating a quarterly plan for a key customer
• Refreshing an existing account plan
• Reviewing stakeholder coverage and growth opportunities

Review sales opportunities by stage to see deal totals, aging, and risks. Identify stalled deals, overdue closing dates, and missing next steps, then compare available opportunities with sales targets and recommend where to focus.

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

• Preparing a weekly sales pipeline review
• Finding stalled deals and overdue closing dates
• Checking whether opportunities cover a sales target