Python-Project-Template

Stage changes and author a Conventional Commit that drives release-please versioning. Use when the user asks to commit work. Handles branch-name sanity, commit type/scope/subject, and reminds not to hand-edit CHANGELOG or version.

Run the project's full quality gate — pytest, pre-commit (black/ruff/isort/flake8/mypy), interrogate docstring coverage, and optionally the tox matrix — then summarize failures with fixes. Use before committing, before opening a PR, or when the user asks to check code quality.

Bootstrap a freshly cloned copy of this Python template into a working project — set the project name/description, install dependencies, wire pre-commit, install the recommended external skills, and initialize the memory bank. Use right after applying or cloning the template, or whenever pyproject.toml still shows the placeholder name "songshgeo".

Update the shared memory bank (architecture.md / model-design.md / progress.md) after design or progress changes, so the persistent context stays accurate for both Cursor and Claude Code. Use when the codebase structure, data model, or project status has changed, or at the end of a work session.

Idempotently migrate an existing project built from an older version of this template to the new Claude Code workflow — move .cursor/cache into the shared memory-bank, add missing .claude scaffolding (CLAUDE.md, skills, settings, recommended-skills), and optionally install the external skill pack. Use to modernize an old repo without touching already-configured metadata. Safe to run repeatedly.