القائمة
Create a release for this repository by tagging main with calendar versioning (optionally using git-flow if configured); use when the user asks to create a release or bump version.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Guides the FastAPI Presentation layer in a Python DDD + Onion Architecture app (route handler structure, Pydantic request/response schemas, mapping Domain exceptions to HTTP errors, and OpenAPI error documentation), based on the dddpy reference. Use when adding/refactoring endpoints that call UseCases and convert primitives ↔ Value Objects/Entities.
Guides FastAPI backend design using Domain-Driven Design (DDD) and Onion Architecture in Python. Use when structuring a FastAPI app (routes/handlers, Pydantic schemas, Depends-based DI), modeling domain Entities/Value Objects, defining repository interfaces, implementing SQLAlchemy infrastructure adapters, or writing use cases, based on the dddpy reference.
Guides unit testing for Python DDD + Onion Architecture apps (Domain Entities/Value Objects and UseCases) using pytest and repository mocks, based on the dddpy reference. Use when adding tests, choosing what to mock, or structuring test folders for a DDD FastAPI project.
Guides project tooling for a Python FastAPI + SQLAlchemy DDD/Onion Architecture codebase: uv-based environment setup, Makefile workflows, ruff formatting/linting, mypy typing, pytest, and CI (GitHub Actions), based on the dddpy reference. Use when bootstrapping a repo or tightening developer experience and quality gates.
Prepare and create git commits in this repository using Conventional Commits; use when the user asks to commit or split commits for a task.
| name | git-flow-release |
| description | Create a release for this repository by tagging main with calendar versioning (optionally using git-flow if configured); use when the user asks to create a release or bump version. |
Before starting the release process, verify:
git status should show a clean working tree).main unless the user specifies otherwise).This repository does not have mandatory lint/test commands; do not run Node/bun/turbo checks here.
Use calendar-based versioning with v prefix for git tags:
vYYYY.MM.DD.N (e.g., v2026.02.04.1)Components:
Determine today's date in YYYY.MM.DD:
today=$(date +%Y.%m.%d)
Check existing tags for today:
git tag --list "v${today}.*"
Choose the next N:
N=1 → vYYYY.MM.DD.1vYYYY.MM.DD.1), increment N (e.g., vYYYY.MM.DD.2)Execute the following steps in order:
Determine version
YYYY.MM.DD.N and prepare short release notes (bullet list)Commit changes (if needed)
git add -A
git commit -m "chore: prepare release vYYYY.MM.DD.N"
Create annotated tag
git tag -a vYYYY.MM.DD.N -m "Release vYYYY.MM.DD.N"
Push main with tags
git push origin main --tags
(Optional) Create a GitHub Release
If gh is available and the user requests it:
gh release create vYYYY.MM.DD.N --generate-notes
Only use this section if git-flow is configured for the repository (a develop branch exists and git flow init has been run).
Start release
git flow release start YYYY.MM.DD.N
Finish release (macOS/BSD safe path)
Always finish without tagging and add the tag manually (avoids getopt errors with -m).
git flow release finish -n YYYY.MM.DD.N
git switch main
git tag -a vYYYY.MM.DD.N -m "Release vYYYY.MM.DD.N"
Push branches and tags
git push origin develop
git push origin main --tags
After completing all steps, report:
2026.02.04.1)v2026.02.04.1)git flow is not installed, inform the user and suggest installing it.git flow release finish, stop and report the conflict details.