agentmods.dev

code-change-summarizer

code-change-summarizer is a skill for Claude Code, Codex from ArabelaTso/Skills-4-SE. It costs 110 tokens per session (3,326 once invoked), scanned A, original, Apache-2.0.

A tool that turns code changes into a structured pull request description. It can summarize what changed, why it changed, testing, design decisions, and breaking changes that may require users to update their code.

In plain words
What is it for?
Use it to write pull request descriptions from diffs, changed files, commits, and issue references, including sections for features, fixes, refactoring, tests, and dependencies.
Why use it?
It removes the need to reconstruct the purpose of a change from a large Git diff. It helps keep proposed changes understandable to reviewers and future maintainers.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 250repo +3 18d ago A scan SkillSpector: pass 110 tokens original Apache-2.0

Good fit Use it to write pull request descriptions from diffs, changed files, commits, and issue references, including sections for features, fixes, refactoring, tests, and dependencies.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arabelatso/skills-4-se/code-change-summarizer
View source ↗ ArabelaTso/Skills-4-SE arabelatso.github.io
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ArabelaTso/Skills-4-SE --skill code-change-summarizer
Clone the repo
git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for code-change-summarizer

README.md
[![agentmods](https://agentmods.dev/badge/skills/arabelatso/skills-4-se/code-change-summarizer.svg)](https://agentmods.dev/skills/arabelatso/skills-4-se/code-change-summarizer)
Your own site
<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/code-change-summarizer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/code-change-summarizer.svg" alt="Measured on agentmods" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,326 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00110 $0.03326
Opus 5 $0.00055 $0.01663
Sonnet 5 $0.00022 $0.00665
Haiku 4.5 $0.00011 $0.00333

Measured 8d ago against content hash 2ec9c6768590, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

code-change-summarizer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/code-change-summarizer/SKILL.md · 684 lines

How it starts

The opening of the file, as written. The whole thing — 684 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Change Summarizer

Generate clear, structured pull request descriptions from code changes.

Workflow

1. Analyze Code Changes

Gather code changes:

  • Git diff output
  • Modified files list
  • Commit messages
  • Related issue numbers

Understand the changes:

  • Read through all modified files
  • Identify what changed (added/modified/removed/fixed)
  • Understand the purpose of changes
  • Note any patterns or themes

Categorize changes:

  • Feature additions: New functionality
  • Bug fixes: Issue resolutions
  • Refactoring: Code improvements without behavior changes
  • Documentation: Doc updates
  • Tests: Test additions or modifications
  • Dependencies: Package updates
  • Configuration: Config or build changes

2. Create Initial Summary

Write a clear title:

Format: [Type] Brief description (max 72 characters)

Types:

  • feat: New feature
  • fix: Bug fix
  • refactor: Code refactoring
  • docs: Documentation
  • test: Tests
  • chore: Maintenance
  • perf: Performance
  • style: Code style
  • ci: CI/CD
  • build: Build system

Examples:

  • feat: Add user authentication with OAuth2
  • fix: Resolve memory leak in data processor
  • refactor: Simplify error handling logic

Write summary paragraph:

  • 2-3 sentences
  • Explain what and why
  • Use active voice
  • Be concise and clear

Example:

This PR adds OAuth2 authentication to the user login system. The change
improves security by using industry-standard authentication and enables
single sign-on with external providers.

3. Document Changes

List changes by category:

Added:

  • New features or functionality
  • New files or components
  • New API endpoints

Modified:

  • Changed behavior or implementation
  • Updated configuration
  • Refactored code

Removed:

  • Deprecated features
  • Deleted files
  • Removed dependencies

Fixed:

  • Bug fixes
  • Issue resolutions
  • Error corrections

Example:

## Changes

### Added
- OAuth2 authentication flow
- User session management
- Login/logout endpoints

### Modified
- User model to include OAuth tokens
- Authentication middleware
- Database schema

### Fixed
- Session timeout not working correctly
- Memory leak in token refresh

Read the full file on GitHub · 684 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 684 lines · 110 tokens per session scan A 2ec9c6768590

Subscribe to this mod's changes

code-change-summarizer is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (250 stars, last pushed 18d ago), licensed Apache-2.0. It adds 110 tokens to every session and 3,326 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude CodeGit and workflowWriting and docsclaudeclaude-skillsmetaprogrammingsoftware-developmentsoftware-engineering
Related

Other skills, from other repositories

release

CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.

oliver-kriska/claude-elixir-phoenix · 60 tokens

changelog-rules

Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.

tobihagemann/turbo · 29 tokens

accessing-github-repos

GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.

oaustegard/claude-skills · 39 tokens

generating-patches

Generates git patch files from codebase modifications for local application. Use when user mentions patch, diff, export changes, bring changes back, apply locally, or after editing uploaded codebases.

oaustegard/claude-skills · 43 tokens

git-pr-review

A read-only reviewer for GitHub pull requests, which are proposed code changes submitted for review. It produces an evidence-based report about whether a pull request should be merged.

huangwb8/skills · 76 tokens

git-workflow

A Git workflow guide for organizing commits, branches, pull requests, releases, and automated version-control tasks. Git is the system developers use to track code changes and collaborate.

huangwb8/skills · 47 tokens