git-master

To create atomic commits in git, the skill analyzes your repository state and groups changes into single, logical units. This ensures your version control history remains clean, focused, and understandable for future tracing.

The best way to rebase and squash commits is by analyzing your current commit style and planning history rewriting operations. This cleans up your branch, ensuring a high-quality codebase before merging into the main project.

You can use git bisect to find a bug by utilizing the skill's advanced history search capabilities. It analyzes log data and executes bisect commands to pinpoint the exact commit that introduced the issue.

Yes, you can use git blame to search project history and find specific code changes. The skill offers advanced search capabilities to identify exactly who wrote particular lines and trace modifications.

To clean up a git branch before a large feature merge, break down your work into small, focused commits and rebase cleanly onto the main branch. This enforces atomic units and maintains a traceable history.

You should avoid rewriting git commit history on shared branches where others have based their work. History rewriting operations like squashing are best reserved for local feature branches before they are merged.