BumpyClock/agent-templates / skills/git-workflow
git-workflow
UnverifiedPrepare branches, commits, pull requests, stacked-PR plans, authorized merges, release checklists, or safe worktree and simulator cleanup.
Git and releases
Use this skill for commit or PR preparation, stacked-PR planning, an authorized merge, release preparation, or requested worktree cleanup. Follow repository templates and policies before these defaults. This skill defines conventions, not permission to commit, push, open or merge a PR, publish a release, or delete user state.
Choose the procedure
- For an authorized PR, read Opening a PR. For PR feedback or a request to watch CI, use Resolve PR comments; open a PR and monitor it for personal repos.
- For a large change or dependent PRs, read Stacked PRs. It owns the decision gates and native
gh stackcommands. - For local screenshots or recordings that belong on a GitHub PR, read Attaching media to a pull request. Upload only to the intended repository and PR.
Branch & PR titles
- Use short, descriptive branch names such as
fix/issue-123orfeat/session-cache. - Use
type(scope): subjectfor PR titles and commit subjects. Choosefeat,fix,docs,refactor,test,chore, orperf; name the affected area in the scope. Write a short, imperative subject without a final period. - Explain the problem and reason for the change before implementation details. Name concrete behavior, relevant symbols, compatibility changes, and material decisions.
- Use
Why,Scope,Tradeoffs,Blast Radius, andVerificationsections when useful, not as a required template. Omit empty sections and boilerplate. - State relevant validation commands and results, plus material checks omitted and why. Reuse evidence under the programming validation guidance; preparing a commit or PR does not add a test gate.
- Include screenshots or videos for user-visible changes when they substantiate a claim or improve reviewability. Keep commit bodies focused on rationale that the subject and diff do not explain.
Merges and releases
For authorized merges, follow the repository's merge policy. Do not infer squash, merge-commit, or rebase strategy from the target branch name. If no policy is available and the strategy affects history or a stacked change, ask before merging.
For release preparation, follow the repository's release checklist. Stop at the requested deliverable without inferring permission to publish or deploy.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 107k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 107k | Updated | Claude CodeCodex | Verified | Install |