New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Code Change Analysis Gate

by telagod in telagod/code-abyss

Checks what a code change touched, how far its impact reaches and whether design docs, tests and README files kept up, before commit or in review.

MITAuto-check: notesDevelopment

SKILL.md written in Chinese; this summary is our English description.

Install Code Change Analysis Gate

skills CLI
$ npx skills add telagod/code-abyss --skill analyzing-changes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install telagod/code-abyss analyzing-changes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/telagod/code-abyss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analyzing-changes .claude/skills/analyzing-changes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
analyzing-changes
GitHub stars
244
Token cost
~532 tokens
SKILL.md length
136 words
Files
3 (incl. scripts)
Skills in repo
38
Repo updated
First seen
Licence
MIT

At a glance

Checks what a code change touched, how far its impact reaches and whether design docs, tests and README files kept up, before commit or in review.

  • Works in 3 steps: 文件分类 — 自动分代码/文档/测试/配置；用于判断「是否纯文档变更」 → 模块识别 — 把变更聚到模块边界；用于判断「跨模块改动」 → 影响评估 — 行数 + 文件数；用于判断「改动是否需要拆 PR」
  • Running a check on staged changes just before committing
  • SKILL.md covers 何时使用, 三种模式, 警告判定 and 解读输出, plus 3 more sections
  • Runs JavaScript scripts from its folder; calls node and git

What it does

The skill runs scripts/change_analyzer.js on the working tree, the staged files or the latest commits, and reports three kinds of signal: files sorted into code, docs, tests and config, changes grouped by module, and an impact estimate from line and file counts. It is described as a health check for a change, not a replacement for review, and its instructions are written in Chinese.

Warnings fire when more than 50 lines of code change without a DESIGN.md update, when more than 30 lines change without test updates, when new files appear without a README update, when config changes go unrecorded, or when files are deleted and references may remain. It also gives rules of thumb for splitting a pull request, points to sibling skills for module checks, security and code quality, and asks a person to review the affected module docs and record what changed, why and where it has impact.

When your agent uses it

  • Running a check on staged changes just before committing
  • Judging how widely a refactor spreads across modules
  • Verifying that DESIGN.md, README and tests were updated along with the code
  • Deciding whether a large change should be split into several pull requests

Example prompts

  • “Analyze my staged changes before I commit and list any documentation drift.”
  • “I just finished the refactor. How far does the impact reach across modules?”
  • “Check the last commit for missing tests and an outdated DESIGN.md.”

Requirements

  • Node.js 18 or newer
  • A git repository
  • Compatibility (from SKILL.md): node>=18
  • Pre-approved tools (allowed-tools): Bash, Read, Grep

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. 文件分类 — 自动分代码/文档/测试/配置；用于判断「是否纯文档变更」
  2. 模块识别 — 把变更聚到模块边界；用于判断「跨模块改动」
  3. 影响评估 — 行数 + 文件数；用于判断「改动是否需要拆 PR」

What it can do on your machine

Read from SKILL.md and the folder at commit 2544577. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    node>=18

    From compatibility in the SKILL.md frontmatter.

Context cost

Code Change Analysis Gate loads about 532 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 136 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~532

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from telagod/code-abyss at commit 2544577, republished under its MIT licence (© telagod). 136 words, ~532 tokens.

Download SKILL.mdSave it as .claude/skills/analyzing-changes/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
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.
allowed-tools
Bash, Read, Grep
compatibility
node>=18
user-invocable
false
argument-hint
--mode working|staged|committed

变更校验关卡

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

何时使用

场景跑判据
提交前（任何代码改动）✅默认门禁
重构完成✅评估辐射面
设计级改动✅DESIGN.md 是否同步
PR review✅替代手工 diff 计数
跨模块大改✅看依赖图是否成环
紧急 hotfix⚠跑，但允许文档同步延后到稳定后

三种模式

模式时机用途
working (默认)写代码过程中自检，看「我现在的工作面有哪些待整理」
stagedgit add 后、commit 前提交闸，看「这一 commit 的合理性」
committedcommit 完成后review，看「上一段历史改了哪些范围」

