Analyzing Changes

Analyzing Changes is a Quality skill for Claude Code, published by telagod in code-abyss.

239 stars32 forkson telagod/code-abyssAdded 2026/09/03Repository updated 2026/07/19

agent-skillsai-agentai-assistantai-personalityblue-teamcharacter-cardclaude-codeclicodexcodex-cliconfigurationdeveloper-toolsdevopsgemini-clipersonaprompt-engineeringred-teamsecurityskills

Install in seconds

Install Analyzing Changes

Copy Analyzing Changes into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/telagod/code-abyss/tree/main/skills/analyzing-changes ~/.claude/skills/analyzing-changes

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/telagod/code-abyss.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/analyzing-changes/SKILL.md in telagod/code-abyss
Installs to: ~/.claude/skills/analyzing-changes
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1478 skills

What Analyzing Changes does

Analyzing Changes analyzes code diffs to estimate impact scope, flag documentation drift, and check whether tests or design docs need updates. Use it before commits, after refactors, or when reviewing cross-module changes.

Analyzing Changes is cataloged under Quality on DirSkills. Analyzing Changes comes from a repository tagged agent-skills, ai-agent, ai-assistant, ai-personality and blue-team.

Documentation

README

Excerpt

变更校验关卡

看清「改了什么、影响哪里、文档是否跟上」——是变更的体检，不是审查替代品。

何时使用

场景	跑	判据
提交前（任何代码改动）	✅	默认门禁
重构完成	✅	评估辐射面
设计级改动	✅	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 文件名/导出符号

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Analyzing Changes

What else does telagod publish alongside Analyzing Changes?
Analyzing Changes is one of 25 skills that DirSkills catalogs from telagod/code-abyss, the repository it ships in. Its siblings there include Adversarial Review Orchestration, Analyzing Spreadsheets and Application Security Defense. Each one is a separate skill with its own page in this directory, installs the same way Analyzing Changes does, and is maintained by telagod in that same repository. The rest of the collection is listed on the telagod/code-abyss page.
How does Analyzing Changes compare to other Quality skills?
Analyzing Changes ranks #1343 by stars among the 1478 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Analyzing Changes against them. Open each page to compare what they document and how they install.