skills.rest
dburkart
dburkartCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sdlc

Standardize branching, commits, and pull-request workflow for engineering teams.

5|1|Updated Apr 14, 2026
Search Tags:#git#code review#pull request#branching strategy#merge process#ci workflow#commit trailers
One-click install
npx skills add https://github.com/dburkart/auto-engineer --skill sdlc-dburkart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc
Source: https://github.com/dburkart/auto-engineer/tree/main/.claude/skills/sdlc
Command: npx skills add https://github.com/dburkart/auto-engineer --skill sdlc-dburkart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents slow, inconsistent development by defining a clear, repeatable software-delivery workflow for branching, committing, opening PRs, and handling CI/review follow-up so changes reliably move to main.

Core Features & Use Cases

  • Branch and commit conventions: Guides how to branch from up-to-date main and how to structure commit messages with the required Co-Authored-By trailer.
  • PR body and opening procedure: Provides a consistent PR template (Summary + Test plan) and instructs how to create PRs without unnecessary boilerplate.
  • Review and CI follow-up process: Directs how to classify PR review outcomes, hand off to wait-for-pr when polling/auto-fix is needed, and enforce a required self-review workflow before merge.

Quick Start

Use the sdlc skill when you are starting a new cohesive change and need to create a branch, make commits, and open a PR with the correct conventions.

Frequently Asked Questions about sdlc

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

FAQPage Schema
How do I standardize branching and commit conventions for new pull requests?▼

To standardize branching and commits, you branch from an up-to-date main and structure commit messages using required trailers like Co-Authored-By. This ensures consistent history across feature or fix branches before opening a pull request.

What should be included in a pull request template for CI workflows?▼

A pull request template should include a Summary and a Test plan section. This structure provides consistent context for CI workflows and reviewers without adding unnecessary boilerplate to the code review merge process.

How does a self-review cycle work before merging a pull request?▼

A self-review cycle requires retrieving the diff and performing actionable triage before any merge. This enforces required commit trailer rules and ensures all review feedback is addressed before the code reaches main.

How do I handle CI failures and review feedback during a merge process?▼

To handle CI failures and review feedback during the merge process, you classify PR review outcomes and hand off to a polling or auto-fix process. This ensures changes reliably move to main after necessary follow-up.

Does this branching strategy workflow require any specific dependencies or CI tools?▼

No specific dependencies or CI tools are required to use this workflow. It focuses on standardizing the branching strategy, commit trailers, and PR body preparation across any general engineering workflow.

Related Skills

Explore More Software Engineering Skills→
cacr92cacr92
4

auto-merge-and-cleanup

Merge a feature branch into main and clean up branches and worktree.

Community
Advanced
chtughachtugha

review-readiness

Monitor pull request readiness across code review, tests, security, QA, and linting.

Community
Intermediate
fabioc-alohafabioc-aloha

Code Review Skill

Guide systematic code reviews of pull requests using a 3-pass strategy.

Community
Intermediate
JsplixJsplix

code-review-pr-body

Generate structured pull request body drafts from git diffs.

Community
Intermediate