Skip to content
Skills Library
Programming · Automation

gitflow

/gitflow

Branches, commits, pushes and pull requests for this repo - naming, history rules, the PR title and a body filled from the PR template and the spec. Use when you create a branch, commit, push, or open or update a PR. Don't use for review comments on an open PR (use pr-comments-fix).

Repository
spur-board ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Branches, commits, pushes and pull requests for this repo - naming, history rules, the PR title and a body filled from the PR template and the spec. Use when you create a branch, commit, push, or open or update a PR. Don't use for review comments on an open PR (use pr-comments-fix).

Original author description

Branches, commits, pushes and pull requests for this repo - naming, history rules, the PR title and a body filled from the PR template and the spec. Use when you create a branch, commit, push, or open or update a PR. Don't use for review comments on an open PR (use pr-comments-fix).

How it works

  1. Branch
  2. Commits
  3. History
  4. PR title
  5. PR body
  6. Public text
Original SKILL.md headings · 92 lines, 767 words
SKILL.md preview
---
name: gitflow
description: Branches, commits, pushes and pull requests for this repo - naming, history rules, the PR title and a body filled from the PR template and the spec. Use when you create a branch, commit, push, or open or update a PR. Don't use for review comments on an open PR (use pr-comments-fix).
---

# Gitflow

One issue, one branch, one PR. Explain why in the PR body.

## Branch

- Name: `<agent>-<issue-number>-<slug>`, e.g. `claude-10-process-skills`; use a short lowercase slug.
- Branch from `main` at the `origin/main` SHA the handoff gives. One issue per branch.

## Commits

- Conventional commits: `<type>(<scope>): <summary>`, imperative, no trailing period.
- Changes to agent files (`.agents/`, `.claude/`, `.codex/`, `AGENTS.md`) go in their own
  commit (`chore(agents)`, or `fix(<skill>)` for a stale rule), apart from code changes.
- Leave the session marker out of commits and PR titles.
- Run `pnpm check` before opening the PR as `AGENTS.md` requires; use it again when a wider local
  check is needed. Without a `package.json`, report `no checks available`. Never wait for or poll
  remote CI.
- The pre-push hook checks the refs being pushed: changed-file format and lint plus types and unit
  tests for changed packages (all packages for shared root changes). Push only the checked-out
  HEAD. `VITEST_MAX_WORKERS` defaults to two and accepts a positive integer override. CI runs
  `check:full`, including startup and process tests.

## History

- Never amend, rebase or force-push a commit that has been pushed. Fixes go in new commits.
- The branch conflicts with `main`: merge `main` into the branch, resolve, commit the merge. Do
  not rebase a pushed branch.
- Never push to `main`, merge a PR, or approve one. A human merges; the repo squash-merges.

## PR title

A conventional commit with the issue number first in the subject, e.g.
`feat(core): #15 add the config schema`, so the PR list shows which issue to read. The type comes
first because releases are versioned from it. The squash commit takes the PR title and GitHub
appends the PR number: `feat(core): #15 add the config schema (#71)`.

## PR body

1. Copy `.github/pull_request_template.md` to `.scratch/pr-body-<issue-number>.md`.
2. Fill each section as mapped below and follow the rules in the template's comments.
3. Delete every `<!---` comment line, the placeholder rows, and `## Changed checks` when it has
   no entries.
4. Keep `Closes #<issue-number>`. The last line is the session marker: the one your launch
   instructions give, else `[AI-generated, session: $SPUR_SESSION]` with the variable expanded.
   It appears once.
5. No PR yet: `gh pr create --base main --title "<title>" --body-file .scratch/pr-body-<N>.md`,
   opened ready for review. A PR exists: `gh pr edit <N> --body-file .scratch/pr-body-<N>.md`.
   Never mark a draft you did not open as ready.

### Mapping from the spec

- Description - what changes for the user, the CLI or API caller, or the agent, from the spec's
  Objective. Out-of-scope follow-ups go in the last bullet with their issue number.
- Architecture decisions - one row per `### Design` entry: decision, the alternative it beat,
  why. Reword each row in plain words; a spec row that cites a private decision or task ID, a
  person, a company or a machine path loses that reference in the PR. No material choice -> one
  line `None - <why>`, e.g. `None - follows the existing pattern in the manager skill`. Never
  invent an alternative to fill a row.
- Testing - one line per acceptance criterion of the issue, in the issue's order: the criterion,
  then the test, or the command and the output it printed, taken from the spec's
  `### Verification` and the close-out evidence. Tick `[x]` only when that proof was observed in
  this run; otherwise leave `[ ]` and write `pending - <why>`.
- Risk - `high`, `medium` or `low` with a one-line reason, from the spec's `### Risks`.
- Changed checks - one line per entry below, from the developer's `Changed checks` output.

### Changed checks

This list wins over the template's shorter comment. Each of these gets its own line, saying what
changed and why:

- deleted tests, or fewer `expect` assertions;
- weakened or changed assertions: a looser matcher, a changed expected value;
- skipped or focused tests: `.skip`, `.only`, `xit`;
- changed snapshots or golden files;
- changed test, lint, TypeScript or CI config, or the shared test kit;
- disabled or loosened lint rules, e.g. `eslint-disable`;
- type escapes: `@ts-ignore`, `@ts-expect-error`, `as any`;
- `continue-on-error` or any other way to let a CI step fail silently;
- loosened thresholds: coverage, timeouts, retries.

`pnpm guardrails` has no rule for a changed expected value (`RULE_IDS` in
`scripts/guardrails.ts`); add that line by hand.

Any other change to a test or a check also gets a line. No entries -> delete the section.

## Public text

PR titles, bodies, commits and comments are public. Write them in English, in your own words.
Leave out private notes, decision or task IDs, people, companies and machine paths.

Versions

RepositoryScoreLicence
This page · AnDeVerin/spur-board90MIT
Mindrally/skills100Apache-2.0
zach-source/claude-plugins100MIT
mgiovani/cc-arsenal90MIT

Database snapshot: 13.11.2026 · package version 1c2348c853e4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100write-pr
    Draft a pull request title and body from the current branch's diff and commit history, following the project's PR template and title conventions. Use when the user is about to open a PR and wants ready-to-paste content, or asks to write, draft, or fill in a PR description.…
  • 100git-workflow-guide
    Guide Git branching strategies, branch naming, and merge operations. Use when: creating branches, merging, pull requests, Git workflow questions. Not for: composing the commit message — use /commit; the safety checks around pushing — use /push. Keywords: branch, merge, PR, pull…
  • 100create-pr
    Create Git branches, commits, pushes, and GitHub pull requests for Next.js. Use when the user asks to create a branch, commit current changes, open a PR or draft PR, publish a pull request, or recover from gh pr create / PR template issues. Covers…
  • 86pr
    Use for /pr, or ''create a PR'' / ''open a pull request'' — creates a pull request for the current branch against the repo''s base branch with a formatted title and body. Not for reviewing an existing PR (review-pr).
  • 100git-commit-and-workflow
    Git commit, branch and pull request best practices using Conventional Commits. Use whenever creating commits, naming branches, preparing pull requests, writing commit messages, or when asked to commit, push, merge or release code.
  • 100pr
    Use for /pr, or 'create a PR' / 'open a pull request' — creates a pull request for the current branch against the repo's base branch with a formatted title and body. Not for reviewing an existing PR (review-pr).

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.