Git control
Standardizes git operations, branch management, and disaster recovery. Use when committing, branching, or resolving conflicts. For commit formatting, see conventional-commits.From its SKILL.md
npx -y skills add tuliosousapro/SaaS-blueprint --skill git-controlAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 8 commands, including `git add <file>` and 7 more.
SKILL.md
2.2 KB, 510 tokens by cl100k_base, as published. Nobody here has run it
Git Control Skill
When to Use
- Whenever performing version control operations.
- When creating new features, fixing bugs, or managing releases.
- For resolving merge conflicts or recovering from mistakes.
1. Core Workflow
Branching Strategy
- Main Branch: Production-ready code only.
- Feature Branches:
feat/[feature-name]for new functionality. - Bug Fix Branches:
fix/[bug-name]for corrections. - Hotfix Branches:
hotfix/[issue]for urgent production fixes.
Staging & Committing
- Always follow the Conventional Commits skill.
- Stage only relevant changes:
git add <file>(avoidgit add .unless necessary). - Review changes before committing:
git diff --staged.
2. Common Operations
Starting Work
git checkout main
git pull origin main
git checkout -b feat/my-new-feature
Synchronizing
git fetch --all
git pull origin [branch-name]
git push origin [branch-name]
Merging & Rebasing
-
Merge: Use for combining long-lived branches.
-
Rebase: Use to keep feature branches up-to-date with main and maintain a clean history.
git checkout feat/my-feature git rebase main
3. Advanced Git Mastery
Conflict Resolution
- Identify files:
git status. - Edit files to resolve
<<<<,====,>>>>markers. - Stage resolved files:
git add <file>. - Continue:
git commitorgit rebase --continue.
Disaster Recovery
- Undo last commit (keep changes):
git reset --soft HEAD~1. - Undo last commit (discard changes):
git reset --hard HEAD~1. - Find lost commits:
git reflog. - Revert a specific commit:
git revert <commit-hash>.
Stashing
- Save work temporarily:
git stash push -m "work in progress". - Retrieve work:
git stash pop.
4. Quality Gates
- No merge commits on feature branches (prefer rebase).
- Each commit must pass linting and tests.
- Pull requests must be clear and focus on a single objective.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most pr commit review skills give in 510 tokens
Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06
- Use conventional commit message formatin 150 of 1055, across 145 files
- Announce skill usage at startin 78 of 1055
- Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
- Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
- Use imperative mood for commit subjectin 52 of 1055
- Run tests to verify clean baselinein 42 of 1055, across 32 files
- Push branch to originin 40 of 1055, across 38 files
- Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
- Delete branches after mergingin 38 of 1055, across 30 files
- Create worktree with new branchin 37 of 1055, across 32 files
- Wrap body text at 72 charactersin 36 of 1055, across 34 files
- Auto-detect and run project setupin 35 of 1055, across 27 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.