警告判定

警告触发处置
代码 >50 行 而 DESIGN.md 未更新设计层面变化未留痕补 DESIGN.md「改了什么/为何」段
代码 >30 行 而无测试更新测试覆盖滞后补单测/集成测；或在 PR 注明「该路径已有 E2E 覆盖」
新增文件而 README.md 未更新用户视角文档滞后补模块入口说明
配置变更未记录部署可能踩坑CHANGELOG / DESIGN 留迁移说明
删除文件引用可能未清理全仓 grep 文件名/导出符号

解读输出

工具产出三类信号：

  1. 文件分类 — 自动分代码/文档/测试/配置；用于判断「是否纯文档变更」
  2. 模块识别 — 把变更聚到模块边界；用于判断「跨模块改动」
  3. 影响评估 — 行数 + 文件数；用于判断「改动是否需要拆 PR」

拆 PR 的判据（基于 commit 角度）：

  • 跨 ≥3 模块且无统一主题 → 拆
  • 单 commit >500 行非生成代码 → 拆
  • 一次同时改架构 + 实现 + 文档 → 通常合理（同主题）

与其他 skill 联动

使用

bash
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 留痕：改了什么、为何改、影响何处。三段缺一不可。

© telagod, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in skills/analyzing-changes of telagod/code-abyss.

  • SKILL.md
  • agents/openai.yaml
  • scripts/change_analyzer.js

Open the folder on GitHubat commit 2544577

Compare with similar skills

Code Change Analysis Gate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Change Analysis Gate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Change Analysis Gate this skilltelagod/code-abyss244—~532Automated safety check: NotesMIT
Qt C++ Code Reviewx-tools-author/x-tools1.1k2 repos~4.3kAutomated safety check: PassBSD-3-Clause
Adversarial Reviewer302ai/302-AI-Studio1321 repos~3kAutomated safety check: PassMIT
Feature-Level Code Reviewdataelement/bisheng12k—~1kAutomated safety check: PassApache-2.0
Two-Axis Code Reviewrengwu/wayfinder-maps134—~1.8kAutomated safety check: PassMIT
Code Revieweralirezarezvani/claude-code-tresor777—~1.8kAutomated safety check: PassMIT

Similar skills

  • Qt C++ Code Review

    x-tools-author/x-tools

    Read-only review of Qt6 C++ code that combines a deterministic lint script with six parallel analysis agents and reports only high-confidence issues.

    1.1k GitHub starsUsed in 2 repos~4.3k tokens
    DevelopmentAuto-check passed

  • Adversarial Reviewer

    302ai/302-AI-Studio

    Adversarial code review that breaks the self-review monoculture.

    132 GitHub starsUsed in 1 repo~3k tokens
    DevelopmentAuto-check passed

  • Feature-Level Code Review

    dataelement/bisheng

    Runs a seven-dimension code review on a finished feature, comparing the diff against a base branch and the feature's spec, design and task files.

    12k GitHub stars~1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Two-Axis Code Review

    rengwu/wayfinder-maps

    Reviews the changes since a commit, branch or tag along two separate axes: the repo's documented coding standards and fidelity to the originating spec or PRD.

    134 GitHub stars~1.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Code Reviewer

    alirezarezvani/claude-code-tresor

    Automatic code quality and best practices analysis. An agent skill from alirezarezvani/claude-code-tresor.

    777 GitHub stars~1.8k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Code Reviewer

    MageByte-Zero/spec-superflow

    Review completed implementation batches for spec compliance and code quality.

    839 GitHub starsUsed in 1 repo~1.5k tokens
    DevelopmentAuto-check passed

More from telagod/code-abyss

