skills.rest
NimbusPowered
NimbusPoweredOFFICIAL
Explore all skills by this author →
WebsiteGitHub

feature-workflow

Create feature branches from development and prepare pull requests back to it.

3|Updated Mar 27, 2026
Search Tags:#git#release management#feature development#pull requests#GitHub CLI#branch workflow
One-click install
npx skills add https://github.com/NimbusPowered/Nimbus --skill feature-workflow-nimbuspowered
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-workflow
Source: https://github.com/NimbusPowered/Nimbus/tree/main/.claude/skills/feature-workflow
Command: npx skills add https://github.com/NimbusPowered/Nimbus --skill feature-workflow-nimbuspowered

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the overhead and mistakes involved in coordinating a consistent git feature-branch workflow, including creating branches from development, opening PRs back to development, and planning release readiness without confusion.

Core Features & Use Cases

  • Feature branch lifecycle management: Creates feat/*, fix/*, refactor/*, or chore/* branches from development with safe naming conventions and confirmation gates.
  • PR creation to the integration branch: Prepares a PR targeting development, including title/body guidance and duplicate-PR avoidance when possible.
  • Release preparation guidance: Recommends running a version check and outlines high-impact release steps after explicit confirmation.

Use cases: Starting a new feature, fixing a bug in isolation, checking what branches/PRs exist, finishing work by opening a PR to development, and preparing for a release merge to main.

Quick Start

Tell the AI: "Start a new feature branch for scaling improvements in Nimbus, and create the PR to development when the work is done."

Frequently Asked Questions about feature-workflow

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

FAQPage Schema
How do I create a feature branch from the development branch using git?▼

Creating a feature branch from development requires a consistent naming convention like feat/*, fix/*, refactor/*, or chore/*. This workflow confirms the branch name and safely creates it from the development base.

What is the best way to prepare a pull request back to the development branch?▼

Preparing a pull request to development involves structuring the title and body while avoiding duplicates. This workflow guides PR creation targeting the integration branch and checks for existing PRs to prevent conflicts.

Can I manage git feature workflows without the GitHub CLI installed?▼

You can manage git feature workflows without the GitHub CLI by falling back to standard git commands. The workflow safely uses gh CLI for PRs when available but relies on git if the tool is missing.

How does release preparation work when merging development to main?▼

Release preparation from development to main involves running a version check and outlining high-impact release steps. This workflow recommends these steps and executes them only after explicit confirmation to avoid unintended destructive actions.

How do I check the status of existing feature branches and pull requests?▼

Checking feature branch and PR status involves listing current branches and open pull requests targeting development. This workflow automates querying local branches and remote PRs to track integration progress.

Related Skills

Explore More Software Engineering Skills→
aivos-xieaivos-xie
1

github-pr-workflow

Automate the GitHub Pull Request lifecycle from branch creation to merging.

Community
Advanced
intrusive-memoryintrusive-memory
5

ship-swift-library

Automate Swift library releases by merging PRs, bumping versions, and publishing GitHub releases.

Official
Advanced
dikinidikini

bk-verify-completion

Automate pre-completion verification of code quality, test coverage, and traceability.

Community
Intermediate
WesleyMFrederickWesleyMFrederick

merging-feature-branches-to-main

Squashes Git feature-branch history into a single commit when merging to main.

Community
Basic