How do I install the Git Workflow skill?

Run npx skillmds@latest add n43-studio/git-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Workflow?

N43-Studio (@n43-studio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Workflow by n43-studio — Agent Skill

Name: Git Workflow
Rating: 4.2 (5 reviews)
Author: N43-Studio

Git Workflow

Provides git workflow conventions including conventional commits, branch naming, PR review guidelines, and issue tracker integration. Use when performing git operations, creating commits, opening PRs, conducting code reviews, or managing branches.

N43-Studio Updated Sep 10, 2026

File contents

Git Workflow Conventions

Quick Start

Commit Format

All commits follow Conventional Commits:

<type>(<scope>): <description>

[optional body]

[optional footer]

Types: feat, fix, docs, style, refactor, perf, test, chore, build, ci

Scopes: Define project-specific scopes in AGENTS.md. Common examples: api, ui, db, auth, build, cursor

Agentic workflow commits: Use chore(cursor): for commands/rules/plans, docs(cursor): for reference docs.

Branch Naming

Default model: personal dev branch (e.g., ryan, erik).

Feature branches are optional for exceptional isolation needs.
Issue association is done through commit footer links, not branch naming.

PR Review Prefixes

Prefix	Meaning	Blocking
`major:`	Must fix	Yes
`minor:`	Should fix	No
`nit:`	Tiny improvement	No
`suggestion:`	Loose idea	No
`question:`	Clarification	No
`praise:`	Positive feedback	No

Use "we"/"the code" instead of "you" in review comments.

Issue Tracker Integration

Configure your issue tracker in AGENTS.md:

Magic words auto-close on merge: Closes {PREFIX}-XXX, Fixes {PREFIX}-XXX, Resolves {PREFIX}-XXX
Link without closing: Refs {PREFIX}-XXX

Examples:

Linear: branch ryan, footer Closes N43-123
Jira: branch erik, footer Closes PROJ-456
GitHub: branch ryan, footer Closes #789

PR Workflow

Squash commits into logical chunks
Rebase onto main (never merge)
Use --force-with-lease when pushing after rebase

Additional Resources

For complete documentation, see reference.md

---name: git-workflowdescription: Provides git workflow conventions including conventional commits, branch naming, PR review guidelines, and issue tracker integration. Use when performing git operations, creating commits, opening PRs, conducting code reviews, or managing branches.---# Git Workflow Conventions## Quick Start### Commit FormatAll commits follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/):```<type>(<scope>): <description>[optional body][optional footer]```**Types**: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `chore`, `build`, `ci`**Scopes**: Define project-specific scopes in `AGENTS.md`. Common examples: `api`, `ui`, `db`, `auth`, `build`, `cursor`**Agentic workflow commits**: Use `chore(cursor):` for commands/rules/plans, `docs(cursor):` for reference docs.### Branch NamingDefault model: personal dev branch (e.g., `ryan`, `erik`).- Feature branches are optional for exceptional isolation needs.- Issue association is done through commit footer links, not branch naming.### PR Review Prefixes| Prefix | Meaning | Blocking || ------------- | ----------------- | -------- || `major:` | Must fix | Yes || `minor:` | Should fix | No || `nit:` | Tiny improvement | No || `suggestion:` | Loose idea | No || `question:` | Clarification | No || `praise:` | Positive feedback | No |Use "we"/"the code" instead of "you" in review comments.### Issue Tracker IntegrationConfigure your issue tracker in `AGENTS.md`:- Magic words auto-close on merge: `Closes {PREFIX}-XXX`, `Fixes {PREFIX}-XXX`, `Resolves {PREFIX}-XXX`- Link without closing: `Refs {PREFIX}-XXX`Examples:- Linear: branch `ryan`, footer `Closes N43-123`- Jira: branch `erik`, footer `Closes PROJ-456`- GitHub: branch `ryan`, footer `Closes #789`### PR Workflow1. Squash commits into logical chunks2. Rebase onto `main` (never merge)3. Use `--force-with-lease` when pushing after rebase## Additional Resources- For complete documentation, see [reference.md](reference.md)

Frequently asked questions