All 38 skills in this repo

  • Security Gate Scanner

    telagod/code-abyss

    Scans code with a bundled Node scanner for injection, secret leaks and other dangerous patterns, and requires documented decisions for accepted risks.

    244 GitHub stars~552 tokensUpdated 2 mo ago
    Auto-check: notes

  • Persona Voice Card Builder

    telagod/code-abyss

    Distills a recurring agent voice from conversations into a restricted Persona Voice Card, validates it for schema, safety and distinctness, and prepares it for community submission.

    244 GitHub stars~716 tokensUpdated 2 mo ago
    Auto-check: notes

  • Skill Cultivation Funnel

    telagod/code-abyss

    Distills repeated workflows into new skills, improves existing ones and promotes them through local, project and community tiers after a default-deny safety scan.

    244 GitHub stars~794 tokensUpdated 2 mo ago
    Auto-check: notes

  • DOCX Processing Toolkit

    telagod/code-abyss

    Routes Word document tasks to the right tool: pandoc for text, raw OOXML for structure and comments, docx-js for new files, and a mandatory redlining flow for edits to others' documents.

    244 GitHub stars~668 tokensUpdated 2 mo ago
    Auto-check: notes

  • PDF Processing Toolkit

    telagod/code-abyss

    Picks the right Python library or CLI tool for a PDF task, text and table extraction, merging, splitting, OCR, watermarking or form filling, and points to a matching recipe.

    244 GitHub stars~532 tokensUpdated 2 mo ago
    Auto-check: notes

  • Code Quality Gate Checker

    telagod/code-abyss

    Checks cyclomatic complexity, function and file length, parameter count, nesting depth and naming conventions against fixed thresholds, with a bundled Node.js script and hotspot integration.

    244 GitHub stars~609 tokensUpdated 2 mo ago
    Auto-check: notes

Works with

Categories

Questions about Code Change Analysis Gate

What does Code Change Analysis Gate do?

Checks what a code change touched, how far its impact reaches and whether design docs, tests and README files kept up, before commit or in review. js on the working tree, the staged files or the latest commits, and reports three kinds of signal: files sorted into code, docs, tests and config, changes grouped by module, and an impact estimate from line and file counts. It is described as a health check for a change, not a replacement for review, and its instructions are written in Chinese.

When should I use Code Change Analysis Gate?

Code Change Analysis Gate fits situations like: running a check on staged changes just before committing; judging how widely a refactor spreads across modules; verifying that DESIGN.md, README and tests were updated along with the code; deciding whether a large change should be split into several pull requests.

How do I install Code Change Analysis Gate in Claude Code?

Run `npx skills add telagod/code-abyss --skill analyzing-changes -a claude-code`. Or copy the skill folder (skills/analyzing-changes in telagod/code-abyss) into .claude/skills/analyzing-changes in your project. Claude Code loads it when a task matches its description.

How do I install Code Change Analysis Gate in Codex?

Run `npx skills add telagod/code-abyss --skill analyzing-changes -a codex`. Or copy the skill folder (skills/analyzing-changes in telagod/code-abyss) into .agents/skills/analyzing-changes in your project. Codex loads it when a task matches its description.

Can I use Code Change Analysis Gate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add telagod/code-abyss --skill analyzing-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyzing-changes, .gemini/skills/analyzing-changes, .github/skills/analyzing-changes and .opencode/skills/analyzing-changes in your project.

What does Code Change Analysis Gate need to run?

Going by SKILL.md and its folder, Code Change Analysis Gate needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and git). Our summary lists: Node.js 18 or newer; A git repository. Its frontmatter pre-approves these tools: Bash, Read, Grep. Compatibility (from SKILL.md): node>=18.

Does Code Change Analysis Gate access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Code Change Analysis Gate safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Code Change Analysis Gate use?

Code Change Analysis Gate is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Change Analysis Gate use?

About 532 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Change Analysis Gate?

Skills that share tags, products or a category with Code Change Analysis Gate: Qt C++ Code Review (x-tools-author/x-tools, 1.1k stars), Adversarial Reviewer (302ai/302-AI-Studio, 132 stars), Feature-Level Code Review (dataelement/bisheng, 12k stars) and Two-Axis Code Review (rengwu/wayfinder-maps, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Change Analysis Gate?

telagod (a GitHub user) maintains it in telagod/code-abyss, which has 244 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on July 19, 2026.

Source: telagod/code-abyss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.