skills.rest
pdylanross
pdylanrossCOMMUNITY
Explore all skills by this author →
GitHub

development-workflow

Defines and enforces a standardized development workflow with branch naming, pull requests, and conventional commits.

1|Updated Jan 21, 2026
Search Tags:#git#workflow#development#pull request#github#branching
One-click install
npx skills add https://github.com/pdylanross/barnacle --skill development-workflow-pdylanross
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: development-workflow
Source: https://github.com/pdylanross/barnacle/tree/main/.claude/skills/development-workflow
Command: npx skills add https://github.com/pdylanross/barnacle --skill development-workflow-pdylanross

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the repository's development workflow, ensuring consistency in branch naming, commit messages, and the pull request process, which reduces confusion and improves code integration.

Core Features & Use Cases

  • Consistent Branching: Enforces clear prefixes for feature, bug, and documentation branches.
  • Standardized PR Process: Outlines the steps from creation to merging, including CI and review.
  • Conventional Commits: Promotes readable and parseable commit history.
  • Use Case: A new developer joins the project and needs to understand how to contribute code. This Skill provides all the necessary guidelines and commands to get started immediately.

Quick Start

Create a new branch for a feature using the command git checkout -b feat/my-new-feature.

Frequently Asked Questions about development-workflow

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

FAQPage Schema
How do I standardize Git branch naming conventions for my repository?▼

Standardizing Git branch naming uses prefixes like feat for features, bug for fixes, and docs for documentation. This keeps branches organized and clarifies their purpose for everyone on the team.

How do I format commit messages using conventional commits?▼

Formatting commit messages using conventional commits involves using structured prefixes to categorize changes. This creates a readable and parseable commit history that is easier to maintain.

What is the best way to structure a pull request process for new developers?▼

The best way to structure a pull request process is to outline steps from creation to merging, including CI checks and reviews. This provides all necessary guidelines for new developers to contribute immediately.

Why does my development workflow need standardized pull request procedures?▼

Your development workflow needs standardized pull request procedures to reduce confusion and improve code integration. Consistent PR steps ensure efficient collaboration across the repository.

Can I use this development workflow for a new software repository?▼

Yes, you can use this development workflow for a new software repository. It defines and enforces clear guidelines for branching, pull requests, and commits to facilitate collaboration from the start.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
AlejocabezaAlejocabeza
1

changelog-automation

Generate Keep a Changelog changelogs from commits, PRs, and releases.

Community
Advanced
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
zach-sourcezach-source

gitflow

Implement GitFlow branching with feature, release, and hotfix workflows.

Community
Intermediate