'blast radius' 검색 결과

Audit an agent's harness against the four rings: containment, guides, sensors, permissions. Use when the user asks whether their agent setup is safe, wants a review of sandboxing / permissions / hooks / AGENTS.md guardrails, or asks what a bad session could break. Read-only: reports the blast radius and a hardening list, changes nothing. Do NOT use for context layout (context-audit) or cost routing (gate-check).

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

Trace error propagation through a multi-agent session by agent depth — where failures originated, the depth at which they appeared, and how they cascaded up to parent agents — using the Agent Monitor workflow intelligence API and the session event stream. Use when a multi-agent run failed and you need to find the origin and blast radius of the failure.

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

Systematic PR review with blast-radius analysis, security scanning, and breaking-change and test-coverage deltas. Use when reviewing PRs that touch shared libraries, APIs, database schemas, auth, or security-sensitive code.

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

Prevent Terraform/OpenTofu hallucinations by diagnosing and fixing failure modes: identity churn, secret exposure, blast-radius mistakes, CI drift, and compliance gate gaps. Use when generating, reviewing, refactoring, or migrating IaC and when building delivery/testing pipelines.

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

Explores codebase structure, affected files, blast radius, related tests, and local conventions for a focused topic. Use when review or planning needs structural lookup without bloating main context.

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

Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.

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

Security-focused differential code review with blast radius analysis, risk-adaptive depth (DEEP/FOCUSED/SURGICAL), git history correlation, and structured finding format. Adapted from Trail of Bits. Use when reviewing PRs, commits, or code changes for security implications.

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

Failure injection patterns, blast radius control, steady state hypothesis, and gameday planning for resilience testing.

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

Enhancement overlay for multi-agent / tool-using coder agents. Encodes the per-agent tool- scoping discipline that role-based frameworks (CrewAI, LangChain) document only as a passing best-practice: which agent gets which tool, and why blanket-sharing every tool to every agent is a correctness and blast-radius risk. Activates when an agent system has tools AND there is more than one agent (or one agent holding many tools). Treat a tool as a capability grant; scope by least-privilege. ENHANCE overlay — read alongside [[crewai]], [[agentsop-http-tool-wrapping]], [[agentsop-llm-tool-idempotency]]. Search keywords: which tools per agent, least-privilege agent, agent tool access, tool permissions, limit agent tools, scope tools to roles.overlay_type: enhancement

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

Deliberate-choice procedure for a medium-to-high-stakes engineering fork — when the first plausible solution (the instinct, the default next-token pull) would be costly to get wrong. Fires AUTONOMOUSLY: invoke proactively whenever a fork fits, never wait to be asked — mechanical triggers include a fix failing for the 2nd-3rd time, adding a dependency, schema/migration design, deleting or deprecating things others depend on, changing a public API, choosing an architecture or stack. Refuse the premature collapse: hold real options open (urge · contrarian · synthesis · out-of-box · intuitive dots · precedent · first-principles), ground each branch in at least one fact from outside the model (codebase, docs, benchmark, spike), future-model consequences (blast radius, reversibility, maintenance, pre-mortem), collapse by deliberate choice, then try to refute the winner before acting. Log the decision and rejected branches in docs/decision_logs/. Not for routine calls — a decision worth more than one forward pass.

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

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.

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

Builds or updates the code knowledge graph via tree-sitter AST and SQLite. Use when setting up the graph before search or blast-radius analysis.

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

Validate system resilience through controlled fault injection. Covers hypothesis-driven chaos experiments, failure injection types (network, service, infrastructure, dependency), LitmusChaos/Chaos Mesh/AWS FIS/Gremlin/toxiproxy tooling, automated abort gating, game day planning, and progressive chaos adoption. Use when: "chaos engineering," "fault injection," "resilience test," "game day," "failure recovery," "system reliability," "blast radius." Not for: safe rollout flags/canary/dark launch during a release — use testing-in-production; designing new tests from production telemetry — use observability-driven-testing. Related: testing-in-production, observability-driven-testing, performance-testing, release-readiness, test-environments.

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

Documents rollback procedures before making risky changes. Covers what's changing, verification steps, rollback procedures, and blast radius assessment. Use before database migrations, breaking API changes, infrastructure or DNS changes, large dependency upgrades, or any change where undo is not obvious.

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

Use when starting any security review in code_review - risk-tier each changed file, read the repo's own security patterns, compare, then trace source to sink, including removed guards and blast radius

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

Builds per-repo code graphs in JSON and markdown-ready derived artifacts. Use when you need blast radius, symbol-level maps, import graphs, inheritance, or test links.

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

Code understanding tool selection. Use when exploring architecture, finding definitions, tracing call chains, assessing blast radius of changes, or debugging code paths in the Genesis codebase.

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

Coordinates an active production incident by establishing command, reducing blast radius, preserving evidence, communicating verified impact, restoring service, validating recovery, and creating owned follow-up actions. Use for outages, severe degradation, security or data-integrity events, failed releases, and urgent operational triage. Not for a normal local bug, routine alert tuning, or a postmortem after the incident is already closed.

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

Analyzing pre-change impact across vertical (dependency chains, files) and horizontal (pattern consistency, naming) dimensions. Use to estimate blast radius before a refactor. No code.

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

Investigate and remediate data quality alerts using Monte Carlo MCP tools. Runs root cause analysis, assesses blast radius, discovers available tools (MCP/CLI/API), proposes and executes fixes, or escalates with full context when uncertain.

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

Structured incident response. Use when user reports an outage, production error, or says 'incident', 'something is down', 'users are affected'. Triage severity, contain blast radius, root-cause, document timeline, generate postmortem.

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

Triage mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for triage teams that diagnose an issue without changing it.

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

Entity-aware code change analysis using the pi-sem tools. Use when the user asks what changed, wants blast radius or affected tests, needs focused context for a function/class, wants review help on a commit/branch/PR, or asks to compare semantic diff with raw git diff. Prefer sem_context and sem_impact; use sem_diff selectively for summaries and reviews.

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

Design a chaos engineering experiment — hypothesis, blast radius, steady state, and abort conditions. Use when asked to "design a chaos experiment", "inject a failure", or "test the resilience of this service".

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