Git Pr Workflow

Git PR Workflow

Overview

Use this skill when the repository should follow a predictable Git and handoff workflow instead of re-explaining the same steps in every AGENTS.md.

The goal is to keep delivery flow consistent across repositories:

• do not work on main
• use a sensible working branch with repo-appropriate naming
• implement in coherent batches
• pause for user review before the final verification gate
• run the real verification gate after acceptance
• commit with consistent prefixes
• push the ready branch
• finish with copy-pasteable PR notes

Read references/workflow-checklist.md when deciding branch naming, docs-only verification exceptions, or the expected PR-notes shape.

Core Rules

• Repo-specific workflow rules still win when they are stricter or more specific.
• Explicit user instructions in chat override the default workflow.
• Before editing, confirm the current branch is not main.
• If the repo documents branch naming conventions, follow them.
• If no repo convention exists, use a clear branch name with a conventional prefix.
• Use targeted checks while implementing, but reserve the final verification gate for after user review and acceptance.
• Commit in reasonable, coherent batches. A single PR may contain multiple commits.
• Use capitalized conventional commit prefixes such as Feature:, Fix:, Docs:, Chore:, Refactor:, or Test:.
• After acceptance, verification, and commit, push the branch unless the user explicitly wants to stop before push.
• End with copy-pasteable PR notes in a single fenced code block unless the branch is intentionally not PR-ready.

Token Discipline

• Do not narrate every Git command.
• Report only:
  • branch state and branch choice when relevant
  • review pause status
  • final verification result
  • commits created
  • whether the branch was pushed
  • PR notes or the reason they were intentionally omitted
• Expand only when branch hygiene, verification exceptions, or push readiness is non-obvious.

Workflow

1. Start from branch hygiene

Before implementation:

• inspect the current branch
• if on main, create or switch to a working branch before editing
• if the repo already defines branch naming rules, follow them

Prefer short, descriptive branch names such as:

• feature/player-card-charts
• bugfix/search-empty-state
• docs/api-readme-refresh
• chore/update-tooling

For repositories that already standardize on prefixes like feature/, bugfix/, chore/, docs/, refactor/, or test/, preserve that convention.

2. Implement in coherent batches

Keep work grouped into meaningful units:

• one feature slice
• one bug fix
• one docs refresh
• one test batch
• one refactor concern

Do not wait until the very end to think about commit boundaries.

3. Use iterative checks while working

While implementing, run only the checks needed to stay honest:

• focused tests
• typecheck
• lint
• targeted verification for the touched behavior

These are implementation checks, not the final gate.

4. Pause for user review before the final gate

After the batch is ready:

• summarize the implemented change briefly
• ask the user to review
• do not run the final verify gate yet unless the user has already accepted the batch
• if review feedback arrives, iterate and return to the review pause as needed

This review pause is part of the workflow, not an optional courtesy.

5. Run the final verification gate after acceptance

After the user explicitly accepts the batch:

• run the repo's real verification gate, usually npm run verify
• if it fails, fix the issue and rerun the necessary checks until it passes

Docs-only changes may skip the full gate only when the touched files are limited to docs or workflow text and the repo treats that as a valid exception.

Read references/workflow-checklist.md for the usual docs-only and repo-config exception boundaries.

6. Commit in ready batches

Once the accepted batch is verified, commit it unless the user explicitly wants to hold commits.

Use commit messages like:

• Feature: Add park visit summary cards
• Fix: Correct goalie playoff ranking sort
• Docs: Refresh local setup notes
• Chore: Tighten verify script inputs

Use sentence-style capitalization after the colon.

7. Push and prepare handoff

When the branch is accepted, verified, and committed:

• push the branch
• if more implementation is still planned on the same branch, say so clearly
• if the branch is PR-ready, provide copy-pasteable PR notes

PR notes should usually include:

• Title
• Summary
• Verification

Wrap the notes in one fenced code block so they are easy to copy.

Anti-Patterns

• starting implementation on main
• inventing a one-off branch name when the repo already has a convention
• treating targeted tests as a substitute for the final verify gate
• running final verify before the user has reviewed the batch
• building one giant end-of-task commit when the work had obvious batch boundaries
• skipping push or PR notes without saying why
• mixing docs-only exceptions into runtime-code changes without calling out the difference

Expected Behavior When This Skill Is Used

When applying this skill to a task:

1. Check branch state before editing.
2. Use a repo-appropriate working branch.
3. Implement in coherent batches with iterative checks.
4. Pause for user review before the final verification gate.
5. After acceptance, run the real verification gate.
6. Commit with consistent prefixes.
7. Push the branch and provide fenced PR notes when ready.

Source: maestor/node-fantrax-stats-parser — distributed by TomeVault.