KS
Killer-Skills

f3-git-workflow — how to use f3-git-workflow how to use f3-git-workflow, f3-git-workflow setup guide, git workflow management, feature branch management, monorepo development, f3-git-workflow vs gitflow, f3-git-workflow install, f3 nation monorepo

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing streamlined git workflow management with feature branches and merge commits. f3-git-workflow is a git workflow management system using feature branches with merge commits for clear history and streamlined development

Features

Uses feature branches with merge commits for clear history
Supports branch structure with main, staging, dev, feat, fix, and bug branches
Manages remotes with md and f3 repositories for seamless collaboration
Enables push and pull requests from dev to staging and main branches
Utilizes merge commits for pre-production testing and production deployment

# Core Topics

F3-Nation F3-Nation
[5]
[7]
Updated: 2/25/2026

Quality Score

Top 5%
36
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
Cursor IDE Windsurf IDE VS Code IDE
> npx killer-skills add F3-Nation/f3-nation/f3-git-workflow

Agent Capability Analysis

The f3-git-workflow MCP Server by F3-Nation is an open-source Categories.community integration for Claude and other AI agents, enabling seamless task automation and capability expansion. Optimized for how to use f3-git-workflow, f3-git-workflow setup guide, git workflow management.

Ideal Agent Persona

Perfect for Development Agents needing streamlined git workflow management with feature branches and merge commits.

Core Value

Empowers agents to manage monorepos using a git workflow with clear history, leveraging feature branches, merge commits, and remotes like 'md' and 'f3' for efficient collaboration and version control.

Capabilities Granted for f3-git-workflow MCP Server

Automating feature branch creation with 'feat/*', 'fix/*', and 'bug/*' naming conventions
Merging commits from development integration branches to staging and production environments
Maintaining a clear history by using merge commits and pushing to remotes like 'md' and 'f3'

! Prerequisites & Limits

  • Requires git version control system
  • Limited to specific branch structure with 'main', 'staging', 'dev', and feature branches
Project
SKILL.md
4.5 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

F3 Nation Git Workflow

This workflow uses feature branches with merge commits to maintain clear history.

Branch Structure

  • main - Production (merges from staging only)
  • staging - Pre-production testing (merges from dev only)
  • dev - Development integration (merges from feature branches)
  • feat/*, fix/*, bug/* - Feature/fix branches (branch from dev)

Remotes

  • md (High-Country-Dev) - Always push here
  • f3 (F3-Nation client) - Push only when explicitly requested

Complete Workflow

1. Create Feature Branch

bash
1# Ensure dev is up to date 2git checkout dev 3git pull md dev 4 5# Create feature branch 6git checkout -b feat/your-feature-name

2. Make Changes and Commit

Make your changes, then commit with clear messages:

bash
1git add -A 2git commit -m "$(cat <<'EOF' 3Short description of changes 4 5- Detail 1 6- Detail 2 7EOF 8)"

3. Run CI Checks on Feature Branch

Before merging, run all CI checks on the feature branch:

bash
1# Run all checks (continues even if one fails, so you see all errors) 2pnpm run typecheck lint format test --continue

Or run individually:

bash
1pnpm typecheck # Type checking 2pnpm lint # Linting 3pnpm format # Format checking 4pnpm test # Tests (requires test database)

Fix any issues before proceeding to merge. If tests require the database:

bash
1pnpm reset-test-db 2pnpm test

4. Merge Feature into Dev

Use --no-ff to create a merge commit with two parents:

bash
1git checkout dev 2git merge feat/your-feature-name --no-ff -m "$(cat <<'EOF' 3Short description of changes 4 5- Detail 1 6- Detail 2 7EOF 8)"

5. Bump Version on Dev

Before merging to staging, bump the version:

Files to update:

  • package.json (root)
  • apps/map/package.json
  • apps/api/package.json
  • packages/shared/src/app/changelog.ts
bash
1# After updating files 2git add -A 3git commit -m "Bump to X.Y.Z"

Version bump types:

  • Patch (3.6.1 → 3.6.2): Bug fixes, small improvements
  • Minor (3.6.2 → 3.7.0): New features, larger changes
  • Major (3.7.0 → 4.0.0): Breaking changes

6. Push Dev to Remote

bash
1# Normal push 2git push md dev 3 4# If history was rewritten (rebased/reset) 5git push md dev --force-with-lease

7. Merge Dev into Staging

Use --no-ff with a descriptive message (NOT "Merge branch 'dev'"):

bash
1git checkout staging 2git pull md staging 3git merge dev --no-ff -m "$(cat <<'EOF' 4X.Y.Z: Short description of changes 5 6- Detail 1 7- Detail 2 8EOF 9)"

8. Push Staging to Remote

bash
1# Normal push 2git push md staging 3 4# If history was rewritten 5git push md staging --force-with-lease

9. (Optional) Push to Client Remote

Only when explicitly requested:

bash
1git push f3 dev 2git push f3 staging

Quick Reference

Verify Merge Commit Parents

bash
1# Should show two parent commits 2git log --oneline --graph -5

View Branch Differences

bash
1# What's in dev but not staging 2git log staging..dev --oneline 3 4# What's in staging but not main 5git log main..staging --oneline

Reset Branch to Remote State

bash
1git checkout dev 2git reset --hard md/dev

Agent Instructions

When helping with this workflow:

  1. Run CI checks on feature branch before merging (pnpm run typecheck lint format test --continue)
  2. Always use --no-ff for merges to create merge commits
  3. Never use generic merge messages like "Merge branch 'dev'" - always describe the changes
  4. Bump version on dev before merging to staging
  5. Include version in staging merge message (e.g., "3.6.2: Add feature X")
  6. Push to md remote by default, only push to f3 when asked
  7. Use --force-with-lease instead of --force when force pushing is needed

Example: Complete Feature Merge

bash
1# 1. Create feature branch and make changes 2git checkout dev && git pull md dev 3git checkout -b feat/my-feature 4# ... make changes ... 5git add -A && git commit -m "Add shared errors constants for role management" 6 7# 2. Run CI checks on feature branch 8pnpm run typecheck lint format test --continue 9 10# 3. Merge feature to dev 11git checkout dev 12git merge feat/my-feature --no-ff -m "Add shared errors constants for role management" 13 14# 4. Bump version 15# (edit package.json files and changelog.ts) 16git add -A 17git commit -m "Bump to 3.6.2" 18 19# 5. Push dev 20git push md dev 21 22# 6. Merge dev to staging 23git checkout staging && git pull md staging 24git merge dev --no-ff -m "3.6.2: Add shared errors constants for role management" 25 26# 7. Push staging 27git push md staging

Related Skills

Looking for an alternative to f3-git-workflow or building a Categories.community AI Agent? Explore these related open-source MCP Servers.

View All

widget-generator

Logo of f
f

widget-generator is an open-source AI agent skill for creating widget plugins that are injected into prompt feeds on prompts.chat. It supports two rendering modes: standard prompt widgets using default PromptCard styling and custom render widgets built as full React components.

149.6k
0
Design

chat-sdk

Logo of lobehub
lobehub

chat-sdk is a unified TypeScript SDK for building chat bots across multiple platforms, providing a single interface for deploying bot logic.

73.0k
0
Communication

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication