analyzing-changes
From the author
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.
Install
npx skills add telagod/code-abyss --skill analyzing-changes -a claude-code
Installs to .claude/skills/analyzing-changes/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 74
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- change-impact-analysisnaodeng/awesome-qa-skillsUse this skill when you need to analyze how a code, configuration, or requirement change affects quality scope; triggers include 变更影响分析 and change impact analysis.Planning★ 279
- understand-diffEgonex-AI/Understand-AnythingUse when you need to analyze git diffs or pull requests to understand what changed, affected components, and risksEngineering★ 88.2K
- diff-analysisathola/claude-night-marketAnalyzes changesets with risk scoring, categorization by type and impact, and release note preparation. Use when extracting insights from raw change data.Productivity★ 343
- Reviewing CodeMicrock/ordinary-claude-skillsSystematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.Engineering★ 408
- architect-analyzetikalk/adlc-team-skillsUse when validating generated or refined architecture artifacts, before feature development, during architecture review, or periodically to detect ADR↔AD drift, completeness gaps, and quality issues.Planning★ 143
- change-impactqshanx/docs-governance在改代码、数据、接口或治理文档前做有证据的影响分析，并在实施后把计划影响与实际 diff 对照；覆盖代码调用、数据/Schema、API 契约、测试、文档、ADR、部署、迁移和回滚。用于跨模块修改、高风险变更、数据库迁移、认证、公共接口、用户问“会影响哪里”“改之前检查一下”或实施后需要反思偏差时。English triggers: change impact analysis, blast radius, pre-change analysis, migration impact, rollback plan, post-implementation alignment.Planning★ 253
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in