'severity' 검색 결과

Check a Kiln branch or pull request through real browser interactions. Multiple agents test separate feature areas in isolated environments, then combine findings into a severity-ranked Markdown report with reproduction steps and expected versus actual behavior.

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

• Checking all new behavior in a branch or pull request
• Testing multiple feature areas in parallel
• Finding UI text issues and inconsistent interactions

Review vulnerability findings before drafting a bug bounty report. Seven validation questions and submission checklists help assess scope, reproducibility, demonstrated impact, duplicate reports, and whether the claimed severity matches the available evidence.

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

• Decide whether a finding is ready to report
• Recheck suspected authentication bypasses
• Match severity claims to demonstrated impact

Turn validated vulnerabilities into clear bug bounty reports for HackerOne, Bugcrowd, Intigriti, or Immunefi. Platform templates help organize demonstrated impact, reproducible steps, supporting evidence, severity reasoning, and concrete fixes in language reviewers can follow.

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

• Draft a report using a platform-specific template
• Write clear titles and impact summaries
• Organize reproduction steps and supporting evidence

Triage a raw bug report into something a team can act on — clean repro steps, a defensible severity/priority, environment, likely area/owner, and duplicate check. Use when asked to triage this bug, set severity and priority, is this a P1, or clean up this bug report for the backlog. Produces the normalized repro, a severity and priority with the reasoning (impact × frequency × workaround), the environment/metadata, a suspected component and owner queue, and a duplicate/related-issue check — flagging when info is missing rather than guessing.

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

Production incident response. Use when handling incidents, classifying severity, reconstructing timelines, writing postmortems, generating comms templates, or building response playbooks with severity scoring and RCA frameworks.

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

Systematic QA testing for web applications, desktop apps, and workflows. Three tiers: QUICK (critical/high severity only — 5 min), STANDARD (+ medium severity — 15 min), EXHAUSTIVE (+ cosmetic — 30+ min). Tests user flows, finds bugs, reports with severity classification, and optionally auto-fixes with atomic commits. Produces before/after health scores and ship-readiness summary. Use when user says "test this", "QA", "find bugs", "does this work?", or "is it ready to ship?". Voice triggers: "quality check", "run QA", "test the app". For report-only (no fixes), use with --report-only flag.

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

인공지능 에이전트의 문제를 지시, 기억, 도구 실행, 화면 표시 등 12개 계층에서 조사합니다. 코드와 로그를 근거로 원인을 정리하고 심각도에 따른 지적 사항과 수정안을 제시합니다.

• 앱 안에서만 발생하는 문제 조사
• 이전 대화가 섞이는 원인 확인
• 도구 실행 누락과 허위 실행 보고 확인

Retrieve climate-related disaster records, including floods, cyclones, droughts, and heatwaves. Check affected countries, severity, status, and population figures, then consult climate anomalies and related news for broader context.

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

• Check ongoing floods and cyclones
• Review disaster severity and affected populations
• Explore climate anomalies and related news

Check internet disruptions using Cloudflare Radar data. Filter detected outages by country and time window, then review their location, cause, severity, and end time to understand regional failures or nationwide shutdowns.

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

• Check ongoing internet outages in a country
• Review disruptions detected during a selected period
• Investigate reported shutdowns or cable cuts

Check current airport delays and cancellations worldwide, including delay types, severity, average delay minutes, and the share of flights affected. Use airport-level alerts to understand disruption before a trip or review conditions across a region.

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

• Checking airport disruption before departure
• Reviewing airports with severe delays
• Checking delayed-flight shares and cancellation counts

Run three static audits covering architecture alignment, threats, and MCP server policies, permissions, and dependencies. Store timestamped results, track changes across runs, and fail scheduled CI jobs when findings reach a chosen severity.

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

• Running weekly architecture and security audits
• Reviewing MCP permissions and dependency findings
• Comparing audit records over time

Audit a codebase across nine areas, including architecture, tests, security, and documentation. Produces TECH_DEBT_AUDIT.md with source locations, severity ratings, estimated repair effort, and prioritized recommendations to help plan maintenance work.

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

