fix(repository-template): update repository links to point to stefaniuk repository

Author: stefaniuk

.github/skills/repository-template/SKILL.md

@@ -5,7 +5,7 @@ description: Toolkit for creating a code repository from template, or/and updati
 
 # Repository Template Skill 🧩
 
-This skill enables adopting, configuring, or removing capabilities from the [NHS England Tools Repository Template](https://github.com/nhs-england-tools/repository-template). Each capability is modular and can be applied independently.
+This skill enables adopting, configuring, or removing capabilities from the [NHS England Tools Repository Template](https://github.com/stefaniuk/repository-template). Each capability is modular and can be applied independently.
 
 ## Source Reference 📚
 
@@ -23,11 +23,11 @@ For example, to adopt `scripts/init.mk`, copy from:
 
 to your target repository's `scripts/init.mk`.
 
-⚠️ Distribution note: this SKILL file is mirrored verbatim across three homes - the NHS England shared GitHub Copilot prompt catalogue (similar to the [Awesome GitHub Copilot Customizations](https://github.com/github/awesome-copilot)), the upstream [Repository Template](https://github.com/nhs-england-tools/repository-template), and every repository created from that template. Keep the wording identical in all locations, instead of editing per environment, detect where you are and resolve paths accordingly.
+⚠️ Distribution note: this SKILL file is mirrored verbatim across three homes - the NHS England shared GitHub Copilot prompt catalogue (similar to the [Awesome GitHub Copilot Customizations](https://github.com/github/awesome-copilot)), the upstream [Repository Template](https://github.com/stefaniuk/repository-template), and every repository created from that template. Keep the wording identical in all locations, instead of editing per environment, detect where you are and resolve paths accordingly.
 
 🤖 Assistant behaviour: when a user asks broad questions such as _"repository template – describe how to use this skill"_, respond by summarising the capability list below, you must list all the capabilities in a tabular form as the next step and invite user to issue a follow-up prompt that names a specific capability plus an action (add, remove or improve) they want performed in their repository. This keeps replies actionable and focused on the modular building blocks.
 
-AI assistants or automation should detect the active context before copying files. For a reliable conclusion, check the repository's git URL first (for example, `git remote get-url origin`). If it points to `nhs-england-tools/repository-template`, you are working inside the upstream template and can read directly from the project root.
+AI assistants or automation should detect the active context before copying files. For a reliable conclusion, check the repository's git URL first (for example, `git remote get-url origin`). If it points to `stefaniuk/repository-template`, you are working inside the upstream template and can read directly from the project root.
 
 Use the following checks after confirming the git URL:
 
@@ -1415,7 +1415,7 @@ SONAR_TOKEN=$SONAR_TOKEN \
 To adopt the complete template directly from GitHub:
 
 ```bash
-git clone https://github.com/nhs-england-tools/repository-template.git my-project
+git clone https://github.com/stefaniuk/repository-template.git my-project
 cd my-project
 rm -rf .git
 git init

.github/skills/repository-template/scripts/git-clone-repository-template.sh

@@ -3,8 +3,9 @@
 cd "$(git rev-parse --show-toplevel)" || exit 1
 cd .github/skills/repository-template
 if ! [ -d "assets" ]; then
-  git clone https://github.com/nhs-england-tools/repository-template.git assets
+  git clone https://github.com/stefaniuk/repository-template.git assets
 else
   cd assets
-  git pull origin main
+  git pull origin custom
 fi
+git checkout custom