erk-diff-analysis

dagster-io's avatarfrom dagster-io

Internal skill for commit message generation. Only load when explicitly requested by name or invoked by commands.

⭐32stars🔀2forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

The erk-diff-analysis skill is a specialized Claude agent tool designed for automated commit message generation and intelligent diff analysis. It streamlines the software development workflow by transforming complex code changes into concise, strategic, and component-level summaries, ensuring high-quality version control documentation and improved team collaboration.

Use Cases

  • Automated Pull Request Documentation: Generate professional and accurate summaries for PRs by analyzing code diffs, highlighting significant logic changes and architectural impacts.
  • Standardizing Git Commit History: Maintain a clean and consistent repository history by enforcing structured commit messages that focus on module-level changes rather than granular function updates.
  • Breaking Change Identification: Automatically detect and prominently flag breaking changes within a diff to alert maintainers and ensure safer release management.
  • Technical Debt Tracking: Use the concise diff analysis to quickly review changes in test coverage patterns and repository structure during the development cycle.
nameerk-diff-analysis
descriptionInternal skill for commit message generation. Only load when explicitly requested by name or invoked by commands.

Diff Analysis

This skill provides the commit message generation prompt used by PR submission commands.

When to Use

Only load this skill when:

  • Explicitly requested by name (erk-diff-analysis)
  • Invoked by commands like /erk:git-pr-push

Usage

Load references/commit-message-prompt.md when analyzing a diff, then apply its principles to generate output.

Key Principles

  • Be concise and strategic - focus on significant changes
  • Use component-level descriptions - reference modules/components, not individual functions
  • Highlight breaking changes prominently
  • Note test coverage patterns
  • Use relative paths from repository root