feat: remove revision from versioning, use minor for same-day releases

- New format: v1.5.20260313 (no r1/r2 suffix)
- Same-day releases increment minor: v1.5, v1.6, etc.
- Updated all docs and skills accordingly

Author: AI Developer

.opencode/agents/repo-manager.md

@@ -29,18 +29,18 @@ You are a specialized Git repository management agent for {{cookiecutter.project
 - Maintain clean Git history and follow conventional commit standards
 
 ## Version Format
-Use hybrid versioning: `v{major}.{minor}.{YYYYMMDD}r{revision}`
+Use hybrid versioning: `v{major}.{minor}.{YYYYMMDD}`
 
 **Examples:**
-- `v1.2.20260302r1` - Version 1.2, first release on March 2, 2026
-- `v1.2.20260302r2` - Version 1.2, second release same day
-- `v1.3.20260315r1` - Version 1.3, first release on March 15, 2026
+- `v1.2.20260302` - Version 1.2, release on March 2, 2026
+- `v1.3.20260313` - Version 1.3, release on March 13, 2026
+- `v1.4.20260313` - Version 1.4, second release same day
+- `v2.0.20260401` - Version 2.0, release on April 1, 2026
 
 **Version Rules:**
 - **Major**: Increment for breaking changes
-- **Minor**: Increment for new features  
-- **Date**: Current date YYYYMMDD
-- **Revision**: Daily revision counter (r1, r2, r3...)
+- **Minor**: Increment for new features (or same-day releases)
+- **Date**: Release date YYYYMMDD
 
 ## Release Naming Convention
 Generate themed names using: `{adjective} {animal}`

.opencode/skills/git-release/SKILL.md

@@ -16,32 +16,31 @@ Use this when ready to create a new release after features are complete and test
 ## Hybrid Versioning System
 
 ### Version Format
-`v{major}.{minor}.{YYYYMMDD}r{revision}`
+`v{major}.{minor}.{YYYYMMDD}`
 
 **Components:**
 - **Major**: Breaking changes (e.g., API changes, removed features)
-- **Minor**: New features, significant enhancements  
+- **Minor**: New features, significant enhancements, or same-day releases
 - **Date**: Release date in YYYYMMDD format
-- **Revision**: Daily revision counter (r1, r2, r3...)
 
 **Examples:**
 ```
-v1.0.20260302r1  # Version 1.0, first release on March 2, 2026
-v1.0.20260302r2  # Version 1.0, second release same day (hotfix)
-v1.1.20260315r1  # Version 1.1, first release on March 15, 2026
-v2.0.20260401r1  # Version 2.0, breaking changes on April 1, 2026
+v1.0.20260302  # Version 1.0, release on March 2, 2026
+v1.1.20260315  # Version 1.1, release on March 15, 2026
+v1.2.20260315  # Version 1.2, second release same day
+v2.0.20260401  # Version 2.0, breaking changes on April 1, 2026
 ```
 
 ### Version Bump Rules
 ```bash
 # Feature release (minor bump)
-v1.2.20260302r1 → v1.3.{today}r1
+v1.2.20260302 → v1.3.{today}
 
 # Breaking change (major bump)  
-v1.2.20260302r1 → v2.0.{today}r1
+v1.2.20260302 → v2.0.{today}
 
-# Same day hotfix (revision bump)
-v1.2.20260302r1 → v1.2.20260302r2
+# Same day release (increment minor by 2)
+v1.2.20260302 → v1.3.20260302
 ```
 
 ## Release Naming Strategy

.opencode/skills/template-release/SKILL.md

@@ -16,20 +16,19 @@ Use this when ready to release a new version of the cookiecutter template after
 ## Template Versioning Strategy
 
 ### Hybrid Calver Versioning for Template
-Use hybrid versioning: `v{major}.{minor}.{YYYYMMDD}r{revision}`
+Use hybrid versioning: `v{major}.{minor}.{YYYYMMDD}`
 
 **Version Bump Guidelines:**
-- **Major (v2.x.xxxxr1)**: Breaking changes to cookiecutter variables, major workflow changes, removed features
-- **Minor (v1.x.xxxxr1)**: New agents, new skills, workflow enhancements, new features
-- **Revision (v1.2.xxxxr2)**: Bug fixes, documentation updates, minor improvements on same day
+- **Major (v2.x.20260401)**: Breaking changes to cookiecutter variables, major workflow changes, removed features
+- **Minor (v1.x.20260315)**: New agents, new skills, workflow enhancements, new features, or same-day releases
 
 **Examples:**
 ```
-v1.0.20260302r1  # Initial release on March 2, 2026
-v1.1.20260315r1  # Added repo-manager agent and git-release skill on March 15
-v1.1.20260315r2  # Fixed bug in template generation same day
-v1.2.20260320r1  # Added template-manager meta agent on March 20
-v2.0.20260401r1  # Changed cookiecutter.json structure (breaking) on April 1
+v1.0.20260302  # Initial release on March 2, 2026
+v1.1.20260315  # Added repo-manager agent and git-release skill on March 15
+v1.2.20260315  # Second release same day (increment minor)
+v1.3.20260320  # Added template-manager meta agent on March 20
+v2.0.20260401  # Changed cookiecutter.json structure (breaking) on April 1
 ```
 
 ## Release Process Workflow
@@ -56,54 +55,31 @@ fi
 ### Phase 2: Version Calculation and Update
 ```bash
 # Get current version from git tags
-current_version=$(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.00000000r0")
-echo "Current version: $current_version"
+current_version=$(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.00000000")
 
-# Determine next version based on changes
-echo "Analyzing changes since last release..."
-git log ${current_version}..HEAD --oneline
-
-# Version bump logic (manual decision)
-echo "Select version bump type:"
-echo "1. Revision (bug fixes, docs - same day)"
-echo "2. Minor (new features, agents, skills)"
-echo "3. Major (breaking changes)"
-
-# For automation, analyze commit messages
-breaking_changes=$(git log ${current_version}..HEAD --grep="BREAKING CHANGE" --oneline | wc -l)
-new_features=$(git log ${current_version}..HEAD --grep="feat:" --oneline | wc -l)
-bug_fixes=$(git log ${current_version}..HEAD --grep="fix:" --oneline | wc -l)
-
-# Get current date for calver
+# Calculate new version
 current_date=$(date +%Y%m%d)
-
-if [ "$breaking_changes" -gt 0 ]; then
-    bump_type="major"
-elif [ "$new_features" -gt 0 ]; then
-    bump_type="minor"
-else
-    bump_type="revision"
-fi
-
-# Extract current version components
 current_major=$(echo $current_version | sed 's/v\([0-9]\+\)\..*/\1/')
 current_minor=$(echo $current_version | sed 's/v[0-9]\+\.\([0-9]\+\).*/\1/')
 current_date_in_tag=$(echo $current_version | sed 's/v[0-9]\+\.[0-9]\+\.\([0-9]\{8\}\).*/\1/')
-current_revision=$(echo $current_version | sed 's/.*r\([0-9]\+\)/\1/')
 
-# Calculate new version
 case $bump_type in
     "major")
-        new_version=$(echo "v$((current_major + 1)).0.${current_date}r1")
+        new_version=$(echo "v$((current_major + 1)).0.${current_date}")
         ;;
     "minor")
-        new_version=$(echo "v${current_major}.$((current_minor + 1)).${current_date}r1")
+        # If same day as last release, increment minor further
+        if [ "$current_date_in_tag" = "$current_date" ]; then
+            new_version=$(echo "v${current_major}.$((current_minor + 2)).${current_date}")
+        else
+            new_version=$(echo "v${current_major}.$((current_minor + 1)).${current_date}")
+        fi
         ;;
     "revision")
         if [ "$current_date_in_tag" = "$current_date" ]; then
-            new_version=$(echo "v${current_major}.${current_minor}.${current_date}r$((current_revision + 1))")
+            new_version=$(echo "v${current_major}.$((current_minor + 1)).${current_date}")
         else
-            new_version=$(echo "v${current_major}.${current_minor}.${current_date}r1")
+            new_version=$(echo "v${current_major}.${current_minor}.${current_date}")
         fi
         ;;
 esac
@@ -353,7 +329,7 @@ EOF
 git add .
 git commit -m "feat(agents): add template-manager meta agent"
 @template-manager /skill template-release
-# Output: "Created release v1.2.20260320r1 with new meta agent functionality"
+# Output: "Created release v1.2.20260320 with new meta agent functionality"
 ```
 
 ### Patch Release  
@@ -362,7 +338,7 @@ git commit -m "feat(agents): add template-manager meta agent"
 git add .
 git commit -m "fix(docs): correct cookiecutter variable examples"
 @template-manager /skill template-release
-# Output: "Created release v1.2.20260320r2 with documentation fixes"
+# Output: "Created release v1.2.20260320 with documentation fixes"
 ```
 
 ### Major Release
@@ -373,5 +349,5 @@ git commit -m "feat!: restructure cookiecutter variables for better usability
 
 BREAKING CHANGE: cookiecutter.json format changed"
 @template-manager /skill template-release
-# Output: "Created release v2.0.20260401r1 with breaking changes - migration guide included"
+# Output: "Created release v2.0.20260401 with breaking changes - migration guide included"
 ```

AGENTS.md

@@ -67,7 +67,7 @@ When developers use this template, they get:
 7. **Quality Assurance** → Comprehensive quality checks
 
 ### Repository Management
-- Hybrid versioning: `v1.2.20260302r1` (major.minor.calver)
+- Hybrid versioning: `v1.2.20260302` (major.minor.calver)
 - Themed releases: "swift cheetah", "vigilant owl", "creative fox"
 - Automated PR workflows with conventional commits
 - GitHub CLI integration
@@ -88,7 +88,7 @@ When developers use this template, they get:
 cookiecutter gh:your-username/python-project-template
 
 # Or use a specific version
-cookiecutter gh:your-username/python-project-template --checkout v1.2.20260312r1
+cookiecutter gh:your-username/python-project-template --checkout v1.2.20260312
 ```
 
 ### Template Development Workflow
@@ -108,14 +108,15 @@ cookiecutter gh:your-username/python-project-template --checkout v1.2.20260312r1
 ## Template Versioning
 
 ### Hybrid Calver Versioning for Template
-- **Major (v2.x.xxxxr1)**: Breaking changes to cookiecutter variables
-- **Minor (v1.x.xxxxr1)**: New agents, skills, workflow features
-- **Revision (v1.2.xxxxr2)**: Bug fixes, documentation updates
+- **Major (v2.x.20260401)**: Breaking changes to cookiecutter variables
+- **Minor (v1.x.20260315)**: New agents, skills, workflow features, or same-day releases
 
 ### Recent Releases
-- **v1.0.20260312r1**: Initial release with development workflow
-- **v1.1.20260312r1**: Added repository management agent
-- **v1.2.20260312r1**: Added meta template management system
+- **v1.0.20260312**: Initial release with development workflow
+- **v1.1.20260312**: Added repository management agent
+- **v1.2.20260312**: Added meta template management system
+- **v1.3.20260313**: Added session-workflow skill
+- **v1.4.20260313**: Added AI-driven themed naming
 
 ## Generated Project Features
 

CHANGELOG.md

@@ -24,7 +24,7 @@ All notable changes to this template will be documented in this file.
 - **7-Phase Development Cycle**: Feature Definition → Prototype → TDD → Signature Design → Architecture Review → Implementation → Quality Assurance
 - **SOLID Principles Enforcement** - Single responsibility, dependency inversion, interface segregation
 - **Object Calisthenics** - No primitives, small classes, behavior-rich objects
-- **Hybrid Calver Versioning**: v1.2.20260302r1 format with themed releases
+- **Hybrid Calver Versioning**: v1.2.20260302 format with themed releases
 - **Themed Release Names**: "Swift Cheetah", "Vigilant Owl", "Creative Fox" based on PR sentiment
 - **Property-Based Testing**: Hypothesis integration for robust test coverage
 

README.md

@@ -16,7 +16,7 @@ Modern cookiecutter template delivering enterprise-grade Python projects with **
 🏗️ **SOLID Architecture** - Object calisthenics, dependency inversion, and protocol-based design  
 ⚡ **Zero-Config Setup** - UV package manager, Ruff formatting, PyTest + Hypothesis testing  
 🎯 **Quality Enforced** - 100% coverage, static typing, property-based testing  
-🔄 **Smart Releases** - Calver versioning with themed releases (`v1.2.20240315r1 "Swift Cheetah"`)  
+🔄 **Smart Releases** - Calver versioning with themed releases (`v1.2.20260315 "Swift Cheetah"`)  
 📋 **Complete Workflows** - 7-phase development cycle from prototype to production
 
 ## 🎯 Perfect For

cookiecutter.json

@@ -9,6 +9,6 @@
   "project_short_description": "Python template with some awesome tools to quickstart any Python project",
   "minimum_coverage": 100,
   "include_examples": "true",
-  "version": "0.1.20260312r1",
+  "version": "0.1.20260312",
   "license": ["MIT", "BSD_3_Clause", "Apache_2.0", "GPL_3.0", "Proprietary"]
 }

{{cookiecutter.project_slug}}/.opencode/agents/repo-manager.md

@@ -29,18 +29,18 @@ You are a specialized Git repository management agent for {{cookiecutter.project
 - Maintain clean Git history and follow conventional commit standards
 
 ## Version Format
-Use hybrid versioning: `v{major}.{minor}.{YYYYMMDD}r{revision}`
+Use hybrid versioning: `v{major}.{minor}.{YYYYMMDD}`
 
 **Examples:**
-- `v1.2.20260302r1` - Version 1.2, first release on March 2, 2026
-- `v1.2.20260302r2` - Version 1.2, second release same day
-- `v1.3.20260315r1` - Version 1.3, first release on March 15, 2026
+- `v1.2.20260302` - Version 1.2, release on March 2, 2026
+- `v1.3.20260313` - Version 1.3, release on March 13, 2026
+- `v1.4.20260313` - Version 1.4, second release same day
+- `v2.0.20260401` - Version 2.0, release on April 1, 2026
 
 **Version Rules:**
 - **Major**: Increment for breaking changes
-- **Minor**: Increment for new features  
-- **Date**: Current date YYYYMMDD
-- **Revision**: Daily revision counter (r1, r2, r3...)
+- **Minor**: Increment for new features (or same-day releases)
+- **Date**: Release date YYYYMMDD
 
 ## Release Naming Convention
 Generate themed names using: `{adjective} {animal}`

{{cookiecutter.project_slug}}/.opencode/skills/git-release/SKILL.md

@@ -16,32 +16,31 @@ Use this when ready to create a new release after features are complete and test
 ## Hybrid Versioning System
 
 ### Version Format
-`v{major}.{minor}.{YYYYMMDD}r{revision}`
+`v{major}.{minor}.{YYYYMMDD}`
 
 **Components:**
 - **Major**: Breaking changes (e.g., API changes, removed features)
-- **Minor**: New features, significant enhancements  
+- **Minor**: New features, significant enhancements, or same-day releases
 - **Date**: Release date in YYYYMMDD format
-- **Revision**: Daily revision counter (r1, r2, r3...)
 
 **Examples:**
 ```
-v1.0.20260302r1  # Version 1.0, first release on March 2, 2026
-v1.0.20260302r2  # Version 1.0, second release same day (hotfix)
-v1.1.20260315r1  # Version 1.1, first release on March 15, 2026
-v2.0.20260401r1  # Version 2.0, breaking changes on April 1, 2026
+v1.0.20260302  # Version 1.0, release on March 2, 2026
+v1.1.20260315  # Version 1.1, release on March 15, 2026
+v1.2.20260315  # Version 1.2, second release same day
+v2.0.20260401  # Version 2.0, breaking changes on April 1, 2026
 ```
 
 ### Version Bump Rules
 ```bash
 # Feature release (minor bump)
-v1.2.20260302r1 → v1.3.{today}r1
+v1.2.20260302 → v1.3.{today}
 
 # Breaking change (major bump)  
-v1.2.20260302r1 → v2.0.{today}r1
+v1.2.20260302 → v2.0.{today}
 
-# Same day hotfix (revision bump)
-v1.2.20260302r1 → v1.2.20260302r2
+# Same day release (increment minor by 2)
+v1.2.20260302 → v1.3.20260302
 ```
 
 ## Release Naming Strategy

{{cookiecutter.project_slug}}/AGENTS.md

@@ -109,12 +109,12 @@ task doc-serve
 
 ## Release Management
 
-This project uses a hybrid versioning system: `v{major}.{minor}.{YYYYMMDD}r{revision}`
+This project uses a hybrid versioning system: `v{major}.{minor}.{YYYYMMDD}`
 
 ### Version Examples
-- `v1.2.20260302r1` - Version 1.2, first release on March 2, 2026
-- `v1.2.20260302r2` - Version 1.2, second release same day (hotfix)
-- `v1.3.20260315r1` - Version 1.3, first release on March 15, 2026
+- `v1.2.20260302` - Version 1.2, release on March 2, 2026
+- `v1.3.20260313` - Version 1.3, release on March 13, 2026
+- `v1.4.20260313` - Version 1.4, second release same day (increment minor)
 
 ### Release Naming
 Releases use adjective-animal themes based on PR sentiment analysis: