Merge feature/git-flow-convention into main

v1.0.1: Git Flow Convention for skills, Forgejo→GitHub mirror workflow

Author: André Lange

.forgejo/workflows/mirror.yml

@@ -0,0 +1,18 @@
+name: Mirror to GitHub
+on:
+  push:
+    branches: [main]
+
+jobs:
+  mirror:
+    runs-on: docker
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Push to GitHub (public mirror)
+        env:
+          GH_TOKEN: ${{ secrets.GH_MIRROR_TOKEN }}
+        run: |
+          git remote add github-mirror https://x-access-token:${GH_TOKEN}@github.com/LangeVC/skillweave.git
+          git push github-mirror main --tags

CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 1.0.1
+
+- **FEATURE**: Git Flow Convention — skills enforce minimum branching discipline (feature/fix/chore branches, dev → main merge path, preflight detection)
+- **FEATURE**: Forgejo → GitHub mirror workflow (`.forgejo/workflows/mirror.yml`) — auto-push to GitHub on main push
+- **IMPROVEMENT**: promptchain-execute Preflight Phase 1 now includes git flow state evaluation (Step 7)
+- **IMPROVEMENT**: releasechain Pipeline Stage 5 expanded with branch model, merge flow enforcement, and config schema
+- **IMPROVEMENT**: launch Pre-Launch-Checklist includes git flow check (dev → main merge path verified)
+- **IMPROVEMENT**: Skill SKILL.md files synced between user-level and repo-level copies
+
 ## 1.0.0 — Forever Free
 - **RELEASE**: SkillWeave v1.0.0 "Forever Free" — production-stable AI skill orchestration
 - **FEATURE**: 5-level test pyramid (Lint → Unit → E2E Smoke → Acceptance → Evidence/Groundedness) with 3-state gate (PROMOTE/HOLD/ROLLBACK)

README.md

