Guide Git workflows for atomic commits, rebasing, blame, and bisect.
npx skills add https://github.com/trystan2k/favoritable-old --skill git-trystan2k
Please help me install this Agent Skill. Skill: git Source: https://github.com/trystan2k/favoritable-old/tree/main/.agents/skills/git Command: npx skills add https://github.com/trystan2k/favoritable-old --skill git-trystan2k
Git workflows are fraught with risk: messy commit histories make code reviews painful, risky rebases can lose work, and tracking down when a bug was introduced can take hours of manual searching. This Skill eliminates those pain points with guided, safe workflows for every common Git operation.
Use the git skill to clean up your current feature branch's commit history into atomic, review-ready commits before pushing to remote.
High-intent search queries and answers about installing and using this skill.
You can clean up messy commit history by grouping changes into logical, atomic commits with fixup support and using interactive rebasing to squash branches. This step-by-step workflow detects your project's commit message style to ensure review-ready branches.
The best way to find which commit introduced a bug is using Git bisect. This workflow walks you step by step through binary searching your commit history, quickly tracking down the exact commit that broke a specific feature or flow.
Git bisect traces bug origins by binary searching through your commit history. It guides you through marking good and bad commits, automatically checking out intermediate versions until the exact commit that introduced the bug is identified.
You can safely rewrite branch history with an interactive rebase using built-in safety guardrails. The workflow includes safety checks for force pushes and main branch protection to prevent overwriting shared history during squashes and branch cleanup.
To find who wrote a line of code or when a change was added, use Git blame and log search tools. These fast change attribution workflows quickly identify the author and timestamp of specific lines within your repository.
Avoid force pushing during a Git rebase when working on shared branches, as it can overwrite collaborative history. The workflow enforces safety guardrails to prevent force pushes and protect main branches from risky rebase operations.
Tx1207Create a new project from a template, initialize uv, and configure a local Git repository.
dtbuchholzStage Git changes, create conventional commits, push branches, and open pull requests via GitHub CLI.
wesleyegbertoAutomate advanced Git workflows for rebasing, cherry-picking, and history cleanup.
ARCASSystemsAutomates git commits for non-technical users via a simplified interface.
