Best use case
git-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Git workflow: branches, PR, merge, cleanup
Teams using git-workflow should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git-workflow/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How git-workflow Compares
| Feature / Agent | git-workflow | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Git workflow: branches, PR, merge, cleanup
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Git Workflow > Standard Git workflow: branches, commits, PR, merge ## When to use - Any change to data or code going to GitHub - "commit" / "push" / "create PR" / "merge" - After running any skill that modifies files ## Rules ### 1. Never push to main directly Always through PR: ```bash git checkout -b <prefix>/<name> # changes git add <files> git commit -m "Description" git push -u origin <prefix>/<name> gh pr create --title "..." --body "..." gh pr merge --squash --delete-branch git checkout main && git pull ``` ### 2. Branch naming | Change type | Prefix | Example | |-------------|--------|---------| | New feature | `feature/` | `feature/clientk-lookalikes` | | Data update | `update/` | `update/stream-cohort-2026-02-08` | | Fix | `fix/` | `fix/crm-product-fk` | | New lead/contact | `feat/` | `feat/kyrylo-mazur-lead` | ### 3. Merge strategy **Always squash merge + delete branch:** ```bash gh pr merge --squash --delete-branch ``` - `--squash` -- one clean commit in main - `--delete-branch` -- automatically deletes the branch after merge ### 4. After merge ```bash git checkout main git pull origin main ``` ### 5. Commit message format ``` <Action>: <what exactly was done> Details if needed. Co-Authored-By: Claude <noreply@anthropic.com> ``` Examples: - `Add 24 stream participants (p-fb-018..041)` - `Update task-042: expand stream outreach to 39 people` - `Fix CRM product FK consistency` ### 6. Cleanup If old branches have accumulated: ```bash # View all remote branches gh api repos/your-org/<repo>/branches --jq '.[].name' # Delete a specific one gh api repos/your-org/<repo>/git/refs/heads/<branch> -X DELETE ``` ## Repositories | Repo | What's there | Prefix | |------|-------------|--------| | `your-org/$PROJECT_ROOT` | CRM + PM data | `update/`, `feat/`, `fix/` | | `your-org/claude-skills` | Claude skills | `update/`, `feature/` | | `your-org/google-tools` | Google API scripts | `feature/`, `fix/` | ## Restrictions - DO NOT commit secrets (.env, token.json, credentials.json) - DO NOT force push - DO NOT rebase main - DO NOT leave dead branches after merge ## Related skills - `change-review` -- CRM/PM data validation before PR - `code-review` -- code review for code PRs
Related Skills
workflow-automation
Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
orchestration-workflow
> Agent 编排工作流——多 Agent 任务分发与协调
av-sync-workflow
Audio-to-video synchronization workflow: analyze audio (beats, tempo, emotion, mood), find/match video clips to match scene and feeling, sync cuts to music beats, generate beat-marked videos. Use when user wants to: (1) turn a song into a music video, (2) sync video clips to music beats, (3) create a video that matches audio mood/scene/rhythm, (4) do beat-matching video editing. Triggers: "制作音乐视频", "音频转视频", "beat matching", "卡点视频", "音视频同步", "视频踩点", "music video creation", "sync video to audio"
wemp-operator
> 微信公众号全功能运营——草稿/发布/评论/用户/素材/群发/统计/菜单/二维码 API 封装
zsxq-smart-publish
Publish and manage content on 知识星球 (zsxq.com). Supports talk posts, Q&A, long articles, file sharing, digest/bookmark, homework tasks, and tag management. Use when publishing content to 知识星球, creating/editing posts, uploading files/images/audio, managing digests, batch publishing, or formatting content for 知识星球.
zoom-automation
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
zoho-crm-automation
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
ziliu-publisher
字流(Ziliu) - AI驱动的多平台内容分发工具。用于一次创作、智能适配排版、一键分发到16+平台（公众号/知乎/小红书/B站/抖音/微博/X等）。当用户需要多平台发布、内容排版、格式适配时使用。触发词：字流、ziliu、多平台发布、一键分发、内容分发、排版发布。
zhihu-post-skill
> 知乎文章发布——知乎平台内容创作与发布自动化
zendesk-automation
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.
youtube-knowledge-extractor
This skill performs deep analysis of YouTube videos through **both information channels** Multimodal YouTube video analysis through both audio (transcript) and visual (frame extraction + image analysis) channels. Especially powerful for HowTo videos, tutorials, demos, and explainer videos where what is SHOWN (screenshots, UI demos, diagrams, code, physical actions) is just as important as what is SAID. Use this skill whenever a user wants to analyze, summarize, or create step-by-step guides from YouTube videos, or when they share a YouTube URL and want to understand what happens in the video. Triggers on requests like "Analyze this YouTube video", "Create a step-by-step guide from this video", "What does this video show?", "Summarize this tutorial", or any YouTube URL shared with analysis intent.