sidstack-impact-safe

Name: sidstack-impact-safe
Rating: 87
Author: junixlabs

在进行高风险变更前，先执行影响分析。当您对核心模块（共享模块、数据库、认证模块）进行修改，或更改 API、调整数据库结构，触及安全相关代码，又或是对多个模块产生影响时，可触发此步骤。随后，先执行 impact_analyze，再进行 impact_check_gate。

SKILL.md

--- frontmatter

name: sidstack-impact-safe
description: >
  Run impact analysis before risky changes. Trigger when: modifying core modules
  (shared, database, auth), changing APIs or schemas, touching security code,
  or affecting multiple modules. Use impact_analyze then impact_check_gate.

Impact-Safe Changes

When to Run Impact Analysis

•Modifying core modules (database, auth, shared)
•Changing API routes or response schemas
•Database schema changes or migrations
•Security-related code (auth, encryption)
•Changes affecting 3+ files across modules

Process

1. Analyze

code

impact_analyze({
  description: "What you're changing and why",
  targetModules: ["module1", "module2"],
  changeType: "feature" | "refactor" | "bugfix" | "migration"
})

2. Check Gate

code

impact_check_gate({ analysisId: "from-step-1" })

3. Interpret

Status	Action
`clear`	Safe to proceed
`warning`	Proceed with extra care
`blocked`	Fix blockers first