From 50d3ac715f39fab193d8e343fa0f009f0c722c0a Mon Sep 17 00:00:00 2001
From: RomanOstr <46819322+RomanOstr@users.noreply.github.com>
Date: Fri, 24 Jul 2026 17:41:53 +0300
Subject: [PATCH] Always publish repositories under Ceratops-Code

---
 .../references/create-or-publish.md                        | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/skills/ceratops-gh-repo-lifecycle/references/create-or-publish.md b/skills/ceratops-gh-repo-lifecycle/references/create-or-publish.md
index e676ba6..5f1a82a 100644
--- a/skills/ceratops-gh-repo-lifecycle/references/create-or-publish.md
+++ b/skills/ceratops-gh-repo-lifecycle/references/create-or-publish.md
@@ -20,9 +20,10 @@ release semantics.
 
 ### Inputs To Capture
 
-- GitHub organization (not a personal account), repo name, default branch,
-  visibility, fork status, and branch naming. Default organization:
-  `Ceratops-Code`.
+- Capture the repo name, default branch, visibility, fork status, and branch
+  naming.
+- Always use `Ceratops-Code` as the GitHub repository owner; do not ask which
+  owner to use.
 - Maintainer merge policy, expected artifact type, release expectations, and
   missing inputs required by the GitHub repo, code repo, or artifact contracts.