Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

git-master

Estrellas3

Forks0

Actualizado9 de marzo de 2026 a las 02:34

Git operations mastery. Atomic commits, rebase/squash, history search (blame, bisect, log -S). Triggers on 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

opzero1

opzero1/op1

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	git-master
description	Git operations mastery. Atomic commits, rebase/squash, history search (blame, bisect, log -S). Triggers on 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.

Git Master Skill

When to Load This Skill

Creating commits (atomic, well-messaged)
Rebasing or squashing commits
History search (blame, bisect, log -S)
Finding "who wrote" or "when was X added"
Any complex git operations

Atomic Commits

Each commit should be:

Single purpose - one logical change
Self-contained - builds and tests pass
Well-messaged - explains WHY, not just WHAT

Commit Message Format

<type>(<scope>): <subject>

<body - optional, explains WHY>

<footer - optional, references issues>

Types: feat, fix, docs, style, refactor, test, chore

Examples

# ✅ GOOD
git commit -m "feat(auth): add JWT refresh token support

Enables seamless token refresh without user re-authentication.
Tokens refresh 5 minutes before expiration.

Closes #123"

# ❌ BAD
git commit -m "fixed stuff"
git commit -m "WIP"
git commit -m "update"

History Search

Find Who Wrote a Line

git blame <file>
git blame -L 10,20 <file>  # lines 10-20 only
git blame -w <file>        # ignore whitespace

Find When Code Was Added

# Search commit messages
git log --grep="keyword"

# Search code changes (pickaxe)
git log -S "function_name"
git log -S "exact string" --all

# Search with regex
git log -G "pattern.*regex"

Find Bug Introduction (Bisect)

git bisect start
git bisect bad HEAD
git bisect good <known-good-commit>
# Git will checkout commits, you test each:
git bisect good  # or
git bisect bad
# When done:
git bisect reset

Interactive Rebase

Squash Recent Commits

git rebase -i HEAD~3  # last 3 commits

In editor, change pick to:

squash (s) - combine with previous, keep message
fixup (f) - combine with previous, discard message
reword (r) - change commit message
edit (e) - stop to amend
drop (d) - delete commit

Rebase onto Base Branch

git fetch origin
git rebase origin/<base-branch>
# Resolve conflicts if any:
git add <file>
git rebase --continue

Replace <base-branch> with the repository's actual target branch.

Safety Rules (CRITICAL)

Action	Safety
`git commit`	Safe
`git commit --amend`	Safe if NOT pushed
`git rebase`	Safe if NOT pushed
`git push --force`	⚠️ DESTRUCTIVE - ask first
`git reset --hard`	⚠️ DESTRUCTIVE - ask first

NEVER force push to main/master without explicit user approval.

Common Workflows

Amend Last Commit (Not Pushed)

git add <files>
git commit --amend --no-edit
# OR to also change message:
git commit --amend -m "new message"

Undo Last Commit (Keep Changes)

git reset --soft HEAD~1

Stash Work in Progress

git stash
git stash pop
git stash list
git stash drop stash@{0}

Create Feature Branch

git checkout -b feature/my-feature
# work, commit...
git push -u origin feature/my-feature

Pull Request Workflow

# Ensure up to date
git fetch origin
git rebase origin/<base-branch>

# Push branch
git push -u origin feature/my-feature

# Create PR
gh pr create --title "feat: description" --body "## Summary
- Change 1
- Change 2"

Again, replace <base-branch> with the repository's real PR target branch.

Más de este repositorio

mismo repositorio

grill-me

opzero1/op1

Interview the user relentlessly about a plan or design until branch-level decisions are resolved for execution.

2026-04-213

figma-design

opzero1/op1

Access Figma designs, extract design systems, and retrieve component specifications. Use when implementing UI from Figma mockups, extracting design tokens, or analyzing design files.

2026-04-213

mcp-economy

opzero1/op1

Enforce cost-aware MCP usage. Use when a task might trigger heavy external tools, web search, or broad context expansion. Prevents token burn by ensuring MCPs are only used when local context is insufficient.

2026-04-213

mcp0-navigation

opzero1/op1

Navigate the Warmplane mcp0 facade efficiently. Use when the active config exposes provider capabilities through `mcp0_*` tools and you need to discover or call provider tools without brute-force describing large capability sets. Trigger on requests involving mcp0, Warmplane, or provider work through the facade such as Linear, Notion, Figma, New Relic, Context7, grep.app, or Storybook tools.

2026-04-213

chrome-devtools

opzero1/op1

Use this when the user needs to control Chrome, navigate to a page, inspect a tab, click or fill elements, take screenshots, or automate a browser flow with aeroxy/chrome-devtools-cli.

2026-04-203

plan-protocol

opzero1/op1

Guidelines for creating and managing implementation plans with citations

2026-04-163

name	git-master
description	Git operations mastery. Atomic commits, rebase/squash, history search (blame, bisect, log -S). Triggers on 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.

Git Master Skill

When to Load This Skill

Creating commits (atomic, well-messaged)
Rebasing or squashing commits
History search (blame, bisect, log -S)
Finding "who wrote" or "when was X added"
Any complex git operations

Atomic Commits

Each commit should be:

Single purpose - one logical change
Self-contained - builds and tests pass
Well-messaged - explains WHY, not just WHAT

Commit Message Format

<type>(<scope>): <subject>

<body - optional, explains WHY>

<footer - optional, references issues>

Types: feat, fix, docs, style, refactor, test, chore

Examples

# ✅ GOOD
git commit -m "feat(auth): add JWT refresh token support

Enables seamless token refresh without user re-authentication.
Tokens refresh 5 minutes before expiration.

Closes #123"

# ❌ BAD
git commit -m "fixed stuff"
git commit -m "WIP"
git commit -m "update"

History Search

Find Who Wrote a Line

git blame <file>
git blame -L 10,20 <file>  # lines 10-20 only
git blame -w <file>        # ignore whitespace

Find When Code Was Added

# Search commit messages
git log --grep="keyword"

# Search code changes (pickaxe)
git log -S "function_name"
git log -S "exact string" --all

# Search with regex
git log -G "pattern.*regex"

Find Bug Introduction (Bisect)

git bisect start
git bisect bad HEAD
git bisect good <known-good-commit>
# Git will checkout commits, you test each:
git bisect good  # or
git bisect bad
# When done:
git bisect reset

Interactive Rebase

Squash Recent Commits

git rebase -i HEAD~3  # last 3 commits

In editor, change pick to:

squash (s) - combine with previous, keep message
fixup (f) - combine with previous, discard message
reword (r) - change commit message
edit (e) - stop to amend
drop (d) - delete commit

Rebase onto Base Branch

git fetch origin
git rebase origin/<base-branch>
# Resolve conflicts if any:
git add <file>
git rebase --continue

Replace <base-branch> with the repository's actual target branch.

Safety Rules (CRITICAL)

Action	Safety
`git commit`	Safe
`git commit --amend`	Safe if NOT pushed
`git rebase`	Safe if NOT pushed
`git push --force`	⚠️ DESTRUCTIVE - ask first
`git reset --hard`	⚠️ DESTRUCTIVE - ask first

NEVER force push to main/master without explicit user approval.

Common Workflows

Amend Last Commit (Not Pushed)

git add <files>
git commit --amend --no-edit
# OR to also change message:
git commit --amend -m "new message"

Undo Last Commit (Keep Changes)

git reset --soft HEAD~1

Stash Work in Progress

git stash
git stash pop
git stash list
git stash drop stash@{0}

Create Feature Branch

git checkout -b feature/my-feature
# work, commit...
git push -u origin feature/my-feature

Pull Request Workflow

# Ensure up to date
git fetch origin
git rebase origin/<base-branch>

# Push branch
git push -u origin feature/my-feature

# Create PR
gh pr create --title "feat: description" --body "## Summary
- Change 1
- Change 2"

Again, replace <base-branch> with the repository's real PR target branch.