GitHub Workflow Adaptation Plan banner
alirezarezvani alirezarezvani

GitHub Workflow Adaptation Plan

Git community intermediate

Description

**Project**: Claude Code Skills Factory **Blueprint Source**: `/Users/rezarezvani/projects/claudecode-github-bluprint` **Date**: November 12, 2025 **Status**: Planning Phase ---

Installation

Terminal
claude install-skill https://github.com/alirezarezvani/claude-code-skill-factory

README

GitHub Workflow Adaptation Plan

**Project**: Claude Code Skills Factory **Blueprint Source**: `/Users/rezarezvani/projects/claudecode-github-bluprint` **Date**: November 12, 2025 **Status**: Planning Phase


🎯 Objective

Adapt the GitHub workflow blueprint to create an automated, Claude Code-integrated branching and PR workflow for the Skills Factory repository that:

    undefined

📊 Current State vs. Desired State

Current Workflow Problems

Issue Impact Example
No branch naming convention Inconsistent branches fix/psychology-advisor-link (unclear)
Direct pushes to main Bypasses review process Recent commits went straight to main
No automated branch creation Manual git commands needed Developer creates branches manually
No PR automation Manual PR creation and cleanup No auto-merge, no auto-delete
No Claude Code review integration Missing automated reviews Reviews done manually
Manual branch management Forgot to switch back to dev Stayed on feature branch

Desired Workflow (Blueprint-Based)

1. Create GitHub Issue
   ↓
2. Label with 'claude-code' + 'status:ready'
   ↓
3. **AUTO**: Branch created (feature/issue-123-clear-name)
   ↓
4. Developer works on branch
   ↓
5. /commit-smart (quality checks + secrets scan)
   ↓
6. /create-pr (auto-links issue, adds labels)
   ↓
7. **AUTO**: PR validation (branch name, title, quality gates)
   ↓
8. Tag @claude for review
   ↓
9. **AUTO**: Claude Code review posted
   ↓
10. After approval → **AUTO**: Merge to dev
   ↓
11. **AUTO**: Delete source branch
   ↓
12. **AUTO**: Switch to dev branch
   ↓
13. Ready for next task

🏗️ Blueprint Patterns to Adopt

Pattern 1: Branch Naming Convention

**From Blueprint**: `{type}/issue-{number}-{slug}`

**Types**:

    undefined

**Example**:

Issue #42: "Add AWS Solution Architect Skill"
Branch: feature/issue-42-add-aws-solution-architect-skill

**Enforcement**:

    undefined

Pattern 2: Branching Strategy

**Blueprint Strategy**: `feature → dev → main`

**Rules**:

    undefined

**Cur