「severity」の検索結果

Hybrid fingerprint + LLM pipeline for bug classification, deduplication, and ticket generation. Normalizes CI logs, creates stable fingerprints, clusters near-duplicates, then uses LLM for severity classification and ticket writing. Includes bug reporting templates and severity/priority matrix. Use when: "bug triage," "classify bugs," "failure analysis," "auto-classify," "CI failures," "bug report," "defect template." Not for: runtime self-healing of one flaky locator — use test-reliability. Not for: designing new tests from production telemetry — use observability-driven-testing. Related: qa-metrics, qa-dashboard, ci-cd-integration, qa-project-context.

日本語の概要は準備中です。原文の説明を表示しています。

Bug bounty report triage, validation, and severity escalation. Use when the user provides a bug bounty report to validate, wants to check if a finding is submittable, needs to escalate severity for maximum payout, or says 'triage this', 'validate this report', 'escalate this', 'is this submittable', 'check this bounty report', 'max bounty', or 'will this get accepted'.

日本語の概要は準備中です。原文の説明を表示しています。

Open, classify, and escalate support cases with Salesforce Technical Support via the Help portal: choosing severity, engaging Premier Success, the Escalate to Technical Support Management path, tracking incidents on the Trust site. NOT for escalating your own org's cases after N hours - use admin/escalation-rules. NOT for SLA milestone timers and entitlement processes - use admin/entitlements-and-milestones.

日本語の概要は準備中です。原文の説明を表示しています。

Classify the severity of hypercalcemia at the bedside — mild, moderate, or severe — by combining the corrected/ionized calcium level with the acuity and symptom pattern, and decide whether the patient needs urgent therapy. Trigger when a clinician asks "is this hypercalcemia severe", "how bad is this calcium level", "when to admit for hypercalcemia", "is this hypercalcemic crisis", "how to grade hypercalcemia", or shares a calcium level and asks how worried to be.

日本語の概要は準備中です。原文の説明を表示しています。

This skill categorizes hypercalcemia of malignancy (HCM) severity using albumin‑adjusted serum calcium into mild (<12 mg/dL), moderate (12‑14 mg/dL), or severe (>14 mg/dL). Use it when a clinician needs to stage HCM to guide initial therapy choices, such as deciding between observation, IV bisphosphonate/denosumab, or calcitonin‑based combination regimens.

日本語の概要は準備中です。原文の説明を表示しています。

Clinical Decision Support System (CDSS) development patterns. Drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), alert severity classification, and integration into EMR workflows. Use when building clinical decision support — drug interaction checks, dose validation, clinical scoring, or alert severity.

日本語の概要は準備中です。原文の説明を表示しています。

Build a structured SOC escalation matrix defining severity tiers, response SLAs, escalation paths, and notification procedures for security incidents.

日本語の概要は準備中です。原文の説明を表示しています。

Turns reported data problems (messages, tickets, meeting notes, complaints) into one DRAFT issue log: one row per issue with the symptom as reported, dataset and fields named, reproduction steps, affected reports, first seen date, reporters, a suggested owner, and blank severity, root cause and status cells for the owner. Never asserts a root cause, severity or fix. Use when the user asks to "log these data issues", "turn these complaints about the numbers into an issue list", "build the data quality backlog", "which reports are hit by this data problem" or "write up the reproduction steps for this data bug". Do not use for exploring or profiling a dataset, use dataset-insight-pack instead; for an IT incident write-up, use incident-postmortem-drafter; for tracking fix actions once assigned, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

技術記事の並列レビュー Council。anti-ai-slop / fact-checker / narrative-critic / reader-advocate を並列 spawn、severity 付き findings を最大3ラウンドで収束。Zenn などのドラフト完成後に使う。「記事レビュー」「editorial swarm」「編集会議」「記事推敲」「記事添削」で発動。

Build a structured SOC escalation matrix defining severity tiers, response SLAs, escalation paths, and notification procedures for security incidents.

日本語の概要は準備中です。原文の説明を表示しています。

Syncpack (モノレポ依存バージョン同期ツール) リファレンス。 .syncpackrc 設定、lint / fix / update / format コマンド、 versionGroups, semverGroups, updateGroups, customTypes, source, catalog プロトコル, semverRangeOnly, minimumReleaseAge, severity, sourceMode, package.json 整列、依存バージョン揃え、CI 連携。

