107건 · 관련도순
Use after the Lean model changed and before touching backend code — regenerates Kotlin from Lean, lists changed generated symbols, the hand-written files and contract tests that reference them, and golden regressions, so the blast radius is known before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing, reviewing, or debugging Terraform/OpenTofu modules, tests, CI, scans, or state ops - diagnoses failure mode (identity churn, secrets, blast radius, CI drift, state corruption) with version-aware guards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Focused Signals scout for PostHog setup health. Reads the project's active health issues — the deterministic findings of PostHog's own health checks (no live events, outdated SDKs, missing reverse proxy, absent web vitals, ingestion warnings, failing data-warehouse models, and more) — and decides which are genuinely worth surfacing. Unlike a one-signal-per-issue push, it bundles kind-clusters into a single finding, weights by real blast radius (cross-referencing actual event volume and reach), and prioritizes issues an agent can resolve via the MCP. Emits only above the confidence bar; otherwise writes durable memory and closes out empty. Self-contained peer in the signals-scout-* fleet — no dependencies on other skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze blast radius before making code changes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan safe refactors using blast radius and dependency mapping
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Author pull requests with intent-separated commits, blast-radius disclosure, and verification evidence. Load when opening a PR, writing a PR description, separating refactor from feature commits, or summarizing a change set for review. Also triggers on "write the PR", "PR body", "intent-separated commits", "split refactor from feature", "pr summary", or after safe-change cycles complete. Extends git-workflow-and-versioning — does not replace it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply one logical code change with mandatory impact mapping, git snapshot, verification, and automatic revert on failure. Load when the user asks for a safe edit, verified change, one change at a time with rollback, or codespine-style edit loop. Also triggers on "safe change", "edit with verification", "don't break the build", "revert if tests fail", or any non-trivial code edit where blast radius matters. Always runs dependency-mapping first. Pairs with incremental-implementation for multi-slice work; this skill is one atomic verify cycle per invocation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Chaos Engineering discipline — proactive experimentation on distributed systems to build confidence in their resilience. Covers Netflix-inspired chaos principles, experiment design, blast radius control, LitmusChaos and Chaos Mesh usage, game day planning, and production safety. USE WHEN: validating system resilience before production incidents, designing chaos experiments, planning game days, implementing CI/CD chaos pipeline, or building confidence in fault tolerance. Triggers on "chaos engineering", "chaos experiment", "game day", "resilience test", "fault injection", "Litmus", "Chaos Mesh", "break things on purpose".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.