commit-analysis
Analyze git changes to understand nature, scope, and commit type for intelligent message generation
Best use case
commit-analysis is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyze git changes to understand nature, scope, and commit type for intelligent message generation
Teams using commit-analysis should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/commit-analysis/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How commit-analysis Compares
| Feature / Agent | commit-analysis | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyze git changes to understand nature, scope, and commit type for intelligent message generation
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Commit Analysis Skill - Change Analysis and Type Detection Intelligent analysis of git changes to determine commit type, scope, and atomicity for semantic commit message generation. ## Operations - **analyze** - Full analysis (type, scope, atomicity) - **detect-type** - Determine commit type (feat, fix, docs, etc.) - **identify-scope** - Identify affected module/component - **assess-atomicity** - Check if changes should be split - **file-stats** - Get file change statistics ## Router Logic Parse $ARGUMENTS to determine which operation to perform: 1. Extract operation from first word of $ARGUMENTS 2. Extract remaining arguments as operation parameters 3. Route to appropriate instruction file: - "analyze" → Read `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/commit-analysis/analyze-changes.md` - "detect-type" → Read `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/commit-analysis/detect-type.md` - "identify-scope" → Read `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/commit-analysis/identify-scope.md` - "assess-atomicity" → Read `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/commit-analysis/assess-atomicity.md` - "file-stats" → Read `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/commit-analysis/file-stats.md` 4. Execute instructions with parameters 5. Return structured analysis results ## Error Handling - If operation is unknown, list available operations - If parameters are missing, show required format - If not a git repository, return clear error message - If no changes to analyze, inform user ## Usage Examples ```bash # Full analysis of current changes /commit-analysis analyze # Detect commit type only /commit-analysis detect-type # Identify affected scope /commit-analysis identify-scope # Check if changes should be split /commit-analysis assess-atomicity # Get file statistics /commit-analysis file-stats ``` --- **Base directory:** `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/commit-analysis` **Current request:** $ARGUMENTS Parse operation and route to appropriate instruction file.
Related Skills
quality-analysis
Deep quality analysis with scoring, recommendations, and actionable reports
history-analysis
Analyze git history to learn project's commit style and conventions
commit-error-handling
Handle git errors and edge cases gracefully
commit-best-practices
Enforce git commit best practices and workflow guidance
atomic-commit
Guide splitting large commits into atomic, focused commits
specification-writing
Core reference for EARS requirement patterns, Given/When/Then acceptance criteria, RFC 2119 language, requirement ID conventions, and specification quality checklists. Background knowledge for the spec-writer agent. Preloaded by spec-writer via the skills frontmatter field; not user-invocable.
refine
Unified specification refinement plugin. Single entry point for all spec operations: greenfield architecture pipelines (principles → design → stack → spec → plan), feature spec creation in existing systems, iterative convergence loops, quality reviews, drift detection, finalization, ticket decomposition, traceable updates, and lifecycle archival. Detects pipeline state from existing artifact frontmatter and routes intelligently. Use whenever you need to create, refine, validate, or evolve a technical specification.
validation-orchestrator
Intelligent validation orchestrator with auto-detection and progressive validation workflows
security-scan
Comprehensive security scanning for secrets, vulnerabilities, and unsafe practices
schema-validation
Validate JSON schemas, required fields, and format compliance for marketplaces and plugins
documentation-validation
Validate documentation completeness, format, and quality for plugins and marketplaces
best-practices
Enforce OpenPlugins and Claude Code best practices for naming, versioning, and standards compliance