@@ -1,7 +1,7 @@
 # SkillWeave
 
 [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
-[![Version](https://img.shields.io/badge/version-1.0.0-blue)](https://github.com/LangeVC/skillweave/releases/tag/v1.0.0)
+[![Version](https://img.shields.io/badge/version-1.0.1-blue)](https://github.com/LangeVC/skillweave/releases/tag/v1.0.1)
 [![Python](https://img.shields.io/badge/python-3.9+-blue.svg)](https://www.python.org/)
 [![Skills](https://img.shields.io/badge/skills-13-blue)](skills/)
 [![Status](https://img.shields.io/badge/status-production--stable-green)](https://github.com/LangeVC/skillweave)

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "skillweave"
-version = "1.0.0"
+version = "1.0.1"
 description = "Multi-agent AI skill orchestration with Next Level features"
 readme = "README.md"
 authors = [

skills/skillweave-launch/SKILL.md

@@ -13,6 +13,9 @@ Bei Fehlschlag wird das Deployment blockiert.
 
 - [ ] Alle Tests grün (CI-Pipeline)
 - [ ] CHANGELOG.md aktualisiert und versioniert
+- [ ] README.md aktualisiert (Version-Badge, Features, Getting Started)
+- [ ] Release-Naming-Convention: exakt `SkillWeave vX.Y.Z` — kein zusätzlicher Text im Titel (Beschreibungstext gehört in die Release Notes Body). Regex: `^SkillWeave v[0-9]+\.[0-9]+\.[0-9]+$`. Bei Verstoß: Release blockieren.
+- [ ] Git-Flow-Check: Release-Branch wurde über `dev` → `main` gemerged (kein direkter Feature-Branch → `main` Merge). Falls `dev` nicht existiert: Warnung ausgeben und empfehlen.
 - [ ] Release-Tag existiert (git tag vX.Y.Z)
 - [ ] Secrets/ENVs in Ziel-Umgebung gesetzt
 - [ ] Maintenance-Mode konfiguriert (Production)

skills/skillweave-promptchain-execute/SKILL.md

@@ -300,6 +300,74 @@ elif result["action"] == "switch_skill":
 Always use intelligent guidance when executing this skill to provide the best 
 user experience and ensure successful outcomes.
 
+## Git Flow Convention
+
+When executing `build` or `mixed` sequences in a git repository, SkillWeave enforces a minimum branching discipline. This prevents work from landing directly on protected branches and ensures a reviewable integration path.
+
+### Branch Model
+
+| Branch | Purpose | Protected |
+|--------|---------|-----------|
+| `main` | Release-ready, tagged with `vX.Y.Z` | Yes — no direct commits |
+| `dev` | Integration branch, CI must be green | Yes — only via PR |
+| `feature/<id>-<slug>` | New functionality, branched from `dev` | No |
+| `fix/<id>-<slug>` | Bug fixes, branched from `dev` | No |
+| `chore/<slug>` | Maintenance, docs, CI changes | No |
+
+### Preflight Detection (before any build work)
+
+Before creating a branch or committing, check the repository state:
+
+1. **Does `dev` exist?** If not, recommend creating it from `main` and explain why.
+2. **Is the current branch `main`?** Warn the user and recommend branching to `dev` or a feature branch. Never commit build work directly to `main`.
+3. **Is there an existing branch for this task?** Search for open branches matching the task ID or slug. If found, offer to continue on that branch instead of creating a new one.
+4. **Is `dev` up to date with `main`?** If `dev` is behind `main`, recommend rebasing or merging `main` into `dev` before branching.
+
+If the user explicitly opts out (e.g., single-branch workflow), respect their choice but log the decision in `.skillweave/tracking-log/`.
+
+### Branch Creation
+
+When starting build work:
+
+1. Determine branch type from the task/PRD context:
+   - PRD tasks with new features → `feature/<ticket-id>-<slug>`
+   - Bug fixes or patches → `fix/<ticket-id>-<slug>`
+   - Maintenance, docs, CI → `chore/<slug>`
+2. Branch from `dev` (not from `main`)
+3. Log the branch name in `.skillweave/tracking-log/` for continuity across sessions
+
+### Merge Flow
+
+The expected merge path for build work:
+
+```
+feature/FEAT-001-auth  →  PR to dev  →  PR to main  →  tag vX.Y.Z
+```
+
+- **Feature branch → `dev`**: Created by `promptchain-execute` or `releasechain` after build gates pass. Requires tests green.
+- **`dev` → `main`**: Created by `releasechain` as the release PR. Requires all integration tests green, changelog updated, version bumped.
+- **Tag on `main`**: Created by `releasechain` or `launch` after merge to `main`.
+
+### Configuration
+
+The git flow can be configured in `.skillweave/config.yaml`:
+
+```yaml
+git_flow:
+  enabled: true
+  branches:
+    production: main
+    integration: dev
+  branch_prefix:
+    feature: feature/
+    fix: fix/
+    chore: chore/
+  require_pr: true
+  auto_create_dev: false
+```
+
+If `git_flow.enabled` is `false` or missing, skip branch enforcement but still warn when committing directly to `main`.
+
 ## Execution Process
 
 ### Phase 1: Preflight
@@ -311,10 +379,14 @@ user experience and ensure successful outcomes.
    - critical path
    - safe parallel lanes
    - review gates
-    - handoff boundary to releasechain/launch (see `.skillweave/release/skill-boundaries.yaml`)
+   - handoff boundary to releasechain/launch (see `.skillweave/release/skill-boundaries.yaml`)
 5. Resolve execution mode
 6. Resolve effective risk mode using hierarchical override system (CLI parameter > environment variable > project config > global config > default)
-7. Determine whether the sequence should run:
+7. **Evaluate git flow state** (see Git Flow Convention above):
+   - Detect branch model (`dev` exists? current branch? open feature branches?)
+   - Create or switch to appropriate work branch
+   - Warn if working directly on `main` or `dev`
+8. Determine whether the sequence should run:
    - as one batch
    - as multiple batches
    - with sidecar subagents

skills/skillweave-releasechain/SKILL.md

@@ -260,14 +260,11 @@ Adjust your pipeline execution based on enabled features to provide enhanced res
    - Multi-agent routing based on capabilities
    - Automatic retry with learning
 
-4. **Verification Feedback Loops (Testing Integration)**
-   - Multi-level verification via `/skillweave test` (5-level pyramid)
-   - **Verify step**: Runs Lint (L1) + Unit (L2) after code generation
-   - **Review Gate**: Runs E2E Smoke (L3) + Acceptance (L4) before release
-   - 3-state gate: PROMOTE (advance) / HOLD (suggest fix) / ROLLBACK (block)
-   - Results stored in `.skillweave/testing/results/yyyy-mm-dd-run-N.json`
-   - Gate decision drives Ralph Loop state transition (Fix/Retry vs Integrate)
-   - See `skills/skillweave-lifecycle/references/testing-flow.md` for full spec
+4. **Verification Feedback Loops**
+   - Multi-level verification (code, functional, system, business)
+   - Automated testing integration
+   - Quality gates before task completion
+   - Continuous improvement from failures
 
 ### Agent-Agnostic Execution
 
@@ -366,14 +363,54 @@ For simple tasks (1-3 tasks, <60 minutes), ReleaseChain uses a streamlined workf
    - **System Level**: E2E tests, performance tests
    - **Business Level**: Acceptance criteria validation
 
-5. **Version Control Integration**
+5. **Version Control Integration — Git Flow**
    - Atomic commits per successful task
    - Descriptive commit messages
-   - Branch management for features
    - Tag creation for milestones
+   - **Git Flow enforcement** (see below)
+
+   **Branch Model:**
+   | Branch | Purpose | Protected |
+   |--------|---------|-----------|
+   | `main` | Release-ready, tagged with `vX.Y.Z` | Yes — no direct commits |
+   | `dev` | Integration branch, CI must be green | Yes — only via PR |
+   | `feature/<id>-<slug>` | New functionality, branched from `dev` | No |
+   | `fix/<id>-<slug>` | Bug fixes, branched from `dev` | No |
+   | `chore/<slug>` | Maintenance, docs, CI changes | No |
+
+   **Preflight checks before any commit:**
+   1. Does `dev` exist? If not, recommend creating it from `main`.
+   2. Is the current branch `main`? Warn and recommend branching.
+   3. Is there an existing branch for this task? Offer to continue on it.
+   4. Is `dev` up to date with `main`? Recommend rebase/merge if behind.
+
+   **Merge flow (enforced by releasechain):**
+   ```
+   feature/FEAT-001-auth  →  PR to dev  →  PR to main  →  tag vX.Y.Z
+   ```
+   - Feature branch → `dev`: After build gates pass, tests green. Create PR.
+   - `dev` → `main`: Release PR. Requires integration tests, changelog, version bump.
+   - Tag on `main`: After merge, created by releasechain or launch skill.
+
+   **Configuration** in `.skillweave/config.yaml`:
+   ```yaml
+   git_flow:
+     enabled: true
+     branches:
+       production: main
+       integration: dev
+     branch_prefix:
+       feature: feature/
+       fix: fix/
+       chore: chore/
+     require_pr: true
+     auto_create_dev: false
+   ```
+
+   If `git_flow.enabled` is `false` or missing, skip enforcement but still warn on direct `main` commits.
 
 6. **Collaboration & Review**
-   - Automated PR creation
+   - Automated PR creation (feature → `dev`, then `dev` → `main` for releases)
    - Code review facilitation
    - Change documentation
    - Stakeholder notification
@@ -383,6 +420,8 @@ For simple tasks (1-3 tasks, <60 minutes), ReleaseChain uses a streamlined workf
    - Changelog generation
    - Release note creation
    - Asset packaging
+   - **Release naming convention (enforced)**: Title must be exactly `SkillWeave vX.Y.Z` — no additional text. Regex: `^SkillWeave v[0-9]+\.[0-9]+\.[0-9]+$`. Descriptive text goes into release notes body only. Block release creation if convention is violated.
+   - **Release merge path (enforced)**: Release PRs merge `dev` → `main`, never feature branches directly to `main`. Tag `vX.Y.Z` is created on `main` after merge.
 
 8. **Deployment Readiness**
    - Build artifact creation