// Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.
End-to-end change-shipping closed loop for non-trivial work — research → proposal doc → phased guarded implementation → PR self-review → harden → merge. Use when taking a substantial change from idea to merged PR, when a task needs a written proposal before code, when implementing in reversible phases behind a guarded commit chain (assert + test + verify, all green before commit), or when self-reviewing your own PR. Complements automating-devops (which is the git/CI/release knowledge reference); this skill is the orchestration spine that sequences a change from zero to merged.
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image publishing, testing, monitoring, or infrastructure automation.
Distills AI agent personality patterns from conversation into a Tech Persona Card v1.0, validates the schema and voice consistency, and routes contributions through the existing submission portal. Use when the user wants to crystallize a recurring voice/tone, fork an existing persona, or share one with the community.
Distills repeated workflows into reusable skills, improves existing skills, and gates them through a three-tier publish funnel (local → project → community). Use when the agent or user notices a pattern worth crystallizing, when an existing skill is incomplete, or when something deserves community contribution. Default deny on dangerous tools and side effects.
Scans code for security vulnerabilities, detects dangerous patterns, and ensures security decisions are documented. Use when running security scans, auditing code, or checking for OWASP issues, injection risks, or sensitive data leaks. Automatically triggered on new modules, security-related changes, or post-refactor.
Processes Excel spreadsheet files (.xlsx, .xlsm, .csv). Creates workbooks, builds formulas, preserves formatting, analyzes tabular data, and validates financial models with zero-formula-error delivery. Use when working with spreadsheet files or tabular data analysis. Do NOT use for Word documents, PDFs, presentations, or database pipelines.
| name | analyzing-changes |
| description | Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring. |
| compatibility | node>=18 |
| user-invocable | false |
| allowed-tools | Bash, Read, Grep |
| argument-hint | ["--mode working|staged|committed"] |
看清「改了什么、影响哪里、文档是否跟上」——是变更的体检，不是审查替代品。
| 场景 | 跑 | 判据 |
|---|---|---|
| 提交前（任何代码改动） | ✅ | 默认门禁 |
| 重构完成 | ✅ | 评估辐射面 |
| 设计级改动 | ✅ | DESIGN.md 是否同步 |
| PR review | ✅ | 替代手工 diff 计数 |
| 跨模块大改 | ✅ | 看依赖图是否成环 |
| 紧急 hotfix | ⚠ | 跑，但允许文档同步延后到稳定后 |
| 模式 | 时机 | 用途 |
|---|---|---|
working (默认) | 写代码过程中 | 自检，看「我现在的工作面有哪些待整理」 |
staged | git add 后、commit 前 | 提交闸，看「这一 commit 的合理性」 |
committed | commit 完成后 | review，看「上一段历史改了哪些范围」 |
| 警告 | 触发 | 处置 |
|---|---|---|
| 代码 >50 行 而 DESIGN.md 未更新 | 设计层面变化未留痕 | 补 DESIGN.md「改了什么/为何」段 |
| 代码 >30 行 而无测试更新 | 测试覆盖滞后 | 补单测/集成测；或在 PR 注明「该路径已有 E2E 覆盖」 |
| 新增文件而 README.md 未更新 | 用户视角文档滞后 | 补模块入口说明 |
| 配置变更未记录 | 部署可能踩坑 | CHANGELOG / DESIGN 留迁移说明 |
| 删除文件 | 引用可能未清理 | 全仓 grep 文件名/导出符号 |
工具产出三类信号：
拆 PR 的判据（基于 commit 角度）：
- 跨 ≥3 模块且无统一主题 → 拆
- 单 commit >500 行非生成代码 → 拆
- 一次同时改架构 + 实现 + 文档 → 通常合理（同主题）
node scripts/change_analyzer.js # working（默认）
node scripts/change_analyzer.js --mode staged # 暂存区
node scripts/change_analyzer.js --mode committed # 已提交
node scripts/change_analyzer.js -v # 详细
node scripts/change_analyzer.js --json # CI 用
工具给信号，人下结论。先读受影响模块 README/DESIGN，确认：
设计级改动须于 DESIGN.md 留痕：改了什么、为何改、影响何处。三段缺一不可。