Creates atomic git commits and analyzes repository history for changes and bugs.
npx skills add https://github.com/ssccio/cc-on-web-base --skill git-master-ssccio
Please help me install this Agent Skill. Skill: git-master Source: https://github.com/ssccio/cc-on-web-base/tree/main/skills/git-master Command: npx skills add https://github.com/ssccio/cc-on-web-base --skill git-master-ssccio
Git changes often get bundled into messy commits and risky rebases, making reviews harder and history harder to understand when something breaks.
Tell the AI to convert your current work into atomic commits, then identify the first commit that introduced a specific bug you provide.
High-intent search queries and answers about installing and using this skill.
To split messy git changes into atomic commits, this Skill analyzes how many files and concerns are touched and forces meaningful commit boundaries based on thresholds. This reduces review risk and rollback complexity by separating changes by concern.
To find when a behavior was introduced in git history, this Skill provides targeted git log, grep, blame, and bisect workflows. These forensic debugging commands trace exactly when specific code symbols or behaviors were introduced across the repository.
Style-aware commit message generation works by detecting conventions from the last 30 commits, including language, semantic prefixes, and cadence. This ensures new commit messages match existing repository styles rather than requiring manual convention checks.
The safest way to rebase git branches involves enforcing rebase guardrails that never rebase main or master and using force-with-lease for safer forcing behavior. This Skill also automatically stashes changes before rebasing to prevent data loss.
Yes, you can use git bisect to debug history and find the first commit that introduced a bug. This Skill supports targeted bisect commands alongside git log and blame workflows to reliably trace when specific code changes or bugs were introduced.
Automated commit splitting for large changes is limited by enforced commit-splitting thresholds based on how many files and concerns are touched. While this reduces review risk, changes spanning too many concerns may require manual intervention to define meaningful boundaries.
ss49919201Stage git changes and generate commit messages from diffs.
santychuycomAnalyze diffs, create atomic conventional commits, push, and open pull requests.
OutlineDrivenSplit staged and unstaged changes into logical atomic commits with pre-commit checks.
chasebuildStage changes with git add -p and generate atomic commit messages.