差分が「その差分自身を審査するレビュー基準・品質ゲート」を弱めていないかを diff-time で検出する。Check 1 レビュールールの削除・弱体化（.river/rules.md / .river/rules.d/*）、Check 2 実行時コンフィグの閾値・ゲート緩和（.river-review.{json,yaml,yml} の review.severity 引き下げ / exclude 拡大 / memory.suppressionEnabled 無効化 / selection.skills.exclude 追加）、Check 3 suppression entry の新規追加、Check 4 lint・静的解析設定からのルール削除や無効化、Check 5 branch protection・required check の緩和、の 5 Check を対象とし、これらが機能変更と同一 PR に混在し、かつ意図の宣言が無い場合に指摘する。report-only。workflow の permissions / action pin は gha-workflow-security、既存 suppression entry の使い分けは suppression-feedback、設定ファイルの一般的妥当性は config-json、.only / .skip / @ts-ignore / @ts-nocheck は heuristic-review.mjs の決定論検出器、リファクタと機能追加の混在は behavior-structure-separation へ委譲する

Build a structured SOC escalation matrix defining severity tiers, response SLAs, escalation paths, and notification procedures for security incidents.

日本語の概要は準備中です。原文の説明を表示しています。

OpenClawのセキュリティ勧告を確認・修正し、非公開フォークの未完了PRや公開条件を検証。承認を経た公開と、公開後の状態確認まで扱うスキル。

• 勧告と非公開フォークの状態確認
• 脆弱性情報や重大度を更新したいとき
• 承認前に公開条件を確認したいとき

機能の実装後やマージ前に、別のエージェントへコードレビューを依頼します。変更内容と要件、対象のコミットを渡し、指摘の重要度に応じて修正を進めるスキルです。

• 大きな機能を実装した後のレビュー
• マージ前に変更を確認したいとき
• 複雑な不具合修正への第三者確認

コーディングの作業ログを振り返り、ファイルの探しやすさ、自動チェック、指示文、ツール利用などを点検して、次回に向けた環境改善案を重要度順に整理するスキル。

• 時間がかかった開発作業の振り返り
• 繰り返すミスの自動チェックを探したいとき
• エージェント向け指示を整理したいとき

Retrieve current airport delay and cancellation alerts worldwide — delay type, severity, average delay minutes, and affected-flight percentages per airport. Use when the user asks whether an airport is delayed, disrupted, or experiencing cancellations.

日本語の概要は準備中です。原文の説明を表示しています。

Retrieve detected internet outages (Cloudflare Radar) with country, cause, severity, and time bounds. Use when the user asks whether a country's internet is down, throttled, or experiencing a shutdown.

日本語の概要は準備中です。原文の説明を表示しています。

Retrieve active cyber-threat intelligence — malware IOCs, C2 infrastructure, and CISA known-exploited vulnerabilities — filterable by type, source, and severity. Use when the user asks about current cyber threats, IOCs, or actively exploited CVEs.

日本語の概要は準備中です。原文の説明を表示しています。

Static security scan of a harness's declared MCP surface via `harness mcp-scan {path}`. Reads `.mcp/servers.json` + `.harness/claims.json`. Pure-read, no dispatch. Exits 1 on findings at or above `--fail-on` severity.

日本語の概要は準備中です。原文の説明を表示しています。

Team Mode security research skill. Orchestrates 3 vulnerability hunters and 2 PoC engineers to audit a codebase in parallel, prove exploitability, classify root causes, and calibrate severity by actual exploitability. Use for security review, vulnerability research, exploitability audit, pre-release security check, threat model validation, and `/security-research`. Triggers: 'security-research', 'security research', 'security review', 'vulnerability audit', 'exploitability audit', '보안 리뷰', '취약점 감사'.

日本語の概要は準備中です。原文の説明を表示しています。

Thorough, file-cited technical debt audit across 9 dimensions using AST-grep (tree-sitter), grep, LSP, and language-native tooling. Produces TECH_DEBT_AUDIT.md with severity, effort estimates, and prioritized fixes. Use when asked for codebase health check, tech debt audit, architecture review, code quality assessment, or cleanup planning. Triggers: 'tech debt', 'technical debt', 'debt audit', 'code health', 'technical debt audit', 'codebase health check', 'find tech debt', 'debt analysis', 'audit code quality'.

日本語の概要は準備中です。原文の説明を表示しています。

Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use after a Strix scan reports findings, or when the user asks to remediate, patch, or fix security issues from a strix_runs report, vulnerabilities.json, findings.sarif, or a cloud scan.

日本語の概要は準備中です。原文の説明を表示しています。

Azure AI Content Safety SDK for Python. Use for detecting harmful content in text and images with multi-severity classification.

日本語の概要は準備中です。原文の説明を表示しています。