software-change-management-using-git
Use this skill when any task is complete, before beginning any non-trivial task, or whenever working with git or tasked with commiting code.
When & Why to Use This Skill
This Claude skill automates the end-to-end software change management process using Git. It intelligently analyzes code changes, manages untracked files, generates idiomatic commit messages based on high-level logic, and handles complex upstream synchronization including conflict resolution and rebasing.
Use Cases
- Automated Commit Generation: Streamlining the development workflow by automatically crafting descriptive, high-quality commit messages after completing coding tasks.
- Git Workflow Standardization: Ensuring consistent change management practices across a team by automating the diff analysis and push process.
- Conflict and Edge Case Resolution: Automatically handling failed pushes by pulling, rebasing, and resolving synchronization issues without manual intervention.
- Repository Maintenance: Managing untracked files and .gitignore updates dynamically as the project evolves.
| name | software-change-management-using-git |
|---|---|
| description | Use this skill when any task is complete, before beginning any non-trivial task, or whenever working with git or tasked with commiting code. |
Software Change Management Using Git
Workflow Automation for Git Commit Management
Examine all changes since the last commit:
- It should do a deepthink to truely understand the changes from a high-level. Think about the consequences and what the main purpose for this change is in terms of the direction we're going. Also, do a diff between the trunk for a further zoomed out view in terms of the full branch and how this commit contributes to the full story. Hand off findings via stream chaining to step 2.
- Look at any untracked files and determine if they should be added to the commit or inserted into the .gitignore. Perform the correct action.
Craft an idiomatic git commit message:
- Take the data handed to you from step 1 and create a single-line description, followed by a blank line and then an itemized high-level changelist
- Commit and push to HEAD
Resolve any edge cases:
- If push fails, resolve by pulling from head, resolving any conflicts, rebasing, or whatever needs to be done to rectify the situation