• Assessing a codebase before maintenance
• Prioritizing technical debt fixes
• Checking architecture and code consistency

Audit a codebase with three vulnerability hunters and two engineers who build small demonstrations of suspected flaws. Verify attack paths, assess severity from demonstrated impact, and report evidence, targeted fixes, and checks to prevent recurrence.

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

• Review security before a release
• Audit security risks in a pull request
• Verify whether a suspected flaw is exploitable

Integrate harmful-content checks into Python applications using Azure AI Content Safety. Analyze text and images by category and severity, and manage custom text blocklists to help review user submissions or AI-generated content before display.

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

• Checking user-submitted text for harmful content
• Analyzing harmful-content categories in uploaded images
• Reviewing AI-generated text before displaying it

Build content moderation features in Java with Azure AI Content Safety. Analyze text and images for harmful content, retrieve severity scores by category, and manage custom blocklists, which are lists of terms to flag.

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

• Checking submitted text for harmful content
• Analyzing images from files or URLs
• Managing custom lists of prohibited terms

Design production alerts, route notifications by severity, and organize on-call schedules. Use configuration examples to define backup contacts, escalation steps when alerts go unanswered, and runbooks that guide responders through incident investigation.

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

• Define alert thresholds and severity levels
• Route notifications to Slack and PagerDuty
• Plan on-call rotations and holiday coverage

Review a pull request or code diff for bugs by reading callers, expected behavior, and nearby error handling. Receive findings tied to specific lines, ranked by severity, plus a summary of merge risks and needed tests.

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

• Checking a pull request for behavioral regressions
• Reviewing risks to stored data
• Investigating input validation and access checks

Turn defects found during Oracle-to-PostgreSQL migration into structured bug reports. Document expected and actual behavior, reproduction steps, severity, root causes, proposed changes, and validation on both databases so teams can act on the findings.

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

• Documenting behavioral differences found during migration
• Organizing reproduction steps and test data
• Recording fixes, affected files, and validation steps

Review a diffusers contribution before opening a pull request. Check the full change against project rules, trace potentially unused code, and receive a severity-based report separating required fixes from points to discuss with reviewers.

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

• Checking a diffusers contribution before opening a pull request
• Investigating potentially unused code in a change
• Reviewing fixes again and preparing notes for reviewers

Build automated responses to AWS GuardDuty security findings using EventBridge and Lambda. Configure severity filters, isolate EC2 instances, disable compromised access keys, preserve disk snapshots for investigation, and send notifications to security teams.

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

• Triggering responses to high-severity GuardDuty findings
• Isolating EC2 instances and preserving investigation data
• Disabling compromised IAM access keys

Set up and operate Amazon GuardDuty to detect threats in AWS. Configure protection features, centralize findings across accounts, investigate suspicious activity, and build automated responses with EventBridge and Lambda, including containment of potentially compromised resources.

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

• Setting up threat detection for AWS accounts
• Investigating credential abuse and compromised instances
• Automating responses to high-severity findings

Design a security operations center escalation matrix that defines incident priorities, response deadlines, analyst responsibilities, and notification paths. Use business impact, asset importance, and data sensitivity to decide when incidents need senior or management attention.

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

• Defining incident priorities and response deadlines
• Clarifying handoffs between analyst tiers
• Setting escalation rules for overdue incidents

Build dashboards that show how long vulnerabilities remain unresolved and compare remediation times with severity-based deadlines. Define response policies, automate escalation notices, and report compliance rates and other measures of remediation progress.

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

• Define vulnerability remediation deadlines
• Visualize overdue vulnerabilities
• Automate reminders and management escalations

Present results returned by a Codex helper while preserving findings, severity, file references, and uncertainty. This internal guidance also covers reporting edited files, failed runs, and setup requirements, with user confirmation before fixing review findings.

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

• Present review findings in order of severity
• Keep observed evidence separate from inferences
• Report files changed by Codex