Skip to main content
affpapa.org
RU EN
prompt GP ChatGPT

Git Workflow taste — Claude & Claude.ai prompt: git process rules

A prompt that gives an AI assistant trunk-based habits: short-lived branches, Conventional Commits, squash-merge and a protected main.

Open on GitHub

What Git Workflow taste does

This is a set of git process rules you paste into a chat as a system instruction. The assistant starts recommending short-lived branches off main, names like fix/login-redirect, imperative commit subjects and prefixes such as feat, fix, chore, docs, refactor. In the commit body it asks for the reason behind a change instead of a restatement of the diff.

Inside are twenty-three items with confidence scores. The review side: one approving review, green CI, squash-merge, PRs under about 400 changed lines, and what, why and how-to-test sections in the description. Main protection is separate: no direct pushes, no force pushes, and your own branch only with --force-with-lease. Other items cover secrets, Git LFS, .gitattributes, git bisect and CODEOWNERS.

The prompt is not tied to a repository and does not configure git itself. It shapes what the model suggests. If your team merges main into branches or keeps long-lived feature branches, the advice will clash with your process — worth settling which workflow you actually want first.

What it helps with

  • align an assistant's git advice with team rules
  • settle branch names and commit subjects
  • split a large PR into smaller pieces
  • set up main protection and required review
  • explain why a change was made, not the diff

Example prompts for the agent

  • Follow the git process rules in this prompt and suggest a branch and commits for the login fix
  • Check my change plan against the trunk-based workflow
  • Write a PR description with what, why and how-to-test sections

How to install Git Workflow taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Git Workflow taste

How to install Git Workflow taste in Claude?

There is no install command. Paste the prompt text into the system instructions or at the top of the conversation so the model keeps these rules in context.

What does Git Workflow taste do?

It gives the assistant trunk-based rules: short-lived branches, Conventional Commits, squash-merge, main protection and review requirements.

Does it need repository access?

No. It is a text prompt for a chat; it does not read your git or change repository settings.

Source text

prompts.csv · CC0-1.0 
# Git workflow taste of a trunk-based team
- Work trunk-based: short-lived branches off main, merged within two days. Confidence: 0.90
- Name branches as <type>/<short-topic>, for example fix/login-redirect. Confidence: 0.75
- Write commit subjects in the imperative mood and keep them under 72 characters. Confidence: 0.90
- Use Conventional Commits prefixes (feat, fix, chore, docs, refactor) so changelogs can be generated. Confidence: 0.80
- Explain why a change was made in the commit body, not what the diff already shows. Confidence: 0.85
- Keep each commit buildable and focused on one logical change. Confidence: 0.85
- Rebase your branch onto main instead of merging main into it. Confidence: 0.80
- Squash-merge pull requests so main has one commit per change. Confidence: 0.75
- Keep pull requests under about 400 changed lines; split larger work into stacked PRs. Confidence: 0.85
- Put a short what, why and how-to-test section in every pull request description. Confidence: 0.85
- Require one approving review and green CI before merging to main. Confidence: 0.90
- Protect main: no direct pushes and no force pushes. Confidence: 0.95
- Only force push your own branch, and always with --force-with-lease. Confidence: 0.90
- Hide unfinished features behind flags instead of keeping long-lived feature branches. Confidence: 0.85
- Tag releases with semantic version tags such as v1.4.2 on main. Confidence: 0.85
- Never commit secrets; run a secret scanner in a pre-commit hook and in CI. Confidence: 0.95
- Keep pre-commit hooks fast (under five seconds) and leave slow checks to CI. Confidence: 0.80
- Use a .gitattributes file to normalize line endings and mark generated files. Confidence: 0.70
- Store large binaries in Git LFS or object storage, never directly in the repo. Confidence: 0.85
- Use git bisect with a scripted test to hunt down regressions. Confidence: 0.70
- Revert a bad commit on main first and investigate afterwards. Confidence: 0.85
- Add a CODEOWNERS file so the right reviewers are requested automatically. Confidence: 0.75
- Delete branches automatically after they are merged. Confidence: 0.90

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for Git and GitHub →
git-workflow-manager VoltAgent Community Designs branching models, configures Git hooks, and automates merge flows. Helpful when merge conflicts slow down releases. 384installs git-workflow affaan-m A skill that hands your agent Git conventions: which branching strategy to pick, how to word commits, and when rebase beats merge. CX Codex +1 5,000installs git-commit official github This skill reviews Git changes, stages related files, and creates Conventional Commits. Use it when you want an agent to make one commit or split work into separate commits. 47,165installs tiny-stepping official github Enforces an incremental workflow where the assistant makes the smallest meaningful change, pauses for review, and commits before moving forward. 57installs

From the same set77

The whole set →
Universal LLM Operating Guidelines A rule set for LLM-assisted coding: understand the task first, then touch the code. Cuts invented APIs and stray edits. GP ChatGPT ★ 174,597repo stars Redis Caching taste A prompt that hands your AI assistant a working set of Redis caching rules: cache-aside reads, TTL with jitter, delete-on-write invalidation. Useful when you design a cache and want the sharp edges covered. GP ChatGPT ★ 174,597repo stars Error Handling taste A prompt that gives an AI assistant the error-handling taste of a TypeScript backend engineer: validate input, split expected errors from bugs, log once, answer with problem+json. GP ChatGPT ★ 174,597repo stars Kubernetes taste A prompt that hands your AI assistant a platform team's Kubernetes rules: GitOps, probes, resources, pod security. Useful when you ask a model to write or review manifests. GP ChatGPT ★ 174,597repo stars Monorepo taste A prompt that hands the agent a fixed set of monorepo conventions: pnpm workspaces, Turborepo, package boundaries and shared configs. Useful when repo structure keeps drifting. GP ChatGPT ★ 174,597repo stars Rust CLI taste A prompt that tells the model how to write a Rust command-line tool: argument parsing, error handling, output streams, tests. GP ChatGPT ★ 174,597repo stars React State Management taste A ruleset for picking React state tools: when to use useState, Zustand, Context and TanStack Query. Helps avoid overbuilt global stores and duplicated state. GP ChatGPT ★ 174,597repo stars Observability taste A prompt that tells an AI assistant how to wire traces, metrics and logs into a service. Handy when you ask a model to write instrumented code. GP ChatGPT ★ 174,597repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor