skills.rest
ravenoak
ravenoakCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Automates Git feature-branch workflows including commits, PRs, CI checks, merges, and cleanup in Cursor.

Updated Apr 27, 2026
Search Tags:#automation#git#workflow#code-review#ci#branch-management#pull-request
One-click install
npx skills add https://github.com/ravenoak/oh-my-stigmergy --skill git-workflow-ravenoak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ravenoak/oh-my-stigmergy/tree/main/.cursor/skills/git-workflow
Command: npx skills add https://github.com/ravenoak/oh-my-stigmergy --skill git-workflow-ravenoak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complete Git work in Cursor with oh-my-stigmergy policy—feature branches, atomic commits at end of work, PR with green allium-specs, squash/rebase merge, delete merged local and remote branches, fetch --prune. Use when branching, committing, pushing, opening or merging PRs, cleaning up stale branches, or finishing an agent session with repo changes.

Core Features & Use Cases

  • Feature-branch workflow with atomic commits
  • PR gating with green allium-specs checks and CI integration
  • Squash/rebase merge strategy and branch cleanup (local + remote)
  • Fetch prune and stale-branch cleanup for repository hygiene

Quick Start

Start from main, create a feature branch, implement changes, push, open a PR, and merge with squash or rebase once all checks pass.

Frequently Asked Questions about git-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a Git workflow with feature branches and pull requests?▼

You can automate a Git workflow by creating feature branches from main, making atomic commits, pushing, opening PRs, and merging with squash or rebase once CI checks pass. This enforces branch hygiene and PR gating end-to-end.

What is the best way to manage branch hygiene and stale branches after a merge?▼

The best way to manage branch hygiene after a merge is to delete merged local and remote branches, then run fetch --prune to clean up stale references. This keeps the repository organized and prevents branch accumulation.

How does PR gating with CI checks work during feature development?▼

PR gating with CI checks works by enforcing allium-specs validation and continuous integration tests to pass before a pull request can be merged. This ensures code quality and prevents unverified changes from entering the main branch.

Can I use squash and rebase merge strategies for atomic commits in Cursor?▼

Yes, you can use squash and rebase merge strategies for atomic commits in Cursor. The workflow supports merging feature branches into main using either method once all PR gating and CI checks are successfully passed.

When do I need to run fetch prune and clean up stale branches?▼

You need to run fetch prune and clean up stale branches after finishing an agent session with repo changes or merging a pull request. This removes deleted remote tracking branches and maintains strict repository hygiene.

Related Skills

Explore More Software Engineering Skills→
Soul-Brews-StudioSoul-Brews-Studio
116

merged

Switch to main, pull latest changes, and delete merged branches.

Official
Basic
aberrantCodeaberrantCode
1

git-cleanup

Audit and remove stale git worktrees and branches merged into dev.

Community
Advanced
ravenoakravenoak

github-flow

Enforce GitHub Flow with feature branches, atomic commits, and CI-gated PR merges.

Community
Intermediate
greghavensgreghavens
8

git-branch-management

Manage Git branches, atomic commits, and pull requests via GitHub CLI.

Community
Advanced