Name: git-workflow
Author: YSMsimon

Imported from YSMsimon/Warden (skills/git-workflow/SKILL.md). Install upstream with npx skills add YSMsimon/Warden --skill git-workflow. Copyright stays with the author.

Git Workflow

Help the user work effectively with git — from individual commits to full branching strategies and pull request descriptions.

Commit messages — Conventional Commits

Format

<type>(<scope>): <short summary>

<optional body — explain WHY, not what>

<optional footer>

Types

Type	When to use
`feat`	New user-facing feature
`fix`	Bug fix
`refactor`	Code restructuring, no behaviour change
`perf`	Performance improvement
`test`	Adding or fixing tests
`docs`	Documentation only
`chore`	Build, deps, tooling
`ci`	CI/CD pipeline
`revert`	Reverting a previous commit

Rules

Summary: max 50 chars, imperative mood ("add" not "added"), no trailing period
Blank line between summary and body
Body: explain why — the diff shows what
Wrap body at 72 characters
Reference issues in footer: Closes #42

Branching strategy

GitHub Flow (default — simple projects, CI/CD)

main is always deployable
Branch for every feature or fix
PR → review → merge to main

Branch naming: feature/jwt-refresh, fix/profile-update-race, chore/upgrade-dependencies

Git Flow (versioned releases, larger teams)

main: production, always tagged
develop: integration branch
feature/*: from develop, back to develop
release/*: from develop when prepping a release
hotfix/*: from main for urgent fixes, merge back to both main and develop

When the user provides context

If they share a diff or describe changes — write the commit message directly, don't just explain the format.

If they show a messy branch history — recommend the exact rebase commands with the real commit count.

If they describe a PR — write the full PR description using the template.

Install git-workflow and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "ysmsimon-warden-git-workflow", "kind": "skill", "name": "git-workflow", "description": "Guide git workflows including writing commit messages, structuring branches, writing PR descriptions, resolving merge conflicts, squashing commits, rebasing, tagging releases, and undoing mistakes. Use this skill whenever the user wants help with a commit message, pull request, branching strategy, git history, rebasing, undoing a commit, stashing, or anything git-related. Trigger on phrases like \"write a commit message\", \"help me PR this\", \"how should I branch\", \"clean up my commits\", \"git conflict\", \"undo\", \"revert\", \"stash\", or any git command question.", "publisher": "YSMsimon", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Guide git workflows including writing commit messages, structuring branches, writing PR descriptions, resolving merge conflicts, squashing commits, rebasing, tagging releases, and undoing mistakes. Use this skill whenever the user wants help with a commit message, pull request, branching strategy, git history, rebasing, undoing a commit, stashing, or anything git-related. Trigger on phrases like \"write a commit message\", \"help me PR this\", \"how should I branch\", \"clean up my commits\", \"git conflict\", \"undo\", \"revert\", \"stash\", or any git command question." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/YSMsimon/Warden", "path": "skills/git-workflow/SKILL.md", "ref": "3a39383012260e56eb8f161c3d9347416624f923", "url": "https://github.com/YSMsimon/Warden/blob/3a39383012260e56eb8f161c3d9347416624f923/skills/git-workflow/SKILL.md", "key": "YSMsimon/Warden/skills/git-workflow/SKILL.md" } }, "instructions": "# Git Workflow\n\nHelp the user work effectively with git — from individual commits to full branching strategies and pull request descriptions.\n\n---\n\n## Commit messages — Conventional Commits\n\n### Format\n```\n<type>(<scope>): <short summary>\n\n<optional body — explain WHY, not what>\n\n<optional footer>\n```\n\n### Types\n| Type | When to use |\n|---|---|\n| `feat` | New user-facing feature |\n| `fix` | Bug fix |\n| `refactor` | Code restructuring, no behaviour change |\n| `perf` | Performance improvement |\n| `test` | Adding or fixing tests |\n| `docs` | Documentation only |\n| `chore` | Build, deps, tooling |", "cost": { "context_tokens": 454 } }

git-workflow

About