21건 · 관련도순
Assess the impact of code changes with GitNexus by tracing callers, dependencies, and affected execution flows. Check existing changes and report their scope, risk, and uncertainty before editing or committing.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Assess how changes, failures, or paused updates to a BigQuery table or view affect downstream assets. Trace data lineage, the relationships showing where data flows, and summarize dependent tables, dashboards, and processes with direct and indirect impacts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Trace where BigQuery and Cloud Storage data comes from and where it goes. The skill summarizes table or column lineage, meaning data origins and movement, in a readable Markdown report to support data quality investigations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze weather data impact on construction schedules. Predict weather delays, optimize work scheduling based on forecasts, and calculate weather-related risk factors for project planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes code change impact with risk scoring and affected-node mapping. Use before merging to understand what a change touches and what lacks test coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Calculates dilutive impact of equity issuance on existing shareholders with EPS, ownership, and NAV per share analysis. Use when modeling dilution, communicating shareholder impact, or comparing capital raise alternatives.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Git-aware smart revert for tracks, phases, and tasks. Handles rewritten history, finds related commits, and provides safe rollback with multiple confirmation gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarizes Google Cloud Data Lineage graphs to help users debug data quality issues and understand data provenance for BQ/GCS. Use when summarizing upstream and downstream data flows, and presenting complex lineage data as an intuitive Markdown report. Don't use for generic BigQuery queries, editing lineage relationships, or downstream deprecation. Don't use for downstream blast-radius impact analysis (use datalineage-bigquery-asset-impact-analysis skill instead).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes the downstream impact (blast radius) when a BigQuery table or view is broken, stale, or modified. Identifies all downstream tables, dashboards, and processes that will be affected. Use when: - Performing a blast radius or impact analysis for a BigQuery table or view. - Assessing the consequences of modifying, deleting, or pausing updates to a BigQuery asset. - Identifying downstream dependencies (tables, dashboards, processes) of a BigQuery asset. Don't use for: - General BigQuery querying or data analysis (use BigQuery-related tools instead). - Non-BigQuery assets (e.g., Cloud Storage files) unless they are part of the BigQuery lineage. - Creating or modifying lineage links directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenLineage, DataHub, Marquez for data lineage tracking and impact analysis. Activate on: data lineage, OpenLineage, DataHub, Marquez, impact analysis, data catalog, column lineage, data discovery. NOT for: data quality validation (use data-quality-guardian), dbt documentation (use dbt-analytics-engineer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a company needs recovery objectives it can defend, before a continuity plan, a disaster recovery design, an audit or a resilience review, and asks "do a BIA", "business impact analysis", "set our RTO and RPO", "what is our maximum tolerable downtime", "which services are critical", "impact tolerance" or "can our backups meet our recovery targets". Lists services from the customer's view, prices an outage over time in the company's own money and obligations, sets recovery time and data loss objectives, maps dependencies, and compares each objective with what backups, restore tests, suppliers and people actually allow, listing the gaps for a decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
diff-time で「影響範囲を repo 全体で調査した証拠」「失敗系を検証した証拠」「外部依存・レート制限・キャッシュ整合を確認した証拠」の欠落を検出する evidence-sufficiency 観点。defect そのものは既存 skill へ委譲し、本 skill は「そのリスク種別を調査した証拠が差分・PR 本文・テストに残っているか」の meta 評価のみを行う。証拠が同一 diff に同梱（テスト・canary・grep 記録）されていれば充足とみなす
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze blast radius before making code changes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenLineage, DataHub, Marquez for data lineage tracking and impact analysis. Activate on: data lineage, OpenLineage, DataHub, Marquez, impact analysis, data catalog, column lineage, data discovery. NOT for: data quality validation (use data-quality-guardian), dbt documentation (use dbt-analytics-engineer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "このファイルを変えたら何が壊れる？", "what depends on this function", "影響範囲を調べて", "show me what imports this module", or wants to understand the blast radius before modifying a shared utility, exported type, or public API. Traces import/require references up to two levels deep and lists affected test files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.