git-pull-requests

Installation
SKILL.md

Rule

The agent prepares and opens the PR; the user reads it and merges. Every step below exists because skipping it once produced a wrong status report, stranded work, or a PR the user couldn't review. Committing itself is governed by git-commit-requires-approval and git-commit-messages. This skill starts once a commit exists and a PR is wanted.

1. One branch, one concern, one PR

  • Branch from current main with a name that says what changes (feat/quick-add-dates, fix/sheet-scroll). Never name another client or project in a branch, commit or PR, even when a design was inspired by one.
  • One feature per PR. Design changes and feature work go in separate PRs. An unrelated fix found along the way gets its own PR off main.
  • "Write it down for later" becomes a docs-only PR (roadmap row, open questions), not code.
Installs
2
First Seen
13 days ago