Releases · nullhack/python-project-template

13 Mar 02:55

nullhack

v1.2.20260312r2

d101f69

v1.2.20260312r2 - Creative Dolphin Latest

Latest

Hotfix release

Fix GitHub Actions context variables being interpreted as Jinja2 template variables
Update template-release to use hybrid calver versioning
Fix cookiecutter.json default version format

Assets 2

12 Mar 10:50

nullhack

v1.0.0

99a68b9

v1.0.0 - Creative Dolphin 🐬

Release v1.0.0 - Creative Dolphin 🐬

AI-Enhanced Development Workflow Template

What's New

This is the first major release of the AI-Enhanced Python Project Template!

AI-Powered Development - OpenCode agents for architecture review, TDD, and repository management
7-Phase Development Cycle - Feature Definition → Prototype → TDD → Signature Design → Architecture Review → Implementation → Quality Assurance
SOLID + Object Calisthenics - Enterprise-grade architecture enforcement
Smart Releases - Hybrid calver versioning with themed release names

Features Added

Developer Agent - Main 7-phase TDD/BDD workflow
Architect Agent - SOLID principles and design review
Repo-Manager Agent - Git operations, PRs, themed releases
10+ Development Skills - feature-definition, prototype-script, tdd-bdd, signature-design, implementation, code-quality, git-release, pr-management
Template Management - Meta agent and skills for managing the template itself
Comprehensive CI - Template validation, generated project tests, Docker builds

Technology Stack

Python 3.13+ with UV package manager
Ruff for linting/formatting
PyTest + Hypothesis for testing
MkDocs for documentation
Docker multi-stage builds

Documentation

Migration

This is the first semantic version release. No breaking changes.

# Generate a new project
cookiecutter gh:nullhack/python-project-template

# Start AI-assisted development
opencode
/init
@developer /skill feature-definition

Assets 2

02 Dec 02:28

nullhack

2025.11.01

bd82ab7

2025.11.01 - modern test

In this release we abandom pytest-bdd in favor of more contemporary approaches, using a combination of:
coverage, hypothesis, cosmic-ray

Behavior test still can be partially used directly in the pytests by using descriptive naming convention and docstring (which will be showed in the pytest report)

Because of the inclusion of dosctrings in pytest report, there's no need for yet another living documentation and this will do just fine as a centralized place for test results