Skill

git-workflow

Git workflow conventions - branching, commits, PRs, rebasing. Auto-loaded when working with git operations, merge conflicts, or PR-related files.

npx claudepluginhub littlelingo/context-engine --plugin context-engine

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- `feat/[name]` for features, `fix/[name]` for bugs, `refactor/[scope]` for restructuring

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Stars1

Forks0

Last CommitMar 29, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Git Workflow

Branching

feat/[name] for features, fix/[name] for bugs, refactor/[scope] for restructuring

Never commit directly to main/master

Keep branches short-lived - merge or rebase within days, not weeks

Commits

Conventional commits: feat:, fix:, refactor:, docs:, test:, chore:

Subject < 72 chars, imperative mood ("add" not "added")

Body: what and why, not how (the diff shows how)

Reference PRP path in footer when implementing features

Pull Requests

Use gh pr create (GitHub) or glab mr create (GitLab)

PR title matches commit subject

Description includes: summary, changes list, testing done, security notes

Link to PRP: .context/features/[NNN]-[name]/PRP.md

Rebasing

Prefer rebase over merge for feature branches (linear history)

git rebase -i main to squash WIP commits before PR

Never rebase shared/published branches

Conflict Resolution

Always pull latest main before starting work

When resolving conflicts: understand both sides before choosing

Run full test suite after every conflict resolution

If conflict is complex, ask before resolving

Common Operations

# Start feature git checkout -b feat/[name] main # Sync with main git fetch origin && git rebase origin/main # Interactive squash before PR git rebase -i main # Create PR gh pr create --title "feat: [description]" --body "[PR body]" # Clean up after merge git checkout main && git pull && git branch -d feat/[name]