diff --git a/docs/development/git-workflow.md b/docs/development/git-workflow.md
new file mode 100644
index 00000000..e39b600d
--- /dev/null
+++ b/docs/development/git-workflow.md
@@ -0,0 +1,130 @@
+# Git Workflow
+
+This pages shows the recommended Git workflow to keep the local repository clean and organized while ensuring smooth collaboration among team members.
+
+## Prerequisites
+
+Make sure you have [Git](https://git-scm.com/) (version 2.23 and above) installed and properly configured especially for authentication.
+
+## Fork and clone the repository
+
+Fork the repository to your own namespace, and let us take `https://github.com/<username>/ss-python` as example.
+
+Clone the repository and navigate to the root directory:
+
+```shell
+git clone git@github.com:<username>/ss-python.git
+cd ss-python
+```
+
+## Configure the remote
+
+Add and update the `upstream` remote repository:
+
+```shell
+git remote add upstream https://github.com/serious-scaffold/ss-python
+git fetch upstream
+```
+
+Configure `git` to pull `main` branch from the `upstream` remote:
+
+```shell
+git config --local branch.main.remote upstream
+```
+
+Configure `git` never to push to the `upstream` remote:
+
+```shell
+git remote set-url --push upstream git@github.com/<username>/ss-python.git
+```
+
+## Verify the remote configuration
+
+List the remote repositories with urls:
+
+```shell
+git remote -v
+```
+
+You should have two remote repositories: `origin` to your forked CPython repository, and `upstream` pointing to the official CPython repository:
+
+```shell
+origin  git@github.com:<username>/ss-python.git (fetch)
+origin  git@github.com:<username>/ss-python.git (push)
+upstream        https://github.com/serious-scaffold/ss-python (fetch)
+upstream        git@github.com:<username>/ss-python.git (push)
+```
+
+Note that the push url of `upstream` repository is the forked repository.
+
+Show the upstream for `main` branch:
+
+```shell
+git config branch.main.remote
+```
+
+You should see `upstream` here.
+
+## Work on a feature branch
+
+Create and switch to a new branch from `main`:
+
+```shell
+git switch -c <branch-name> main
+```
+
+Stage the changed files:
+
+```shell
+git add -p # to review and add changes to existing files
+git add <filename1> <filename2> # to add new files
+```
+
+Commit the staged files:
+
+```shell
+git commit -m "the commit message"
+```
+
+Push the committed changes:
+
+```shell
+git push
+```
+
+## Create a pull request
+
+Navigate to the hosting platform and create a pull request.
+
+After the pull request is merged, you need to delete the branch in your namespace.
+
+```{note}
+It is recommended to configure the automatic deletion of the merged branches.
+```
+
+## Housekeeping the cloned repository
+
+Update the `main` branch from upstream:
+
+```shell
+git switch main
+git pull upstream main
+```
+
+Remove deleted remote-tracking references:
+
+```shell
+git fetch --prune origin
+```
+
+Remove local branches:
+
+```shell
+git branch -D <branch-name>
+```
+
+After all these operations, you should be ready to <project:#work-on-a-feature-branch> again.
+
+## Reference
+
+- [Git bootcamp and cheat sheet, Python Developer's Guide](https://devguide.python.org/getting-started/git-boot-camp/)
diff --git a/docs/development/index.md b/docs/development/index.md
index 24b46c53..03fc20fb 100644
--- a/docs/development/index.md
+++ b/docs/development/index.md
@@ -3,6 +3,7 @@
 This section is designed for developers and covers essential topics during daily development lifecycle. Follow these guidelines to ensure all contributors adhere to best practices, maintain code quality, and collaborate efficiently.
 
 ```{toctree}
+git-workflow
 setup-dev-env
 cleanup-dev-env
 commit
diff --git a/template/docs/development/git-workflow.md.jinja b/template/docs/development/git-workflow.md.jinja
new file mode 100644
index 00000000..b509b581
--- /dev/null
+++ b/template/docs/development/git-workflow.md.jinja
@@ -0,0 +1,131 @@
+[% from pathjoin("includes", "variable.jinja") import repo_url with context -%]
+# Git Workflow
+
+This pages shows the recommended Git workflow to keep the local repository clean and organized while ensuring smooth collaboration among team members.
+
+## Prerequisites
+
+Make sure you have [Git](https://git-scm.com/) (version 2.23 and above) installed and properly configured especially for authentication.
+
+## Fork and clone the repository
+
+Fork the repository to your own namespace, and let us take `https://{{ repo_host }}/<username>/{{ repo_name }}` as example.
+
+Clone the repository and navigate to the root directory:
+
+```shell
+git clone git@{{ repo_host }}:<username>/{{ repo_name }}.git
+cd {{ repo_name }}
+```
+
+## Configure the remote
+
+Add and update the `upstream` remote repository:
+
+```shell
+git remote add upstream https://{{ repo_url() }}
+git fetch upstream
+```
+
+Configure `git` to pull `main` branch from the `upstream` remote:
+
+```shell
+git config --local branch.main.remote upstream
+```
+
+Configure `git` never to push to the `upstream` remote:
+
+```shell
+git remote set-url --push upstream git@{{ repo_host }}/<username>/{{ repo_name }}.git
+```
+
+## Verify the remote configuration
+
+List the remote repositories with urls:
+
+```shell
+git remote -v
+```
+
+You should have two remote repositories: `origin` to your forked CPython repository, and `upstream` pointing to the official CPython repository:
+
+```shell
+origin  git@{{ repo_host }}:<username>/{{ repo_name }}.git (fetch)
+origin  git@{{ repo_host }}:<username>/{{ repo_name }}.git (push)
+upstream        https://{{ repo_url() }} (fetch)
+upstream        git@{{ repo_host }}:<username>/{{ repo_name }}.git (push)
+```
+
+Note that the push url of `upstream` repository is the forked repository.
+
+Show the upstream for `main` branch:
+
+```shell
+git config branch.main.remote
+```
+
+You should see `upstream` here.
+
+## Work on a feature branch
+
+Create and switch to a new branch from `main`:
+
+```shell
+git switch -c <branch-name> main
+```
+
+Stage the changed files:
+
+```shell
+git add -p # to review and add changes to existing files
+git add <filename1> <filename2> # to add new files
+```
+
+Commit the staged files:
+
+```shell
+git commit -m "the commit message"
+```
+
+Push the committed changes:
+
+```shell
+git push
+```
+
+## Create a pull request
+
+Navigate to the hosting platform and create a pull request.
+
+After the pull request is merged, you need to delete the branch in your namespace.
+
+```{note}
+It is recommended to configure the automatic deletion of the merged branches.
+```
+
+## Housekeeping the cloned repository
+
+Update the `main` branch from upstream:
+
+```shell
+git switch main
+git pull upstream main
+```
+
+Remove deleted remote-tracking references:
+
+```shell
+git fetch --prune origin
+```
+
+Remove local branches:
+
+```shell
+git branch -D <branch-name>
+```
+
+After all these operations, you should be ready to <project:#work-on-a-feature-branch> again.
+
+## Reference
+
+- [Git bootcamp and cheat sheet, Python Developer's Guide](https://devguide.python.org/getting-started/git-boot-camp/)
diff --git a/template/docs/development/index.md b/template/docs/development/index.md
index 24b46c53..03fc20fb 100644
--- a/template/docs/development/index.md
+++ b/template/docs/development/index.md
@@ -3,6 +3,7 @@
 This section is designed for developers and covers essential topics during daily development lifecycle. Follow these guidelines to ensure all contributors adhere to best practices, maintain code quality, and collaborate efficiently.
 
 ```{toctree}
+git-workflow
 setup-dev-env
 cleanup-dev-env
 commit